tint2 16.2 released :)

damo · 2017-03-26 16:02:05

^ TY for the info

o9000 · 2017-04-23 15:51:17

I have released 0.14.3. The changes are trivial. The main change is a new tint2rc mime type associated with tint2conf.

However, the debian package scripts need to be updated. To figure out what's wrong, I've created https://gitlab.com/o9000/tint2/tree/mas … ing/debian . It's been tested only on Ubuntu's PPA build servers. I'm not sure if anything needs to be changed for Debian.

The changes were:

* I removed the old wiki content, since now we have a man page and .../doc/tint2
* I updated the *installs file, since some tint2 files were missing on installation (actually this was on stock debian, the BL package was much better, but some files were still missing)
* I included the license header to shut up that lintian warning

You might want to diff it against the BL debian to make sure everything is OK. There are some differences (changelog, control) which should probably remain as they are. If you notice anything unusual, please tell me, I'm a noob when it comes to packaging scripts, I might have done something wrong.

Last edited by o9000 (2017-04-23 15:53:20)

malm · 2017-04-23 16:47:34

Nice new-release script

o9000 · 2017-04-23 16:57:09

malm wrote:

Nice new-release script

Thanks. There were too many things to do by hand, which was error-prone.

o9000 · 2017-04-28 20:33:16

I forgot to say that if you start tint2conf from tint2 (via launcher, clock command, whatever), it should now open directly the current theme instead of just showing you the list of themes. I find this quite useful.

It works by storing the path to the config in the env variable TINT2_CONFIG. You could use it to open the config in an editor if you'd like that.

Last edited by o9000 (2017-04-28 20:35:09)

o9000 · 2017-04-29 11:50:36

0.14.4 out. Two bugfixes (one reported on this forum, thanks for that!) and improved interaction with jgmenu.

malm · 2017-04-29 18:29:52

Nice. I like the tint2conf trick.

o9000 · 2017-05-21 11:36:33

0.14.5 out, fixes some memory leaks.

Sector11 · 2017-05-21 16:12:44

I have a question about tint2. I first used it in Xubuntu somewhere around 2008.

That's ±9 years. Isn't it time to become version 1.something at least?

o9000 · 2017-05-21 17:44:10

I thought about it, not sure what it should be. 1.0? 1.14? 2.14?

Normally the major version number is increased when there are backwards-incompatible changes, which has not been the case since 0.11 I think. That should have been 1.0. Switching to 1.0 now is possible, but doesn't really do justice to a decade old project. Still, staying in 0.* doesn't do it justice either. Not sure about 1.14. Opinions?

Anyways. tint2 will go into bugfix-only mode for a while. I have too many things on my plate at the moment. Minor major version number changes have to wait.

By the way, there is a fork called tint3: https://github.com/jmc-88/tint3 It's a refactoring of tint2 which gets rid of glib; it replaces it with C++ containers. This is a very good idea, glib has been the source of many bugs in tint2; C++ containers are much easier to use. The guy also knows what he's doing. I'm not involved in the project, other than sending a couple of patches for common bugs in tint2/tint3. There was a discussion about merging back the codebase at some point, but I don't really have the time and energy to do that in the near future.

Sector11 · 2017-05-21 18:26:20

tint3 - blasphemy! Never! ... Well, maybe to test. ]:D

As a sofware developer I'm so green behind the ears that mother nature is borrowing some. I'm a zero in other words.

However: you did ask for Opinions.

IMHO: Keep doing what you're doing, your explanation says it all:
Life (plate) = Minor major version number changes have to wait, is more than acceptable.

I was just curious.

ohnonot · 2017-05-22 06:44:24

o9000, you have any idea to what extent the developer of tint3 implements recent changes to tint2?
to what extent it is a 1:1 clone of tint2, in terms of functionality?
e.g., could one use the same config files?
i see now that he has added support for gradients, which is the most recent feature of vanilla tint2, isn't it?
personally, i couldn't be without the exec plugin...

testing:

ln -s /usr/bin/tint3 ~/bin/tint2

o9000 · 2017-05-22 08:37:49

It was a fork of 0.11 while tint2 was not maintained. He is starting to add the new stuff slowly, but I don't know the details. Feel free to ask him

jmc · 2017-05-22 08:53:14

I have been summoned!

Hi everyone, I'm the current maintainer of tint3. o9000 speaks the truth, I forked tint2 during the time it was not actively developed to make some minor improvements here and there, and I've been trying to refactor it to make it more maintainable and, hopefully, less prone to crashes and memory leaks. Since then, Real Life™ has soaked up lots of my time, so I haven't been as proactive as o9000 and the tint2 community in providing new features, but I'm trying to catch up as I can: I've recently added support for gradients, and I'd like to backport some more stuff, eventually...

