mxfb-2025 development ideas

[Jerry3904]

Thanks, fehlix, sounds like a good idea. There is a number of conky topics for MX-25 that I will add to that list.

OK, folks, I'm locking this thread. Have a post coming that categorizes the contents (whew!) so we can actually pitch in.

[Jerry3904]

--4 months later--

I've got an idea that has been coursing through my head for a while, though question whether we have the time, personnel and energy to get it ready for MX-25. Much as I like tint2 and the FB toolbar, I find it annoying that simple common preferences are both not obvious to newbies and require multiple key strokes and hunting. For example, autohide.

My concept is to adopt the design approach that @Melber developed for rofi-manager:



We already have 12/24 hr time change incorporated into tint2-manager with a button that I'd think could be re-purposed with a "hamburger" or similar icon to open the proposed app. In a later development we might want to add a tab for the FB toolbar, or possibly use the same questions for both and have a selection box at the top.

Does this seem like a useful mxfb tool? If we have reasonable agreement that it is, then I'd start a dedicated thread.

[Jerry3904]

I had forgotten to turn the lock off, so Melber sent me this response via PM:

Yes, I can see that being a useful tool. Not going to happen in time for mx25 though. Perhaps a goodie for 25.1 or 25.2.

[i_ri]

/usr/bin/tint2-toggle-autohide.sh
/usr/bin/togglepanel
When there are more than one tint2 running,
these scripts
impact the tint2 that is set as default tint2rc.
To control multiple tint2 individually will require some time to put a script together, as indicated by Melber (Melber' script does indicate"MORE, as proof of concept" as if it is ready for additional inclusions.)

Can tint2-toggle-autohide.sh and/ or /usr/bin/togglepanel be used interim?
until the time when additional tint2 can each have autohide settings manager?

[Jerry3904]

Sure, and that was a bad example I selected (must have been thinking of the FB panel). I will start a thread one of these days.

I have no interest in "controlling tint2's individually" b/c the person who wants to do that will be more than able to edit the script. I'm looking at easing access to 1)common, and 2) simple changes.