GnoMenu 2

Registered by technoshaun

This blueprint has been superseded. See the newer blueprint "Gnomenu 3.0 specs" for updated plans.

GnoMenu 2.0 Blueprint

Synopsis: The GnoMenu 1.X series has proven extremely popular and its success has been measured by the fact that Gnome-Look has created a sub section for GnoMenu Themes and that GnoMenu has been selected to be included into the Ubuntu repositories starting with Jaunty Jackalope (9.04)

GnoMenu is a serious attempt to bring eye candy abilities to the Gnome Menu. Based on “Vista Start Menu” by Chris Hughes. It was picked up for further development by Helder Fraga. Chris Hughes has joined the GnoMenu team.

Helder has since forked the project and renamed it to GnoMenu. Its current incarnation is 1.9.9.

Anton Sudak, whom has also recently joined the GnoMenu Team, and is now the GnoMenu art team leader created the new layout design with his Black White Theme. This new layout brings a fresh new look to GnoMenu and is the first one to deviate from the Vista Menu look. Others are now being developed as well.

GnoMenu is released under the GNU/GPL Version 3 software license.

Under Helder's development GnoMenu has had many serious bugs, annoyances and issues fixed. Though there are more to find and fix GnoMenu is maturing rapidly and proving to be a powerful menu applet in its own right.

GnoMenu is written in Python, which will allow it to be cross platform compatible in the future if desired.

The GnoMenu 1.X series was written in Python 2.5. Python 3.0 was released and is not backwards compatible with Previous Python releases. Because of this the GnoMenu 2.0 Series must be coded in Python 3 series to ensure usability in future Linux releases.

The GnoMenu 2 series will be capable of new features and abilities thanks to advances with Python 3.

This includes features that required more of a work around solution than actual ability, such as:

Translations; GnoMenu 1 had to have its own language handling files to translate terms in the Menu Layout. This is cumbersome and creates bloat. Python 3 now handles the use of local files much better and GnoMenu 2 will take advantage of this. Thus the menu layout can easily be translated via the use of local files to the users native language.

Following the practices set in Advanced Gnome Menu by Marco Mosconi, we should make each menu listing a separate plugin. This will allow for tab menus and other advanced features bringing GnoMenu new abilities and features previously unsupported in the GnoMenu 1 series. These features will allow Theme creators to use Tab based menu designs or other unique methods to open menu panels within GnoMenu. Ideally GnoMenu 2 will allow many different designs that can take advantage of new features in any number of possible layouts and combinations. By following Marco's example of making each menu panel a plugin we begin the process of opening new options and features to Theme Creators.

Another feature that should be consider is the ability to list directories in the panel. (list of advantages and disadvantages needs to be created)

Blueprint information

Status:
Complete
Approver:
Helder Fraga
Priority:
High
Drafter:
technoshaun
Direction:
Approved
Assignee:
GnoMenu Team
Definition:
Superseded
Series goal:
Accepted for trunk
Implementation:
Implemented
Milestone target:
None
Started by
technoshaun
Completed by
technoshaun

Related branches

Sprints

Whiteboard

Add a custom command settings feature for Gnomenu2, a GUI for putting custom commands and paths to GnoMenu for individual Icon shortcuts so that users can easily define access and functions without having to mess with the XML code for the individual theme. However, theme creators should be allowed a method to lock some Icons so that users cannot change the functions or paths, to avoid possible design issues with the theme. (Implemented)

Create a User Options Preference in the GnoMenu Preferences Dialog that allows users to set definable parameters such as whether or not the Super Key should be active in GnoMenu (Implemented)

navigation by arrows as in links or mc is much more convenient than selecting item and press enter. (Implemented)

Reinstate recently used items to the menu. This is a highly useful feature that exists in nearly all menu systems. Also a method to allow users to clear this list needs to be implemented. (Implemented)

Use or code a new keybindings library. Mono is extremely controversial at this time and there is major discussion that it should be removed from Gnome entirely. This means that it most likely will. Dependency even on the bit Mono may put GnoMenu at risk. (Implemented)

With compiz fusion, GnoMenu acts like a window with opening and closing effects. Fix Gnomenu giving it it's own menu effects independent of compiz. (Implemented)

GnoMenu currently requires that Icons be included as part of the theme. This often creates issues when the system Icon theme does not match. An example would be GnoMenu using a Tango theme when the system is using Hydroxygen Icons. A method should be developed that allows GnoMenu to use the system Icons instead. (implemented)

Python 3.0 touts many improvements over Python 2.5 and with Python 3.0 now released creating a version of GnoMenu that depends on Python 3.0 simply makes sense since it is most likely Python 2.5 will be deprecated soon. (Automaticly Implemented)

Add sound effects. Sounds should playing on opening/closing menu. GnoMenu would use themes created for it or system sound theme. NOTE: Good feature idea but users will need a way to turn off this feature. Not everyone wants, or can use, menu event sounds. (Implemented)

Develop a method to quick access to web browser bookmarks. Have GnoMenu read Firefox's (or whatever the default browser is) bookmarks and important them into a menu listing. Helder has noted this would be hard to implement and using pre-existing works (import and converting for GnoMenu) may provide this ability. (Implemented)

In Gnome 3.0 applets are not used so in preparation to move to a different desktop environment, we added a backend engine that uses Xml to store settings when gconf isn't available, this is in preparation to port gnomenu to xfce.
Also a AWN applet was created to run GnoMenu directly from AWN dock. (implemented)

GnoMenu should implement tool tips for button, icon and tab hovers. The themer needs to be responsible for what information is in the tool tip pop ups. Also a method to disable them needs to be in the GnoMenu preferences interface. (Implemented)

Allow GnoMenu to use a background image in the program list menu (not possible in Gtk).

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.