Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
panel-hig [2008/01/06 02:44] – ongardie | panel-hig [2008/03/03 05:51] – ongardie | ||
---|---|---|---|
Line 20: | Line 20: | ||
===== General ===== | ===== General ===== | ||
+ | |||
+ | |||
+ | |||
Line 25: | Line 28: | ||
==== Tooltips ==== | ==== Tooltips ==== | ||
* [rfc] Indentation for sublevel entries should be: 2 spaces? 4 spaces? \t? | * [rfc] Indentation for sublevel entries should be: 2 spaces? 4 spaces? \t? | ||
- | * //ongardie 2007/12/18 05:51 Screenshots would be helpful [added below] // | ||
* //ongardie 2007/12/21 01:51 I think I like 2 spaces the best, personally. // | * //ongardie 2007/12/21 01:51 I think I like 2 spaces the best, personally. // | ||
+ | * With GTK+2.12 you can add widgets in a tooltip, and therefore labels with markups, for bold for example. | ||
+ | * Or maybe a \t with a configurable (plus sensible default) tab width? -- // | ||
Line 37: | Line 41: | ||
2 spaces: | 2 spaces: | ||
{{http:// | {{http:// | ||
+ | |||
Line 47: | Line 52: | ||
Interface guidelines regarding the right-click menu provided by the panel. | Interface guidelines regarding the right-click menu provided by the panel. | ||
- | * [rfc] Help/About? | + | * [rfc] Help? |
* //ongardie 2007/12/18 05:51 The current trend is to not include these at all but to put information on the plugin web site. // | * //ongardie 2007/12/18 05:51 The current trend is to not include these at all but to put information on the plugin web site. // | ||
- | * // fabian 2007/12/18 22:47 GMT Well, some plugins just run the opposite trend: Disk Performance Monitor, Quiklauncher, | + | * [snip] |
- | * I wouldn' | + | |
* Some plugins have a dialog with a Help button which opens a webpage. | * Some plugins have a dialog with a Help button which opens a webpage. | ||
* To clarify, Mike meant to say they display a Help button in their preferences/ | * To clarify, Mike meant to say they display a Help button in their preferences/ | ||
- | * The three plugins fabian pointed out just show an About item in their context menu. Each of those about dialogs is rather poor, IMHO. Help has to be added manually to the context menu, and I agree with Mike in that its almost always unnecessary. I think the guideline here should be " | + | * Help has to be added manually to the context menu, and I agree with Mike in that its almost always unnecessary. I think the guideline here should be "Help context menu items are discouraged. A Help button inside the properties dialog is optional (see ...)" --- // |
+ | |||
+ | * [rfc] About? | ||
+ | * //ongardie 2007/12/18 05:51 The current trend is to not include these at all but to put information on the plugin web site. // | ||
+ | * // fabian 2007/12/18 22:47 GMT Well, some plugins just run the opposite trend: Disk Performance Monitor, Quiklauncher, | ||
+ | * The three plugins fabian pointed out [...] show an About item in their context menu. Each of those about dialogs is rather poor, IMHO. I think the guideline should be "About menu items are discouraged." --- // | ||
==== Menus ==== | ==== Menus ==== | ||
Line 59: | Line 68: | ||
* [draft] Optionally, display a title \\ If you would like to add a title to your menu, set it insensitive and bold, and place it on top of the menu followed by a separator \\ {{http:// | * [draft] Optionally, display a title \\ If you would like to add a title to your menu, set it insensitive and bold, and place it on top of the menu followed by a separator \\ {{http:// | ||
- | * I'm not convinced I like this (and neither is Mike). Perhaps we should discourage menu titles instead. --- // | + | * I'm not convinced I like this. Perhaps we should discourage menu titles instead. --- // |
+ | |||
+ | |||
+ | |||
+ | |||
==== Settings Dialog ==== | ==== Settings Dialog ==== | ||
- | | + | Interface guidelines regarding preferences/ |
+ | |||
+ | | ||
+ | |||
+ | * [draft] It is highly encouraged for settings modifications to take effect immediately. If this is not at all possible, it should be made clear to the user that settings modifications will take effect when the properties dialog is closed. | ||
+ | * The sensitive part can be dropped, it just works if the dialog is set modal (see [[http:// | ||
+ | * "and the plugin' | ||
+ | * Indeed in Xfce it is very common to apply changes immediately unless you are making more complex changes. Please avoid insensitivity or modality where possible. --- kalikiana 2008/01/26 17:06 | ||
+ | * Reworded draft to emphasize this point. | ||
+ | * I think this one's pretty solid now. Let's allow until 2008/03/16 (two weeks) for further debate. If there are no more negative comments, the " | ||
- | * [draft] **Set sensitivity of panel plugin to false** \\ Plugins that don't may be touched while the properties dialog is open may set the sensitivity of their widgets to false during that time. | ||
Line 90: | Line 112: | ||
* xfdesktop (4.4.2 and trunk) | * xfdesktop (4.4.2 and trunk) | ||
* places (1.0 and trunk) | * places (1.0 and trunk) | ||
- | * If there are no objections by 2008-01-19 (two weeks from now), "[draft]" | + | * I don't think the box should have a border/ |
- | * [draft] The image should | + | * Are there any plugins that do that now? --- // |
+ | |||
+ | * [draft] The image inside the button | ||
+ | GdkPixbuf *pixbuf; | ||
+ | |||
+ | size = xfce_panel_plugin_get_size (panel_plugin); | ||
+ | | ||
+ | |||
+ | icon_theme = gtk_icon_theme_get_default (); | ||
+ | pixbuf = gtk_icon_theme_load_icon (icon_theme, | ||
+ | if (G_UNLIKELY (NULL == pixbuf)) | ||
+ | return; | ||
+ | gtk_image_set_from_pixbuf (GTK_IMAGE (panel_plugin-> | ||
+ | g_object_unref (G_OBJECT (pixbuf)); | ||
+ | </ | ||
+ | * Note: this is more a problem of what to do with the size-changed signal | ||
+ | * Should we really have code snippets in here? And I seem to remember someone (maybe Brian) telling you a better way than hard-coding the 2... --- // | ||
* Use a short label to conserve space | * Use a short label to conserve space | ||
* On the label, use capitalization like a title (e.g., "My Button" | * On the label, use capitalization like a title (e.g., "My Button" | ||
Line 103: | Line 142: | ||
examples: verve, dict(ionary) | examples: verve, dict(ionary) | ||
+ | |||
+ | |||
Line 133: | Line 174: | ||
* {{http:// | * {{http:// | ||
* //ongardie 2007/12/21 00:55 Yes, that's a nice effect. Would it work for any monitor? // | * //ongardie 2007/12/21 00:55 Yes, that's a nice effect. Would it work for any monitor? // | ||
- | * The box should have a default border (1px). | + | * [draft] |
* [draft] The box should have a spacing of 2px. | * [draft] The box should have a spacing of 2px. | ||
* //kalikiana 2007/12/17 19:39 Space between labels was discussed before and the argument against it was that you can add space via ' | * //kalikiana 2007/12/17 19:39 Space between labels was discussed before and the argument against it was that you can add space via ' | ||
Line 151: | Line 192: | ||
* [draft] use a -90° angle for monitor labels in horizontal panels and 0° angle for monitor labels in vertical panels. That might save a lot of space. | * [draft] use a -90° angle for monitor labels in horizontal panels and 0° angle for monitor labels in vertical panels. That might save a lot of space. | ||
* //ongardie 2007/12/14 06:17 I entirely agree. To clarify, the bar should be vertical and progress upwards for horizontal panels, and it should be horizontal and progress rightwards for vertical panels. // | * //ongardie 2007/12/14 06:17 I entirely agree. To clarify, the bar should be vertical and progress upwards for horizontal panels, and it should be horizontal and progress rightwards for vertical panels. // | ||
+ | * Do the major plugins work this way now? --- // | ||
===== Class G: Grid ===== | ===== Class G: Grid ===== |