Xfce Wiki

Sub domains
 

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision
Previous revision
Last revisionBoth sides next revision
panel-hig [2008/01/06 02:30] ongardiepanel-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.  --- //[[mmassonnet@gmail.com|Mike Massonnet]] 2008/01/06 07:39//
 +    * Or maybe a \t with a configurable (plus sensible default) tab width? -- //anonymous//
  
  
Line 37: Line 41:
 2 spaces: 2 spaces:
 {{http://mitglied.lycos.de/timshome/download/xfce4/sensors-tooltip.png}} {{http://mitglied.lycos.de/timshome/download/xfce4/sensors-tooltip.png}}
 +
  
  
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, Genmon. // +    * [snip] The plugins are simple to use, usually the help is helpless.  We do keep stuff on the goodies website like summary, documenation, latest version, …  --- //[[mmassonnet@gmail.com|Mike Massonnet]] 2007/12/30 05:32//
-    * I wouldn't say that just because 3 plugins are providing quick help that we should annoy every devs freedom to add something like **that**.  The plugins are simple to use, usually the help is helpless.  We do keep stuff on the goodies website like summary, documenation, latest version, …  --- //[[mmassonnet@gmail.com|Mike Massonnet]] 2007/12/30 05:32//+
     * Some plugins have a dialog with a Help button which opens a webpage.  I think this is best you can do in your plugins.  --- //[[mmassonnet@gmail.com|Mike Massonnet]] 2008/01/02 07:37//     * Some plugins have a dialog with a Help button which opens a webpage.  I think this is best you can do in your plugins.  --- //[[mmassonnet@gmail.com|Mike Massonnet]] 2008/01/02 07:37//
       * To clarify, Mike meant to say they display a Help button in their preferences/properties dialog. See battery monitor or clipman.  --- //[[ongardie@gmail.com|Diego Ongaro]] 2008/01/06 01:11//       * To clarify, Mike meant to say they display a Help button in their preferences/properties dialog. See battery monitor or clipman.  --- //[[ongardie@gmail.com|Diego Ongaro]] 2008/01/06 01:11//
-    * 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 and About context menu items are discouraged. A Help button inside the properties dialog is optional (see ...)" --- //[[ongardie@gmail.com|Diego Ongaro]] 2008/01/06 01:12//+    *  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 ...)" --- //[[ongardie@gmail.com|Diego Ongaro]] 2008/01/06 01:12// 
 + 
 +  * [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, Genmon. // 
 +    * 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." --- //[[ongardie@gmail.com|Diego Ongaro]] 2008/01/06 01:12//
  
 ==== 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://img265.imageshack.us/img265/2880/menutitlepj6.png}}   * [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://img265.imageshack.us/img265/2880/menutitlepj6.png}}
-    * I'm not convinced I like this (and neither is Mike). Perhaps we should discourage menu titles instead. --- //[[ongardie@gmail.com|Diego Ongaro]] 2008/01/06 01:28//+    * I'm not convinced I like this. Perhaps we should discourage menu titles instead. --- //[[ongardie@gmail.com|Diego Ongaro]] 2008/01/06 01:28// 
 + 
 + 
 + 
 + 
  
 ==== Settings Dialog ==== ==== Settings Dialog ====
-  * [rfc] **When to store altered settings?** \\ Moved to [[panel-hig:discussion#when_to_store_altered_settings|discussion page]].+Interface guidelines regarding preferences/properties/setting dialogs. 
 + 
 +  * [rfc] When to store (save) altered settings? \\ Moved to [[panel-hig:discussion#when_to_store_altered_settings|discussion page]]. 
 + 
 +  * [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://library.gnome.org/devel/gtk/2.12/GtkDialog.html#GtkDialogFlags|GtkDialogs flags]]).  Btw, I prefer when the modifications are affected immediately, that's the default habit in most xfce settings dialogs. --- mike 2008/01/10 05:58 
 +      * "and the plugin's widgets should be set insensitive while the dialog is open" dropped  --- //[[ongardie@gmail.com|Diego Ongaro]] 2008/03/03 04:40// 
 +    * 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.  --- //[[ongardie@gmail.com|Diego Ongaro]] 2008/03/03 04:40// 
 +    * 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]" tag should be removed at that time.  --- //[[ongardie@gmail.com|Diego Ongaro]] 2008/03/03 04:44// 
  
-  * [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 86: Line 109:
   * The box should have a default border (1px).   * The box should have a default border (1px).
   * [draft] The box should have a spacing of 4px.   * [draft] The box should have a spacing of 4px.
-  * [draft] The image should have a size of \\ ''%%size of button - MAX (GtkWidget->style->xthickness, GtkWidget->style->ythickness)%%''+    * Plugins known to implement this: 
 +      * xfdesktop (4.4.2 and trunk) 
 +      * places (1.0 and trunk) 
 +    * I don't think the box should have a border/spacing, but use as much space as possible.  The only space would be the space between the childs, and 2 pixels may be a good default.   --- //[[mmassonnet@gmail.com|Mike Massonnet]] 2008/01/19 18:55// 
 +      * Are there any plugins that do that now?  --- //[[ongardie@gmail.com|Diego Ongaro]] 2008/03/03 04:47// 
 + 
 +  * [draft] The image inside the button should be set to the same size as the button (usually the size of the panel) without its padding and border size: \\ <code>  GtkIconTheme *icon_theme; 
 +  GdkPixbuf *pixbuf; 
 + 
 +  size = xfce_panel_plugin_get_size (panel_plugin); 
 +  size -= 2 + 2 * MAX (panel_plugin->button->style->xthickness, panel_plugin->button->style->ythickness)
 + 
 +  icon_theme = gtk_icon_theme_get_default (); 
 +  pixbuf = gtk_icon_theme_load_icon (icon_theme, "icon-name", size, 0, NULL); 
 +  if (G_UNLIKELY (NULL == pixbuf)) 
 +    return; 
 +  gtk_image_set_from_pixbuf (GTK_IMAGE (panel_plugin->icon), pixbuf); 
 +  g_object_unref (G_OBJECT (pixbuf)); 
 +</code> 
 +    * Note: this is more a problem of what to do with the size-changed signal  --- //[[mmassonnet@gmail.com|Mike Massonnet]] 2008/01/19 18:48// 
 +    * 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...  --- //[[ongardie@gmail.com|Diego Ongaro]] 2008/03/03 04:47// 
   * 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 98: Line 142:
  
 examples: verve, dict(ionary) examples: verve, dict(ionary)
 +
 +
  
  
Line 128: Line 174:
       * {{http://img406.imageshack.us/img406/8415/20071217194919102x40scrkk4.png}}       * {{http://img406.imageshack.us/img406/8415/20071217194919102x40scrkk4.png}}
       * //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] The box should have a default border (1px).
   * [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 'whitespace' characters and separators. Some people are tight on real screen estate. However this is good if we explicitly address the space between different monitors.//     * //kalikiana 2007/12/17 19:39 Space between labels was discussed before and the argument against it was that you can add space via 'whitespace' characters and separators. Some people are tight on real screen estate. However this is good if we explicitly address the space between different monitors.//
Line 146: 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.  --- //[[jannis@xfce.org|Jannis Pohlmann]] 2007/12/23 14:10//   * [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.  --- //[[jannis@xfce.org|Jannis Pohlmann]] 2007/12/23 14:10//
     * //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?  --- //[[ongardie@gmail.com|Diego Ongaro]] 2008/03/03 04:51//
  
 ===== Class G: Grid ===== ===== Class G: Grid =====