MX-23 Fluxbox development

[Jerry3904]

I want to start collecting items toward an agenda now so that they can be discussed and worked on gradually. Here is my current list, which I will keep updated--feel free to suggest changes or additions. Please comment by number (e.g., "#6 is a really stupid idea") so we can keep track.

1. use rofi as appfinder substitute
2. remove Debian menu as default, making installation procedure to include current startup entry AND how to remove
3. refresh rofi-help menu
4. change F2 to rofi runbox
5. include gkrellm in comfort style
6. keys: add easy screen blanking:

Code: Select all

# turn off monitor
none F12 :Exec sleep 1 ; xset dpms force off

7. change desktop files for mxfb-look and mx-rofi-manager into general names: Look manager, Rofi manager
8. figure out how to translate labels in the idesk icon files
9. use a Rofi power manager instead of exit-options ?
10. add Goodies to menu with xkcd and/or weather?
11. switch to viewnior or mirage (< Ceeslans) instead of gThumb
12. [ideas?]
13. develop a session file to pull in defaults for mx-fluxbox if they don't exist already. use /etc/X11/Xsession.d/21xfce4-defaults-mx as a template.
14. develop method in startup that would process autostart entries from /etc/xdg/autostart, and ~/.config/autostart.
15. Fluxbox menu -- edit appearance submenu to hide legacy styles as default
16. Include font-awesome in default installation
17. Amend or include additional links in MX-Tour help tab to open mxfb specific help docs.
18. review MX-Tweak tabs
19. MX-Look: Develop a set of looks to be included in the default installation to give user a choice between a few presets setups.

[dolphin_oracle]

2. Please elaborate. I’m not sure what you mean

11. In personally have no problem with an image viewer change. I use mirage myself. Just keep in mind that One of the criteria for gthumb was that it could print.

[wdscharff]

11. a topic I can say something about :-)
Mirage is a bit like "not fish, not meat".
Has a thumbnail overview of a directory.
But like viewnior, it can't do anything with RAW or DNG files.
Its resource requirements (ram) are significantly higher, halfway between gthumb and viewnior.
Viewnior shows the basic EXIF data under properties, mirage does not have this function at all, but it has minimally more "image processing functions".
Printing has never been an issue for me, I generally use exposure services on the WWW or for small formats (<=20x30cm) the Kodak photo imagesetters that are here in the drugstores and supermarkets.

In a voting between the two, I would vote for viewnior.

[Jerry3904]

Thanks both for the comments!

@wdscharff I too am in favor of viewnior ATM, but now have it set as default here so I can do more testing. BTW: you were right about it setting the wallpaper, thanks; we would have to set that with the install. I like the low mem usage, speed and basic functions--like everything else, user can use MXPI to upgrade (gThumb, Mirage, Gimp, etc.) as needed.

@dolphin_oracle #2 Currently the Debian menu from mxfb-accessories is incorporated into the rootMenu by default, which requires additional code for updates and an entry into startup. There is no way to remove it that stops the added upgrade activity as well--user needs to remove a file in /etc IIRC that s/he doesn't even know exists.

I'm hoping we can change the script so that on first run a dialog box will describe what will be changed and added, and how to remove (maybe place that removal info in startup along with the commented command, for instance, so user could find again). Something along those lines ...

[dolphin_oracle]

@dolphin_oracle #2 Currently the Debian menu from mxfb-accessories is incorporated into the rootMenu by default, which requires additional code for updates and an entry into startup. There is no way to remove it that stops the added upgrade activity as well--user needs to remove a file in /etc IIRC that s/he doesn't even know exists.

I'm hoping we can change the script so that on first run a dialog box will describe what will be changed and added, and how to remove (maybe place that removal info in startup along with the commented command, for instance, so user could find again). Something along those lines ...

I honestly don't know what you are referring to. if you can walk me through what file from mxfb-accessories and what file in /etc to remove I'll play around. I've already got Xfce and KDE defaults being respected on first login, just need to figure out fluxbox.

[Jerry3904]

Sorry, lmme splain.

--mxfb-accessories includes mxfb-menu-generator
--when installed, currently that generator automatically triggers code for upgrade use, maybe in /etc/apt/apt.conf.d/ (can't remember now)
--we currently have the generator active in startup and listed in the rootMenu by default

What I imagine:
--generator commented out by default in startup and in rootMenu
--no code enabled by default for upgrade inclusion
--user first launches mxfb-menu-generator: menu and startup enabled, code for upgrade enabled
--somewhow user can easily remove that upgrade code when removing generator

Is that any better?

[dolphin_oracle]

so you want to make it from automatic to manual?

[Jerry3904]

Yup. And have an easy total kill if user changes mind, including removal of apt (?) code

[dolphin_oracle]

well keep it on the list. will require thought and discussion.

[dolphin_oracle]

here's one to add.

develop a session file to pull in defaults for mx-fluxbox if they don't exist already. use /etc/X11/Xsession.d/21xfce4-defaults-mx as a template. I've been working on the xfce one for a while, with the idea of doing one for fluxbox later. will eliminate the mxflux_install script.