Re: [Cooker] [Bug 5566] [kdebase] New: use of proprietary menu location defeats the purpose of a standard Linux desktop
On Thursday 11 September 2003 23:01, Alex Chudnovsky wrote: > On Thursday 11 September 2003 23:31, Buchan Milne wrote: > > Until then, it is impossible to satisfy everyone completely. > > It is. Switch to the exact Debian way - add entries to KDE menu, > don't substitute it. Mandrake already use Debian menu. When something add a menu file for kde, does it appear on gnome ? No. Does it appear on fluxbox ? And, as said before, you can change it with menudrake. > It's not only for third party applications, it's > for installing from source too. It's not always possible to find > Mandrake-specific RPM for some KDE application, especially for a > fresh one. Then you should learn how menu work. http://qa.mandrakesoft.com/twiki/bin/view/Main/MandrakeMenu It is very easy to add a menu file. You can even add it in your home, in ~/.menu -- Mickaël Scherer
Re: [Cooker] [Bug 5566] [kdebase] New: use of proprietary menu location defeats the purpose of a standard Linux desktop
On Thursday 11 September 2003 23:31, Buchan Milne wrote: > On Thu, 11 Sep 2003, [adilz] wrote: > > The menu location should be standardized and the > > KDE default location can be used by all Linux distributions. > > And what about users who use GNOME, WindowMaker, IceWM? Or, do you think > it is more feasible to support 11 desktops/window managers instead of one > menu standard (currently shared by Debian and Mandrake)? > My second computer has Debian installed. The main difference is that Debian DOES NOT SUBSTITUTE the original KDE menu, but rather ADDS to it. > > If not, third > > party software installers will not create links in the KDE "start" menu. > > Tough. The use of menudrake is covered in the documentation in the distro. > OK, so the "third party" installers should use "menudrake" in case of Mandrake, Debian menu system in case of Debian, regular KDE menu system in case of hell knows what... Why do they need all this headache, if it's possible just to use the regular KDE menu system, and let users of some non-regular distribution cope with their problems themselves? > > Does it install menus for the other 11 window managers avaialble in the > distribution. > That's the root of the problem. Freedesktop.org standards are not ready yet, but once they are, the policy should be simple - any desktop that doesn't support these standards, just doesn't get included into the distribution, or is included as unsupported. > > I would strongly suggest using the same location as KDE does for menus. > > Mandrake can add items and folders to that standard location and build > > the applnk-mdk menus there. > > And how do you propose ensuring that these menus do not get removed when > the new ones are rebuilt? > And how Debian does ensure? That's exactly what it does. > Sorry, but the problem is upstream. All the desktops should support the > standards for menus as specified int he freedesktop.org specifications. > Agree completely. > Until then, it is impossible to satisfy everyone completely. It is. Switch to the exact Debian way - add entries to KDE menu, don't substitute it. It's not only for third party applications, it's for installing from source too. It's not always possible to find Mandrake-specific RPM for some KDE application, especially for a fresh one. > Mandrake > provides easy to use solutions for both strategies, but defaults to using > a single consistent menu across desktops. If you install so much software > that it is such a waste of your time to create menu entries, swap to using > the original menus using menudrake. > > @resolution=invalid -- Regards, Alex Chudnovsky e-mail : [EMAIL PROTECTED] ICQ : 35559910
Re: [Cooker] [Bug 5566] [kdebase] New: use of proprietary menu location defeats the purpose of a standard Linux desktop
On Thu, 11 Sep 2003, [adilz] wrote: > Mandrake has used a menu links location (/usr/share/applnk-mdk) that is > different from the default KDE menus (/usr/share/applnk). If the user doesn't change the default, by running menudrake, and changing to using the original menus. Have you tried that? > This is a major issue and could relegate desktop Linux to the wastebasket if > not standardized upon. Well, even worse is the fact that by default, the menus in the two competing default desktops are totally inconsistent, and that they cannot be edited confortably and have both desktops reflect the changes. The menu system works around this deficiency. >No Linux distribution should expect third party > developers to create different versions of their installers to take care of all > the distributions out there. Such developers are few and far between, Mandrakesoft provides packages for the majority of the products the majority of the user base uses, and the community supports the users of proprietary software (in how to add entries to the menu). > The menu location should be standardized and the > KDE default location can be used by all Linux distributions. And what about users who use GNOME, WindowMaker, IceWM? Or, do you think it is more feasible to support 11 desktops/window managers instead of one menu standard (currently shared by Debian and Mandrake)? > If not, third > party software installers will not create links in the KDE "start" menu. Tough. The use of menudrake is covered in the documentation in the distro. > > I verified this with CodeWarrior 6 and there were no links created in the > Mandrake menus. Links were however, correctly created in the default KDE menu > path. Installing OpenOffice after downloading from the OpenOffice.org site also > does the same. Does it install menus for the other 11 window managers avaialble in the distribution. > I would strongly suggest using the same location as KDE does for menus. > Mandrake can add items and folders to that standard location and build the > applnk-mdk menus there. And how do you propose ensuring that these menus do not get removed when the new ones are rebuilt? Sorry, but the problem is upstream. All the desktops should support the standards for menus as specified int he freedesktop.org specifications. Until then, it is impossible to satisfy everyone completely. Mandrake provides easy to use solutions for both strategies, but defaults to using a single consistent menu across desktops. If you install so much software that it is such a waste of your time to create menu entries, swap to using the original menus using menudrake. @resolution=invalid -- |Registered Linux User #182071-| Buchan MilneMechanical Engineer, Network Manager Cellphone * Work+27 82 472 2231 * +27 21 8828820x121 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7 * Please click on http://www.cae.co.za/disclaimer.htm to read our e-mail disclaimer or send an e-mail to [EMAIL PROTECTED] for a copy. *
[Cooker] [Bug 5566] [kdebase] New: use of proprietary menu location defeats the purpose of a standard Linux desktop
http://qa.mandrakesoft.com/show_bug.cgi?id=5566 Product: kdebase Component: kdebase Summary: use of proprietary menu location defeats the purpose of a standard Linux desktop Product: kdebase Version: 3.1.3-74mdk Platform: PC OS/Version: All Status: UNCONFIRMED Severity: normal Priority: P2 Component: kdebase AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] Mandrake has used a menu links location (/usr/share/applnk-mdk) that is different from the default KDE menus (/usr/share/applnk). This is a major issue and could relegate desktop Linux to the wastebasket if not standardized upon. No Linux distribution should expect third party developers to create different versions of their installers to take care of all the distributions out there. The menu location should be standardized and the KDE default location can be used by all Linux distributions. If not, third party software installers will not create links in the KDE "start" menu. I verified this with CodeWarrior 6 and there were no links created in the Mandrake menus. Links were however, correctly created in the default KDE menu path. Installing OpenOffice after downloading from the OpenOffice.org site also does the same. I would strongly suggest using the same location as KDE does for menus. Mandrake can add items and folders to that standard location and build the applnk-mdk menus there. -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are on the CC list for the bug, or are watching someone who is.
