Forum › Forums › antiX-development › Development › bug in script desktop-menu? antiX 19.x 32bit/64bit › Reply To: bug in script desktop-menu? antiX 19.x 32bit/64bit
#45: „Write the output to the applications file from the appropriate template”
What applications file does this refer to? Does it actually mean the program file will get modified?
(I still don’t understand the precise processing of the respective part of the script code, so I have no clue what it actually does when –write-out is filed as an option.)#55: „convert icon base names to icon absolute paths using specified icon theme”
What is meant by “icon base name”? I translated it to „Symbolbild-Basisname”, which sounds pretty technical and is the correct translation but I actually have no clue what to make of it. So best would be here not to translate literally, once we have found out what actually is meant.
#45 means to take the output of desktop-menu and write it to the applications menu file (~/.icewm/menu-applications, ~/.fluxbox/menu-applications, ~/.jwm/menu-applications) using the template file (/usr/share/desktop-menu/templates/*) that matches the window manager you are using. (icewm, fluxbox, jwm, openbox)
#55 means to convert the icon name used in the .desktop file (ex: roxterm) to be the absolute path of the icon using the default users theme or the theme specified with –theme (Ex: roxterm – > papirus-antix theme -> /usr/share/icons/papirus-antix/48×48/categories/utilities-system-monitor.png). In fact this is an outdated option and is pretty much the default now (fluxbox requires it) and likely does not work anymore so this option we can probably remove.
As far as the merge requests… after having a brief look, help me to understand a few things.
1) the help text menu to be translated using gettext. Why is it broken into so many print statements rather than changing the first and last lines to:
print(_("""Usage: %s [options]
.....*......
""" % sys.argv[0]))
2) the config file. This is obviously per user configuration, but why does it need the –write-out-global function? Is it because we are defaulting to reading the configuration file if no option is set? If so –write-out-global is run as root by apt, so which configuration file is it then using? Also are we still using the symlink if the configuration file is used or is there a separation between menu files per user that I am not seeing?
3) One problem with the separator options I have been looking to resolve while you have been making these changes. When you use order=ngc and specify all separator options. One line will show expected results, but another would show unexpected results when there is information missing (like generic name). For example:
| zzzfm | [ file manager ] { The is an application to manage your files }
| zzzfm | [ This is an application to manage your files ]
Computers are like air conditioners. They work fine until you start opening Windows. ~Author Unknown