Bug 193781 - iconsistent naming: menu vs. application launcher
Summary: iconsistent naming: menu vs. application launcher
Status: RESOLVED FIXED
Alias: None
Product: plasma4
Classification: Plasma
Component: widget-kickoff (show other bugs)
Version: unspecified
Platform: openSUSE Unspecified
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-23 17:48 UTC by Maciej Pilichowski
Modified: 2010-06-24 23:15 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Maciej Pilichowski 2009-05-23 17:48:09 UTC
Version:            (using KDE 4.2.2)
Installed from:    SuSE RPMs

Steps to reproduce:
1) go to panel
2) click RMB on KMenu icon, read
menu editor
switch to kickoff menu style
application launcher menu settings
...

It is really confusing. I opt for keeping name KMenu or KDE system menu, because application launcher is simply inaccurate (shutdown system has little to do with launching anything, so it is in a way as much inaccurate as Start->Shutdown in MS-Windows).

However the main point (aside from my preference) is making consistent naming.
Comment 1 Maciej Pilichowski 2009-05-23 17:49:45 UTC
PS. Another reason for keeping "KMenu", application launcher has to be translated, but KMenu (like Konqueror, Dolphin, KMail) is not translated. It helps users to communicate.

Minor things: its shorter, and it is well known name.
Comment 2 Pino Toscano 2009-05-23 18:30:28 UTC
Just a translator's note: "KMenu" could had been translated in KDE 3, and some teams did it like it was "K Menu".
Comment 3 Aaron J. Seigo 2009-06-11 01:06:11 UTC
it's not a menu and "k" says precisely nothing about it.
Comment 4 Maciej Pilichowski 2009-06-11 13:29:07 UTC
Aaron, misunderstanding, this report is not about forcing "KMenu" name, but about consistent naming -- if this is not menu, then please remove "menu" label (because as you say, it is not menu).
Comment 5 Aaron J. Seigo 2009-06-11 18:49:37 UTC
you mean the "Menu Editor" entry? well, that's what it is: it edits the menu of applications. 

the text could probably be changed to one of Application Menu Editor, Application Entries Editor, Applications Editor ... *shrug* personally i prefer the latter. can't be changed for 4.3 as we're in string freeze now.
Comment 6 Maciej Pilichowski 2009-06-11 19:18:46 UTC
> you mean the "Menu Editor" entry? 

Yes, this too. In KDE 4.2.4 there are 3 terms that relates to the same object -- Kickoff, Menu Editor, Application Launcher.

> well, that's what it 
> is: it edits the menu of applications.

Ok, _I_ know :-)

> the text could probably be changed to one of Application Menu
> Editor, Application Entries Editor, Applications Editor ... *shrug*
> personally i prefer the latter. can't be changed for 4.3 as we're
> in string freeze now.

The basic question is what it is -- if "Application Launcher" (*) then all labels should be derivatives of it, like "Application Launcher menu style", "edit Application Launcher menu" and so on.

(*) I am not saying I opt for "application launcher".
Comment 7 Aaron J. Seigo 2009-06-11 19:40:24 UTC
they are all permutations of "*Application Launcher*" except the editor entry; the action to switch to the classic menu style has wording chosen specifically to make it clear what's happening, which is more important than (what would amount to an artifice of) consistency with other entries.

so this boils down to changing Menu Editor to something that fits the theme, such as Applications Editor.
Comment 8 Maciej Pilichowski 2009-06-11 20:49:46 UTC
Style switch -- one thought. Currently it is bi-switch, would it be more flexible (and consistent :-) ), to switch between installed app.launchers? So it could be like menu:
app. launcher menu style >

and in submenu user would get the list of app. launchers (installed). This would remove the need to use product names in the main context menu.
Comment 9 Aaron J. Seigo 2010-06-24 23:15:16 UTC
i've fixed this in my local copy, will be part of 4.6 (and in trunk when 4.6 opens for dev)