MX-23 Fluxbox development

[ceeslans]

@PPC good to see that you still keep track of MX Fluxbox development; I always appreciated your input especially concerning applications like tint2, jgmenu and the likes.
Am intrigued about your FT10 applications package. How (or which part thereof) is compatible with the MX Fluxbox setup?

[PPC]

Am intrigued about your FT10 applications package. How compatible (or which part thereof) is compatible with the MX Fluxbox setup?

I created yad GUI's to simplify adding and removing quick launch icons to a fixed tint2rc (handy if you want to use tint2rc "dock file" to replace the current, much more resource hungry dock), and also edit some of it's basic settings (like color, position, size, etc) - so users can manage all that without the overkill of complexity that's the default tint2 configuration GUI. Those scripts can be adapted to manage any currently enabled tint2 file.

P.

[Melber]

Since I'm not currently a MXFB user, I have no right to "complain", but the tint2 simpledock configuration (maybe adapted from the model I proposed in the past?) does use a lot less resources than the default MXFB toolbar (that uses more RAM for each new icon). I recall having proposed a yad GUI to add/remove quick launch icons to tint2 files- It would be a major change, swapping the default "dock", but I do think it would mean that the end product would be lighter and no features would be lost.

Hi @PPC,

exactly which tint2 configuration do you mean with "simpledock "?
How much is a "lot less" RAM usage?

[PPC]

exactly which tint2 configuration do you mean with "simpledock "?
How much is a "lot less" RAM usage?

I think it's the first tint2 model, available from the tint2 selection window.
Back when I was using MXFB, the original dock used several Mb of RAM more than just using tint2 as a dock. I did not test what's the current difference of RAM usage between both docks.

Really my "main suggestion", if any, would be to implement an MX menu toolbar entry, and also a "show desktop", "File Manager" and "Web browser" quick launch "buttons" on the default fluxbox toolbar - that alone allows users to launch the most used software of any distro with a single click. One can easily add also a text terminal quick launcher (e: >_ ) or a text e-mail quick launcher (ex: @). That would make fluxbox's toolbar as "usable" as most default toolbars, in any OS.
To simply have parity of features between the fluxbox and the tint2 toolbar, this would suffice:
-a launcher for the rofi menu (saying "Menu", or "MX", or whatever)
-a launcher for the settings (using a glyph the devs feel it's appropriate)
-a launcher for the default file manager (using a glyph that looks like a folder)
-a launcher for the default web browser (using a glyph that looks like a globe)
-after the clock, a launcher for exit options (using a glyph that looks like the power button)

Adding new "buttons", however, is so complex that I don't recommend anyone below the level of medium/advanced user should try. If the Devs like that and want to add even more features to the default fluxbox toolbar, an yad script can be created to edit fluxbox's config file and add/remove text quicklaunchers (and even offer a list of generic glyphs that can be used as surrogate "icons").

EDIT: Adding new quick-launchers (other than the ones used by default in the tint2 toolbar) to the default fluxbox toolbar is not a priority - I think the general idea is to use the dock for that - but I think the dock began being used because of the then impossibility to use quick-launch buttons on the fluxbox toolbar, and only after the dock was being used, MXFB began using the tint2 toolbar (that allows quick launch icons) by default.

P.

[siamhie]

Adding new "buttons", however, is so complex that I don't recommend anyone below the level of medium/advanced user should try. If the Devs like that and want to add even more features to the default fluxbox toolbar, an yad script can be created to edit fluxbox's config file and add/remove text quicklaunchers (and even offer a list of generic glyphs that can be used as surrogate "icons").

P.

I saw your post on the antiX forums and found it easy to follow but then again, I know my way around the various config files needed to edit.


I've only begun to set up my buttons. viewtopic.php?p=759995#p759995

[i_ri]

Hello Jerry3904
fluxbox /apps tint2 Layer Desktop

review
The /apps file setting tint2 to Layer Desktop
furnishes behavior of Normal Windows are Above tint2 panel.
Windows cover tint2 toolbar.

When tint2 is running:
Without an /apps setting for the tint2 Layer,
take that out. Not having /apps set tint2 Layer
trial these for minimizing all and maximizing all windows when tint2 is running.

Code: Select all

# Control Mod1 Down :MacroCmd {ShowDesktop} {Deiconify}
# Control Mod1 Up :ForEach {Deiconify}

put the two on one keybind, together.

Code: Select all

Control Mod1 Up :ToggleCmd {MacroCmd {ShowDesktop} {Deiconify}} {ForEach {Deiconify}} 

--tint2 xdotool button.
long version. The filtering (filter) syntax condition arguments that worked in fluxbox 1.3.5 do not transfer to fluxbox 1.3.7+git. ..., however, need adapt newer condition (filter)arguments.
Some Blah Matches (filter) longer version not worth it when there is
this Deiconify default fluke that works with event tint2.
Try the Control Mod1 Down. with tint2 running; with tint2 Layer control removed from /apps.

mixed with alt+d it is quite a bit of control to visible or not visible tint2. Where else* can a person obliterate a toolbar? call it a feature.

*fluxbox toolbar, fluxbox Configuration menu Toolbar Visible. myself, answer.

[Jerry3904]

First this thread is not active because MX 23 Fluxbox development is finished, but we do have a MX 25 thread open where this belongs. Perhaps you could repost over there so we can find it later when we get more serious about that development.

The new version of mx-fluxbox that came through a few days ago added to the apps file a layer 12 setting for tint2 and conky, right? So if I understand correctly you are proposing a key combo to toggle tint2 state instead of having it be fixed.

<I'm going to lock this topic>