Nope, in the default slim setup desktop-session is started as the session handler. If you would like a program started globally then put it in / etc / desktop-session / startup, on a per user basis ~ / . desktop-session / startup and on a per wm basis ~ / . wm / startup. This is not 100% finalized but it is what to do for this beta.SamK wrote:~/.xinitrc-custom
Is this correctly"plummed-in"? I can't get anything to run from it.
-
DavePosts: 1,062
- Joined: 20 Jan 2010
#136
-
SamKPosts: 1,028
- Joined: 21 Aug 2011
#137
Even though you no longer suspect Menu Manager is contributing to the matters you reported earlier, it would be useful to confirm it. That is now quite easy to do in two short tests. If you are willing to do them it will give Menu Manager a clean bill of health and thereby provide reassurance to other users.
Because various of your reports have made reference to the Applications section of the menu it is appropriate to test whether Menu Manager is working as expected in this area. Test 4 will confirm it is able to hide an item in the Applications menu structure. Test 5 will confirm it is able to show the item hidden in test 4.
TEST 4
Step 1
Boot the shipped 15-b3 ISO using live without any form of persistence. This will provide a clean testing environment.
Step 2
antiX Main Menu-->Applications-->Graphics
Note the section contains an item named GColor2
Step 3
Control Center-->Edit Menus
Select Applications when asked which menu to change
Select Hide when asked whether to hide or show an item
Select Gcolor2 when asked to select an item to hide (Note its status)
Select Refresh when asked whether to refresh the menu or make another change
A window reports the update has been done.
Step 4
antiX Main Menu-->Applications-->Graphics
The section no longer contains an item named GColor2
Once this position is established go on to the next test. There is no need to restart or reboot.
TEST 5
Step 1
Control Center-->Edit Menus
Select Applications when asked which menu to change
Select Show when asked whether to hide or show an item
Select Gcolor2 when asked to select an item to show (Note its status is currently Hidden)
Select Refresh when asked whether to refresh the menu or make another change
A window reports the update has been done.
Step 2
antiX Main Menu-->Applications-->Graphics
The section now contains an item named GColor2
OUTCOME
Post the results of tests 4, and 5.
General note for tests 4 and 5
The shipped .desktop files are a bit of a hotchpotch as far as the value of NoDisplay= is concerned. This is the value that Menu Manager uses to determine the hidden/shown status. Some don't have one, some have one that is any combination of upper and lower case letters. Menu Manager has to accommodate these by adopting a standard form for this particular entry.
All .desktop files that have been either hidden or shown by Menu Manager are given the standard form. They then report that corresponding state.
In the shipped ISO, any file that does not have the NoDisplay= entry reports as Not Set, those using a non standard form report as Malformed. Neither of these affect its operation in any way i.e. each file still behaves as expected in the antiX menu irrespective of the status reported by Menu Manager.
Exaggerating to make the point, if every shipped .desktop file were hidden (or shown) by Menu Manager none of them will report as Not Set or Malformed, they will each report as Hidden (or Shown).
OK so you have confirmed Menu Manager has been eliminated as a potential source of problems of removing menu items in your earler reports.skidoo wrote:...Test3 results are fine, they are as expected.
Even though you no longer suspect Menu Manager is contributing to the matters you reported earlier, it would be useful to confirm it. That is now quite easy to do in two short tests. If you are willing to do them it will give Menu Manager a clean bill of health and thereby provide reassurance to other users.
Because various of your reports have made reference to the Applications section of the menu it is appropriate to test whether Menu Manager is working as expected in this area. Test 4 will confirm it is able to hide an item in the Applications menu structure. Test 5 will confirm it is able to show the item hidden in test 4.
TEST 4
Step 1
Boot the shipped 15-b3 ISO using live without any form of persistence. This will provide a clean testing environment.
Step 2
antiX Main Menu-->Applications-->Graphics
Note the section contains an item named GColor2
Step 3
Control Center-->Edit Menus
Select Applications when asked which menu to change
Select Hide when asked whether to hide or show an item
Select Gcolor2 when asked to select an item to hide (Note its status)
Select Refresh when asked whether to refresh the menu or make another change
A window reports the update has been done.
Step 4
antiX Main Menu-->Applications-->Graphics
The section no longer contains an item named GColor2
Once this position is established go on to the next test. There is no need to restart or reboot.
TEST 5
Step 1
Control Center-->Edit Menus
Select Applications when asked which menu to change
Select Show when asked whether to hide or show an item
Select Gcolor2 when asked to select an item to show (Note its status is currently Hidden)
Select Refresh when asked whether to refresh the menu or make another change
A window reports the update has been done.
Step 2
antiX Main Menu-->Applications-->Graphics
The section now contains an item named GColor2
OUTCOME
Post the results of tests 4, and 5.
General note for tests 4 and 5
The shipped .desktop files are a bit of a hotchpotch as far as the value of NoDisplay= is concerned. This is the value that Menu Manager uses to determine the hidden/shown status. Some don't have one, some have one that is any combination of upper and lower case letters. Menu Manager has to accommodate these by adopting a standard form for this particular entry.
All .desktop files that have been either hidden or shown by Menu Manager are given the standard form. They then report that corresponding state.
In the shipped ISO, any file that does not have the NoDisplay= entry reports as Not Set, those using a non standard form report as Malformed. Neither of these affect its operation in any way i.e. each file still behaves as expected in the antiX menu irrespective of the status reported by Menu Manager.
Exaggerating to make the point, if every shipped .desktop file were hidden (or shown) by Menu Manager none of them will report as Not Set or Malformed, they will each report as Hidden (or Shown).
-
skidooPosts: 1,444
- Joined: 09 Feb 2012
#138
ControlCentre --} System (tab) --} Configure System --} dialogbox titled"Antix System"
This is just feedback. Please don't spend time typing answers here to the user-POV questions I'm raising.
In the tab titled"Disk_Management", I'm confused by
checkbox[ ] Enable Disk Management... plus"Options"
The latter 3 options, linked as a set of radio buttons ~~ seems clear those would trigger one-time operations.
User wonders: is"Clear package Cache" a one-time operation? It is performed if I tick its box then click OK ?
If so, why its control disabled, until/unless I first tick the"Enable Disk Management" box?
-=-
Same for"Clear Logs" ~~ user is left guessing/wondering whether, if ticked, a one-time operation will be pereformed...
...or whether this aspect of"management", once"enabled", will be performed automatically on a regular basis (each boot?)
I"enabled" ClearPackageCache and clicked OK.
No confirmation dialog.
Upon immediately revisiting ControlCentre --} System (tab) --} Configure System --} DiskManagement (tab)
I find the main checkbox unticked, with ClearPackageCache grayed-out and unticked.
Confusing.
If the action was a one-time operation, was it immediately performed?
A flag was set, and I should expect it will be performed during next boot? Next shutdown?
Now that the flag is set, will ClearPackageCache be"managed" (performed automatically, on a recurring basis)?
If so, how do I later"toggle it off"? Must I revisit this dialog + click top"enable" + leave checkbox unclicked then click OK?
In the absence of documentation (if such exists, consider providing a"help" button linking to it)
conveying"...next boot" (or ...next shutdown, or ...each shutdown, or during each shutdown) seems important.
For each of the options, need to convey whether user's choice will"PERFORM a one-time action" vs"setting a flag, a toggle, to ENABLE automated management"
Same as described above, the"Grub Repair" tab, and its checkbox, is equally daunting / confusing.
Surely it's a one-time operation. Wording the label as"PERFORM grub repair" (no caps) would be more clear.
This is just feedback. Please don't spend time typing answers here to the user-POV questions I'm raising.
In the tab titled"Disk_Management", I'm confused by
checkbox[ ] Enable Disk Management... plus"Options"
The latter 3 options, linked as a set of radio buttons ~~ seems clear those would trigger one-time operations.
User wonders: is"Clear package Cache" a one-time operation? It is performed if I tick its box then click OK ?
If so, why its control disabled, until/unless I first tick the"Enable Disk Management" box?
-=-
Same for"Clear Logs" ~~ user is left guessing/wondering whether, if ticked, a one-time operation will be pereformed...
...or whether this aspect of"management", once"enabled", will be performed automatically on a regular basis (each boot?)
I"enabled" ClearPackageCache and clicked OK.
No confirmation dialog.
Upon immediately revisiting ControlCentre --} System (tab) --} Configure System --} DiskManagement (tab)
I find the main checkbox unticked, with ClearPackageCache grayed-out and unticked.
Confusing.
If the action was a one-time operation, was it immediately performed?
A flag was set, and I should expect it will be performed during next boot? Next shutdown?
Now that the flag is set, will ClearPackageCache be"managed" (performed automatically, on a recurring basis)?
If so, how do I later"toggle it off"? Must I revisit this dialog + click top"enable" + leave checkbox unclicked then click OK?
In the absence of documentation (if such exists, consider providing a"help" button linking to it)
conveying"...next boot" (or ...next shutdown, or ...each shutdown, or during each shutdown) seems important.
For each of the options, need to convey whether user's choice will"PERFORM a one-time action" vs"setting a flag, a toggle, to ENABLE automated management"
Same as described above, the"Grub Repair" tab, and its checkbox, is equally daunting / confusing.
Surely it's a one-time operation. Wording the label as"PERFORM grub repair" (no caps) would be more clear.
-
skidooPosts: 1,444
- Joined: 09 Feb 2012
#139
Sam, those additional tests produce expected results, both in non-persistent and persistent live session.
suggestion: If possible, in the 3-2-1 countdown confirmation dialog, display just the progressbar and omit the"OK" button.
wishlist item: case-INsensitive sort for Name= strings displayed to the show/hide screens
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://standards.freedesktop.org/desktop-entry-spec/latest/ar01s11.html"
linktext was:"http://standards.freedesktop.org/deskto ... 01s11.html"
====================================
and employ a custom line X-antix-MenuManager= line instead of dealing with the hodgepodge?
A further consideration: the mix includes occasional OnlyShowIn= declarations.
I haven't scoured the current antix beta build for instances of this among .desktop files for preinstalled apps, but the MX build will surely contain .desktop files which declare OnlyShowIn=xfce
NotShowIn= is another valid declaration, but is seldom encountered & I'm at a loss to recall an example where disregarding it was beneficial/desirable.
Why should (must) MenuManager consider whether a OnlyShowIn declaration exists?
Example: install"mate-system-monitor" and note that it fails to display in menu (because"UpdateMenus" apparently respects the OnlyShowIn declaration).
I tested adding it via MenuManager, which offered it as a show-able item. Voila, as desired, it displayed to the menu (SystemTools subcat);
however, down the road... once the"Update Menus" command is used, mate-system-monitor will again be absent from the desktop menu.
If conveying that was your intent (vs choosing to suppress"malformed" items from being displayed to the picker screen), great.
suggestion: If possible, in the 3-2-1 countdown confirmation dialog, display just the progressbar and omit the"OK" button.
wishlist item: case-INsensitive sort for Name= strings displayed to the show/hide screens
Might it be beneficial to"extend the spec"In the shipped ISO, any file that does not have the NoDisplay= entry reports as Not Set, those using a non standard form report as Malformed.
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://standards.freedesktop.org/desktop-entry-spec/latest/ar01s11.html"
linktext was:"http://standards.freedesktop.org/deskto ... 01s11.html"
====================================
and employ a custom line X-antix-MenuManager= line instead of dealing with the hodgepodge?
A further consideration: the mix includes occasional OnlyShowIn= declarations.
I haven't scoured the current antix beta build for instances of this among .desktop files for preinstalled apps, but the MX build will surely contain .desktop files which declare OnlyShowIn=xfce
NotShowIn= is another valid declaration, but is seldom encountered & I'm at a loss to recall an example where disregarding it was beneficial/desirable.
Why should (must) MenuManager consider whether a OnlyShowIn declaration exists?
Example: install"mate-system-monitor" and note that it fails to display in menu (because"UpdateMenus" apparently respects the OnlyShowIn declaration).
I tested adding it via MenuManager, which offered it as a show-able item. Voila, as desired, it displayed to the menu (SystemTools subcat);
however, down the road... once the"Update Menus" command is used, mate-system-monitor will again be absent from the desktop menu.
From user POV,"malformed" suggests I should avoid attempting to show/hide those items.if every shipped .desktop file were hidden (or shown) by Menu Manager none of them will report as Not Set or Malformed
If conveying that was your intent (vs choosing to suppress"malformed" items from being displayed to the picker screen), great.
Last edited by skidoo on 11 Jun 2015, 07:09, edited 3 times in total.
-
skidooPosts: 1,444
- Joined: 09 Feb 2012
#140
Source for the latter is not on github; is it downloadable from daveserver?
Bug exists in fbxkb, or just in antix-fbxkb ?There is a known bug in fbxkb where it always gives you the US flag until a key is pressed.
Source for the latter is not on github; is it downloadable from daveserver?
-
BitJamPosts: 1,308
- Joined: 31 Aug 2009
#141
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://github.com/aisbaa/fbxkb/commits/master"
linktext was:"this version from 2009"
====================================
? The older version didn't work properly on newer systems. So we fixed it so it works pretty well except for that known bug and a limit on the number of layouts it will deal with at one time. All of these limitations may be due to the older interface it uses to ask the X server about keyboard layouts. If you can find a better version, please do. I have more important things to work on or antiX-15 won't get released before anticap goes away for the summer. You may thing this minor bug is the end of the world but there are many many things that have a much higher priority in order to get antiX-15 out the door.
Do you meanskidoo wrote:Bug exists in fbxkb, or just in antix-fbxkb ?There is a known bug in fbxkb where it always gives you the US flag until a key is pressed.
Source for the latter is not on github; is it downloadable from daveserver?
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://github.com/aisbaa/fbxkb/commits/master"
linktext was:"this version from 2009"
====================================
? The older version didn't work properly on newer systems. So we fixed it so it works pretty well except for that known bug and a limit on the number of layouts it will deal with at one time. All of these limitations may be due to the older interface it uses to ask the X server about keyboard layouts. If you can find a better version, please do. I have more important things to work on or antiX-15 won't get released before anticap goes away for the summer. You may thing this minor bug is the end of the world but there are many many things that have a much higher priority in order to get antiX-15 out the door.
-
skidooPosts: 1,444
- Joined: 09 Feb 2012
#142
I asked for the access to the source code to a binary distributed in the antix iso... and in reply you"go off on me",
ranting about misplaced priorities and the price of rice in China rather than providing a link to the requested source.
FWIW, there might be a newer version, available from debian, that you're not aware of.
v0.6-1.1
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://packages.debian.org/jessie/fbxkb"
linktext was:"https://packages.debian.org/jessie/fbxkb"
====================================
You might be wasting effort unnecessarily maintaining the (known buggy) antix-fbxkb which, according to its man page is v 0.6
ranting about misplaced priorities and the price of rice in China rather than providing a link to the requested source.
FWIW, there might be a newer version, available from debian, that you're not aware of.
v0.6-1.1
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://packages.debian.org/jessie/fbxkb"
linktext was:"https://packages.debian.org/jessie/fbxkb"
====================================
You might be wasting effort unnecessarily maintaining the (known buggy) antix-fbxkb which, according to its man page is v 0.6
Considering that I've sifted through code to chase down other"lesser, low priority" known bugs (mouse accel setting, kb selection setting), I'm shocked by the brusqueness of your reply.
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://metadata.ftp-master.debian.org/changelogs//main/f/fbxkb/fbxkb_0.6-1.1_changelog"
linktext was:"http://metadata.ftp-master.debian.org/c ... _changelog"
====================================
fbxkb (0.6-1.1) unstable; urgency=low
* Non-maintainer upload. (Patch by Mònica RamÃrez Arceda <monica@probeta.net>)
* eggtrayicon.c, fbxkb.c: Replace deprecated gdk_display and GDK_DISPLAY() with gdk_x11_get_default_xdisplay().
* Link to X11 to build with binutils-gold. (Closes: #554280)
-- Konstantinos Margaritis <markos@debian.org> Fri, 31 Jan 2012 13:46:19 +0200
-
fatmacPosts: 850
- Joined: 26 Jul 2012
#143
@skidoo
Seems to me BitJam gave you a link to the code source.
I don't think s/he 'went off on one', just busy trying to fix things so that 15 gets released on time.
__{{emoticon}}__
Seems to me BitJam gave you a link to the code source.
I don't think s/he 'went off on one', just busy trying to fix things so that 15 gets released on time.
__{{emoticon}}__
-
skidooPosts: 1,444
- Joined: 09 Feb 2012
#144
IceWM menu displays an icon for EVERY entry under Applications submenu.
Both in fluxbox and in JWM menus, entries for { Clipit, Gweled, HexChat, wpa-gui, ROXTerm } are displayed without icon.
So, what quirk do these particular .desktop files have in common? I couldn't find a commonality.
hexchat.desktop contains a strange stanza (I've never encountered any .desktop file
[Desktop Action SafeMode]
gweled.desktop and clipit.desktop do not explicitly state a file extension (e.g."Icon=gweled")
...but iceweasel.desktop shares this 'quirk' yet its icon still displays in all 3 menus
Both in fluxbox and in JWM menus, entries for { Clipit, Gweled, HexChat, wpa-gui, ROXTerm } are displayed without icon.
So, what quirk do these particular .desktop files have in common? I couldn't find a commonality.
hexchat.desktop contains a strange stanza (I've never encountered any .desktop file
[Desktop Action SafeMode]
gweled.desktop and clipit.desktop do not explicitly state a file extension (e.g."Icon=gweled")
...but iceweasel.desktop shares this 'quirk' yet its icon still displays in all 3 menus
-
skidooPosts: 1,444
- Joined: 09 Feb 2012
#145
fatmac, kudos for trying to keep the peace, but... the link provided ("the old code...") seems useless/irrelevant.
The binary for the"we fixed" newer code is contained in a differently-named package, 'antix-fbxkb'. Debian repos contain a relatively recent 'fbxkb'.
Differing package names suggest that either the left hand is unaware what the right hand is doing, or the code contained within each differs significantly.
The binary for the"we fixed" newer code is contained in a differently-named package, 'antix-fbxkb'. Debian repos contain a relatively recent 'fbxkb'.
Differing package names suggest that either the left hand is unaware what the right hand is doing, or the code contained within each differs significantly.
-
anticapitalista
Posts: 5,955
- Site Admin
- Joined: 11 Sep 2007
#146
git repo for fbxkb used in antiX is here.
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://github.com/antiX-Linux/fbxkb-antix"
linktext was:"https://github.com/antiX-Linux/fbxkb-antix"
====================================
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://github.com/antiX-Linux/fbxkb-antix"
linktext was:"https://github.com/antiX-Linux/fbxkb-antix"
====================================
-
SamKPosts: 1,028
- Joined: 21 Aug 2011
#147
Now Menu Manager (MM) has been ruled out from contributing to your reported matters that leaves three other suspects:
Unless the purpose of Update Menu has changed significantly from antiX-13.2, and my tests in antiX-14/15 when developing MM, currently its primary role during a session is to rebuild/refresh the menu only for the current window manager. Within a session it can be used to add an item to the menu. For example, after installing an app in a way that does not trigger the (new to 14/15) automated menu refresh routine, or after a user created .desktop file is manually placed in /usr/share/applications/[antix/].
Using Update Menu will not display an item created by Add Menu Item when it fails to automatically refresh the menu after that item .desktop file has been produced.
The main suspects for many of the matters in your reports are Add Menu Item + Remove Menu Item. I'm not 100% certain, but have reasonable levels of confidence, these have been broken in every iteration of the 14/15 development ISO.
When creating any menu item, MM can be used as a more user friendly alternative to Add Menu Item, provided you do not need the item to be displayed in the Applications menu. You have previously proven that MM reliably creates items in the Personal menu area. What might surprise you is that MM is able to do this for any GUI or CLI app irrespective of whether they currently have a .desktop file available in the system.
The following is an example of using MM to add wicd-curses to the Personal menu. This app is shipped in the 15-beta3 ISO without a .desktop file because it is usually started from the command line.
Step 1
Control Center-->Edit Menus
Select Personal when asked which menu to change
Select Add when asked whether to add or remove an item
Select Gcolor2 when asked to select an item to add
Change the name to WICD via Command Line when asked for the name to display in the menu
Change the name of the app to wicd-curses in the line asking to append parameters etc
Enable Tick to select an alternative icon...
Enable Tick to launch in a terminal
Choose Select Icon when prompted
Browse for and select your choice of icon e.g. /usr/share/pixmaps/network-config.xpm
Select Refresh when asked whether to refresh the menu or make another change
A window reports the update has been done.
Step 2
antiX Main Menu-->Personal
The section now contains an item named WICD via Command Line
Click on it and the wicd-curses app opens as expected
The above is to illustrate the flexibility and ease of use of MM. The logic behind placing the item in the Personal menu is relatively straightforward. The fact that someone is creating their own choice of menu item is essentially a personalization of their system, so it is placed in the Personal menu area.
OK it has now been confirmed that Menu Manager is working as designed in all respects. Because it is a new app to antiX, that confirmation will give confidence to users to try it for themselves.skidoo wrote:those additional tests produce expected results, both in non-persistent and persistent live session.
Now Menu Manager (MM) has been ruled out from contributing to your reported matters that leaves three other suspects:
- antiX-Menu-->Update Menu
- antiX Menu-->Applications-->Preferences-->Add Menu Item + Remove Menu Item
- User Error
Unless the purpose of Update Menu has changed significantly from antiX-13.2, and my tests in antiX-14/15 when developing MM, currently its primary role during a session is to rebuild/refresh the menu only for the current window manager. Within a session it can be used to add an item to the menu. For example, after installing an app in a way that does not trigger the (new to 14/15) automated menu refresh routine, or after a user created .desktop file is manually placed in /usr/share/applications/[antix/].
Using Update Menu will not display an item created by Add Menu Item when it fails to automatically refresh the menu after that item .desktop file has been produced.
The main suspects for many of the matters in your reports are Add Menu Item + Remove Menu Item. I'm not 100% certain, but have reasonable levels of confidence, these have been broken in every iteration of the 14/15 development ISO.
When creating any menu item, MM can be used as a more user friendly alternative to Add Menu Item, provided you do not need the item to be displayed in the Applications menu. You have previously proven that MM reliably creates items in the Personal menu area. What might surprise you is that MM is able to do this for any GUI or CLI app irrespective of whether they currently have a .desktop file available in the system.
The following is an example of using MM to add wicd-curses to the Personal menu. This app is shipped in the 15-beta3 ISO without a .desktop file because it is usually started from the command line.
Step 1
Control Center-->Edit Menus
Select Personal when asked which menu to change
Select Add when asked whether to add or remove an item
Select Gcolor2 when asked to select an item to add
Change the name to WICD via Command Line when asked for the name to display in the menu
Change the name of the app to wicd-curses in the line asking to append parameters etc
Enable Tick to select an alternative icon...
Enable Tick to launch in a terminal
Choose Select Icon when prompted
Browse for and select your choice of icon e.g. /usr/share/pixmaps/network-config.xpm
Select Refresh when asked whether to refresh the menu or make another change
A window reports the update has been done.
Step 2
antiX Main Menu-->Personal
The section now contains an item named WICD via Command Line
Click on it and the wicd-curses app opens as expected
The above is to illustrate the flexibility and ease of use of MM. The logic behind placing the item in the Personal menu is relatively straightforward. The fact that someone is creating their own choice of menu item is essentially a personalization of their system, so it is placed in the Personal menu area.
-
skidooPosts: 1,444
- Joined: 09 Feb 2012
#148
Sam, I now understand/agree that the sole"MM-related issue" I've reported (beyond wishlist/suggestion items) is this:
an entry labeled"Retry" (in fluxbox, or quirky rectangle in icewm) is displayed to Personal submenu when it becomes empty
Beyond the scope of MenuManager, here are a few additional (new) points of testing feedback:
suggestion: For sake of continuity, change controlCentre"Edit menus" label to"Edit menus (MenuManager)"
suggestion: To eliminate confusion,"Add Menu Item" (add-desktop script) should be revised to either
a) call"Update Menus" before exiting, or b) provide onscreen notice to user, advising that a manual"Update Menus" operation is necessary
observation-slash-suggestion: After recently revisiting antiX 13.1 (for sake of comparison), the older, compact (smaller icons) layout does seem more comfortable.
Comfortable?"No nonsense, power-packed"... compared to feeling like 'geez, all this could/should fit in fewer notebook tabs. 8 per tab is a PITA to hunt/find something'.
an entry labeled"Retry" (in fluxbox, or quirky rectangle in icewm) is displayed to Personal submenu when it becomes empty
Beyond the scope of MenuManager, here are a few additional (new) points of testing feedback:
suggestion: For sake of continuity, change controlCentre"Edit menus" label to"Edit menus (MenuManager)"
suggestion: To eliminate confusion,"Add Menu Item" (add-desktop script) should be revised to either
a) call"Update Menus" before exiting, or b) provide onscreen notice to user, advising that a manual"Update Menus" operation is necessary
observation-slash-suggestion: After recently revisiting antiX 13.1 (for sake of comparison), the older, compact (smaller icons) layout does seem more comfortable.
Comfortable?"No nonsense, power-packed"... compared to feeling like 'geez, all this could/should fit in fewer notebook tabs. 8 per tab is a PITA to hunt/find something'.
-
skidooPosts: 1,444
- Joined: 09 Feb 2012
#149
Many hands make light work...
Thank you. Although my skills are limited, the prospect of fixing (vs reporting) bugs is appealing.anticapitalista wrote:git repo for fbxkb used in antiX is here.
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"https://github.com/antiX-Linux/fbxkb-antix"
linktext was:"https://github.com/antiX-Linux/fbxkb-antix"
====================================
Many hands make light work...
-
SamKPosts: 1,028
- Joined: 21 Aug 2011
#150
antiX Control Center
Way back to the opening post of this topic
antix-15-beta3-available-t5638.html
Since the early days of the 13 series we have been making steady progress in rationalising the menu in conjunction with Control Center (CC). This latest incarnation is very much out-of-step with the previous work.
Up to now the work had progressed within a pattern:
Way back to the opening post of this topic
antix-15-beta3-available-t5638.html
I fully agree with the last part, in fact overkill is probably and intentional, toungue-in-cheek, understatement.anticapitalista wrote:more options added to antiX control centre. (Probably overkill)
Since the early days of the 13 series we have been making steady progress in rationalising the menu in conjunction with Control Center (CC). This latest incarnation is very much out-of-step with the previous work.
Up to now the work had progressed within a pattern:
- Items in the menu do not duplicate items in the CC
- Where appropriate, items in the CC may have a corresponding .desktop file which is not displayed in the menu. This gives the user an option to show it in the menu (perhaps now via Menu Manager)
- Items in the CC fall into three broad categories
Items which perform setup or configurations for other apps or users
Items which perform infrequently conducted"system level" tasks
Items which a non technical user might reasonably perceive and expect to be in a single, central, location
- Items that are best suited to the CC being shown in the menu
- Items that are best suited to the menu being shown in the CC
- Plenty of duplicated items in both menu and CC