I also have ideas on new cool things to build, which I sometimes dump @ https://github.com/jmc-88/tint3/projects if you're curious. Those are not tint3-specific, so I'd love to share these between projects (and do a code merge for real, given enough time).

Anyway, currently you can't expect 1:1 compatibility, though that's what I'm striving for. Feel free to try tint3 out if you'd like, and let me know if it totally sucks.

P.S.: let me use this occasion to publicly praise o9000 for taking the time to cross-report bugs shared by the two projects; I'd never have discovered them on my own.

malm · 2017-05-22 19:50:14

IMO:
- It would have been tidier if the team who brought it to 0.11 had nudged it over the line to v1.0.
- @o9000: Don't underestimate what you've done! You've put a hugh amount of work into it. tint2 lay pretty dormant at 0.11 for some time. You have not only created a new home (at gitlab), but brought stability, features and documentation to a new level. I think tint2 deserves to be v1.0.
- If we don't do it at this point, we risk getting stuck at 0.x 'forever'.
- I don't think that tagging at v1.0 undermines or takes away anything from the original ttm+tint2 devs.
- I think that releasing v1.0 can take place without indicating that we have lost backward compatibility.
I think it does three things:
1. Sends a message that the project is active
2. Shows that we have the features originally intended (okay ambigous statement, but you know what I mean)
3. Removes any sense that we are still at some sort of alpha/beta stage.

@jmc - great stuff. I will compile and have a play.
(or use backports if @earlybird uploads - even easier :-) )

P.S. I don't like 1.14 or 2.14 - not sure why, just don't feel right.

Last edited by malm (2017-05-22 19:52:24)

o9000 · 2017-05-22 20:36:23

Thanks for the input. Indeed 1.0 feels natural, and I think we shall see it happen this summer.

One thing I can guarantee: the version number will NOT go backwards.

malm · 2017-05-22 20:42:28

Yippee!

Sector11 · 2017-05-22 21:28:09

o9000 wrote:

One thing I can guarantee: the version number will NOT go backwards.

Hey that's different!

But wait a minute: 42 would be great!

- The answer to Life the Universe and Tint2! It's a natural!

ohnonot · 2017-05-23 04:32:04

hei jmc, thanks for the response!

jmc wrote:

I've recently added support for gradients, and I'd like to backport some more stuff, eventually...

so no executor plugin currently... :'(

P.S.: let me use this occasion to publicly praise o9000 for taking the time to cross-report bugs shared by the two projects; I'd never have discovered them on my own.

you are preaching to the choir here!

martix · 2017-05-25 16:03:03

After reading some recent posts, indeed, it seems to be the right idea with v1.0.

There is a minor feature I'd like to mention: I'm not sure but somehow I recall grabbing an icon after holding a left click on it and not only pull it to an other desktop, but also e.g. in between two other icons on the same desktop (in order to change how the icons are arranged on the same desktop). It is still possible to change the order of the icons on the same desktop: If I'm not mistaken it works after a right click. I was just wondering if it would be generally more convenient (or possible?) that the icon could be inserted between to other icons on the same desktop with the "hold left click+move" method?

#101 2017-03-26 16:02:05

Re: tint2 16.2 released :)

#102 2017-04-23 15:51:17

Re: tint2 16.2 released :)

#103 2017-04-23 16:47:34

Re: tint2 16.2 released :)

#104 2017-04-23 16:57:09

Re: tint2 16.2 released :)

#105 2017-04-28 20:33:16

Re: tint2 16.2 released :)

#106 2017-04-29 11:50:36

Re: tint2 16.2 released :)

#107 2017-04-29 18:29:52

Re: tint2 16.2 released :)

#108 2017-05-21 11:36:33

Re: tint2 16.2 released :)

#109 2017-05-21 16:12:44

Re: tint2 16.2 released :)

#110 2017-05-21 17:44:10

Re: tint2 16.2 released :)

#111 2017-05-21 18:26:20

Re: tint2 16.2 released :)

#112 2017-05-22 06:44:24

Re: tint2 16.2 released :)

#113 2017-05-22 08:37:49

Re: tint2 16.2 released :)

#114 2017-05-22 08:53:14

Re: tint2 16.2 released :)

#115 2017-05-22 19:50:14

Re: tint2 16.2 released :)

#116 2017-05-22 20:36:23

Re: tint2 16.2 released :)

#117 2017-05-22 20:42:28

Re: tint2 16.2 released :)

#118 2017-05-22 21:28:09

Re: tint2 16.2 released :)

#119 2017-05-23 04:32:04

Re: tint2 16.2 released :)

#120 2017-05-25 16:03:03

Re: tint2 16.2 released :)

Board footer