By default, Bugzilla does not search the list of RESOLVED bugs.
You can force it to do so by putting the upper-case word ALL in front of your search query, e.g.: ALL tdelibs
We recommend searching for bugs this way, as you may discover that your bug has already been resolved and fixed in a later release.

Bug 977

Summary:	Avoiding potential menu clutter and conflicts with KDE3 and KDE4
Product:	TDE	Reporter:	Darrell <darrella>
Component:	tdelibs	Assignee:	Timothy Pearson <kb9vqf>
Status:	RESOLVED FIXED
Severity:	critical	CC:	bugwatch, darrella
Priority:	P1
Version:	R14.0.0 [Trinity]
Hardware:	Other
OS:	Other
Compiler Version:		TDE Version String:
Application Version:		Application Name:
Attachments:	Proposed menu changees

Description Darrell 2012-04-22 17:36:29 CDT

This bug report is created to separate tasks originally described in bug report 892.

1. There exists no method to distinguish TDE and KDE3 apps in the TDE menu when both desktops are installed concurrently.

2. The current method of appending "[KDE4]" to KDE4 menu items (kservice.cpp) creates a cluttered menu system. This method does distinguish KDE4 items but the clutter creates a menu that is difficult to read.

Discussion

Although Trinity developers do not officially support KDE3, users can still install both. For testers this is a desired setup because KDE3 will always remain a benchmark for testing Trinity.

The method used to distinguish KDE4 apps by appending "[KDE4]" to the menu description could be used for KDE3 apps too. Adding such a method first requires resolving bug report 892, which addresses where Trinity desktop files are installed. Currently Trinity desktop files are installed to $PREFIX/applications/kde, which should be changed to a proposed $PREFIX/applications/tde. As KDE4 desktop files are installed to $PREFIX/applications/kde4, the old default location of $PREFIX/applications/kde for KDE3 would remain unaffected by both Trinity and KDE4.

Rather than append menu items with [KDE3] or [KDE4], a novel idea, perhaps a cleaner solution is to provide KDE3 and KDE4 desktops with their own top level menu. The [KDE3] or [KDE4] appendage creates too cluttered of a menu. With a top level menu, the KDE3 and KDE4 menus that come packaged with those desktop could be used separately and not clutter the Trinity menu. As all of the menu related items in Trinity have been renamed in previous GIT merges to avoid conflicts with the other desktops (read Comment 4), this option should be doable and is more palatable than appending with [KDE3] or [KDE4].

Comment 1 Darrell 2012-04-22 17:40:39 CDT

Reference in original comment for Comment 4 is to  bug report 892 (http://bugs.pearsoncomputing.net/show_bug.cgi?id=892#c4).

Comment 2 Darrell 2012-06-06 22:09:31 CDT

I developed an xdg menu system that I am testing. The new menu system retains the "[KDE4]" appendage but moves all KDE4 menu items to separate menus. I'll post more soon to the developer's mail list. The new menu seems to be working well.

Supporting KDE3 in the Trinity menu is contradictory because running KDE3 apps inside the Trinity environment is a library-loading nightmare. I got confused in my original request with wanting to install both desktops on the same system for comparative testing purposes (no reboots, no VMs, just use two different login accounts). Doing so does not and should not include menu support. An appropriate solution is to ensure no KDE3 menu items appear anywhere in the Trinity menu. KDE3 and Trinity may be concurrently installed on the same system using a different $PREFIX, but the menu systems of each desktop needs to ignore the other desktop. KDE3 has no knowledge of Trinity and that menu needs no editing.

I haven't yet worked out common menu system where KDE4 apps populate correctly but KDE3 apps are ignored. More than likely, those few who want to run KDE3 along with Trinity will have to apply a special menu that is not supported officially by Trinity developers. We could post something like that to the wiki.

Comment 3 Darrell 2012-06-13 19:27:27 CDT

Update: I now have a remedy to resolve this bug report. I am testing the changes. I expect to post patches Real Soon Now :-) and then ask others to test.

I also have a way to create a menu with no KDE3/4 menu items at all, when either desktop is installed concurrently with Trinity. I am unlikely to offer that solution as a project patch. Likely I'll post that fix to my web site or the wiki.

Comment 4 Darrell 2012-06-19 20:27:41 CDT

Created attachment 683 [details]
Proposed menu changees

This attachment is not a patch but a tar.gz. This will allow more people to help test because a patch set requires build all affected packages. Details for installing and explanations will be posted in the developer's mail list, but basically:

Unpack and install the directories files to $PREFIX/share/desktop-directories. These files are unique and do not overwrite anything. They are easy to identify because all but one have a "kde-" prefix rather than "tde-" prefix.

Unpack and install the desktop_files to $PREFIX/share/applications/tde.

Install the three applications.menu-* files to $SYSCONFDIR/xdg/menus.

Testing is easy: copy the desired applications.menu* to the same location as applications.menu (overwrite).

These *.desktop files won't work in 3.5.13 because they presume the latest XDG updates.

Comment 5 Darrell 2012-06-19 20:36:24 CDT

Correction: there are only two menu files in the tar.gz collection.

Comment 6 Darrell 2012-06-26 11:06:09 CDT

Patches pushed to GIT in the following commits:

tdelibs: 787bd794
tdebase: 0140d761
tdepim: 013a6831
tdeaddons: 1a930d38
tdeutils: f4827475
koffice: e5e1e49d

I'll leave the bug report open for a while to accomodate problems or requested changes.

Comment 7 Darrell 2012-06-26 11:22:19 CDT

tdebase: 0140d761 and f42090e9

Comment 8 Darrell 2012-08-14 08:22:04 CDT

No comments or complaints for several weeks. Closing as resolved.