Difference between revisions of "Features/Replace GtkMenu"
(Add Basic Template) |
|||
| Line 21: | Line 21: | ||
* Email: sam@sl.o | * Email: sam@sl.o | ||
| + | * I do not own this feature, I just made the wiki page. | ||
== Current status == | == Current status == | ||
| Line 43: | Line 44: | ||
==UI Design== | ==UI Design== | ||
===Resources=== | ===Resources=== | ||
| − | + | [[File:Change-default-app-android-31.png|none|thumb|Android 4.x]] | |
| + | [[File:GNOME Modal Gedit.png|none|thumb|GNOME 3.16.2]] | ||
Revision as of 20:11, 23 May 2015
There are comments (in italics) providing guidance to fill out each section, see also the Feature Policy Page for a more detailed explanation of the new-feature process. Copy the source to a new page named Features/Your Feature Name before making changes! DO NOT EDIT THIS TEMPLATE.
Summary
Get rid of Gtk.Menu based palettes - use a modal.
Owner
- Name: Sam
- Email: sam@sl.o
- I do not own this feature, I just made the wiki page.
Current status
- Targeted release: 0.108
- Last updated: 24/May/2015
- Percentage of completion: 0%
Detailed Description
GtkMenu palettes (namely, clipboard and journal) are hard to maintain and theme. They should be removed.
The only reason they are used now is because they support nesting of menus. However, a modal could be used instead.
Benefit to Sugar
This will make sugar easier to maintain and reduce the amount of visual bugs.
Scope
Adding a modal should be a quick process. It would probably only involve:
- Adding a modal primative to `sugar3.graphics.sleectormodal`
- Migrating the 2 users of the GtkMenu to the modal and GtkWindow based palettes
UI Design
Resources
How To Test
Features/Replace GtkMenu/Testing
User Experience
If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice.
Dependencies
What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, does your feature depend on completion of another feature owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time? Other upstream projects like Python?
Contingency Plan
If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "None necessary, revert to previous release behaviour." Or it might not. If your feature is not completed in time, we want to assure others that other parts of Sugar will not be in jeopardy.
Documentation
Is there upstream documentation on this feature, or notes you have written yourself? Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.
Release Notes
The Sugar Release Notes inform end-users about what is new in the release. An Example is 0.84/Notes. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the release team and shipped with the release.