Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
design:appfinder [2011/06/06 23:30] – [ToDo] ochosi | design:appfinder [2012/02/22 17:09] (current) – [Comments] amic | ||
---|---|---|---|
Line 22: | Line 22: | ||
* I was thinking since the dropdown shows the history, it could be used instead of the expander to show the extended mode with history focused (instead of showing an actual dropdown). If that's impossible I'd vote for something like a more subtle togglebutton. I'll see whether I can come up with a decent mockup. --- // | * I was thinking since the dropdown shows the history, it could be used instead of the expander to show the extended mode with history focused (instead of showing an actual dropdown). If that's impossible I'd vote for something like a more subtle togglebutton. I'll see whether I can come up with a decent mockup. --- // | ||
* Completion including rich text and icons can be done using GtkEntryCompletion with a GtkListStore combined with any cell renderers. | * Completion including rich text and icons can be done using GtkEntryCompletion with a GtkListStore combined with any cell renderers. | ||
+ | * Might we please have tab completion? Thank you. --- // | ||
Line 50: | Line 51: | ||
* I would prefer not to introduce new UI paradigms that people are unfamiliar with. An error icon is something that people are not used to clicking on. --- // | * I would prefer not to introduce new UI paradigms that people are unfamiliar with. An error icon is something that people are not used to clicking on. --- // | ||
* I think idea 3 can be dropped. The limited space to the left of the buttons is everything but a nice location to place text messages. --- // | * I think idea 3 can be dropped. The limited space to the left of the buttons is everything but a nice location to place text messages. --- // | ||
+ | * Why not just make the ' | ||
===== Compact Mode (Expanded) ===== | ===== Compact Mode (Expanded) ===== | ||
Line 58: | Line 60: | ||
==== Comments ==== | ==== Comments ==== | ||
* Not sure if we should hide the completion in expanded view. I guess we have to try it first, see if it feels natural. I think we should also skip the history popup menu, like we have it now in xfrun4, and expect users to use the expanded view for that.\\ That said I really like the design. Maybe we can use the space below the icon for the category list as well, but it looks clean and usable for sure. --- // | * Not sure if we should hide the completion in expanded view. I guess we have to try it first, see if it feels natural. I think we should also skip the history popup menu, like we have it now in xfrun4, and expect users to use the expanded view for that.\\ That said I really like the design. Maybe we can use the space below the icon for the category list as well, but it looks clean and usable for sure. --- // | ||
+ | |||
+ | * There is a problem with the up/down key : if you do two times down you are going in the expanded view, but now you cannot do up again to be in the reduced view (you have to do 2x Shift-Tab, and then Up. Concerning the history popup menu, I think it is a bad idea to remove it (this is what I use most). | ||
Line 70: | Line 74: | ||
Expanded layout with 6px between the icon and the treeview, entry still center-aligned with the icon. | Expanded layout with 6px between the icon and the treeview, entry still center-aligned with the icon. | ||
- | ==== ToDo ==== | ||
- | Stuff that needs to be implemented in the [[http:// | ||
- | |||
- | | **ID** | **Description** | **Status** | | ||
- | | B01 | Right-click menu in treeview(s). | -- | | ||
- | | B01.1 | Open exo-desktop-item-edit? | ||
- | | B01.2 | Clear custom commands from the history and clear all. | -- | | ||
- | | B02 | Items not visible on start in expanded mode. | @palegreen: Yes | | ||
- | | I01 | Store settings in XfceRc file (xfconf is slow) | -- | | ||
- | | I01.1 | Window size and pane position. | -- | | ||
- | | I01.2 | Last category? | -- | | ||
- | | I02 | Investigate dbus daemon, profiling shows a lot of time is spend in starting Gtk (theme/ | ||
- | | I03 | Save successfully launched commands | @orange: | ||
- | | I04 | Simple extension framework. | -- | | ||
- | | I04.1 | Match prefixes only. | -- | | ||
- | | I04.2 | Simple editor. | -- | | ||
- | | I04.3 | Support custom icons. | -- | | ||
- | | I04.4 | Do we need this in expanded view as well, like Jannis' | ||
- | | I05 | Garcon menu reloading support. | -- | | ||
- | | I06 | (icon) theme changes: reload cached pixbufs. | -- | | ||
- | | I07 | Bunch of clever key combinations to speed-up navigation. | -- | | ||
- | | I08 | Obey show-image-on-button setting for launch button. | -- | | ||
- | | I09 | Sort custom commands before desktop-file commands in the completion. | @palegreen: Yes | | ||
==== Ideas ==== | ==== Ideas ==== | ||
* [[releng: | * [[releng: | ||
Line 101: | Line 82: | ||
* One more note on the error-handling behavior: I personally think the appfinder shouldn' | * One more note on the error-handling behavior: I personally think the appfinder shouldn' | ||
* Agreed, it should not close on error. --- // | * Agreed, it should not close on error. --- // | ||
+ | * A bit off-topic, but I am not sure that appfinder is the right name for this tool. I mean that it is going to be more than an application-finder, | ||
== Extensions == | == Extensions == | ||
Line 108: | Line 90: | ||
* Picking the idea up from error-handling, | * Picking the idea up from error-handling, | ||
* We always use the default web browser. I am not sure we want to integrate something like "Open With" in the appfinder. Probably not. --- // | * We always use the default web browser. I am not sure we want to integrate something like "Open With" in the appfinder. Probably not. --- // | ||
+ | * I actually like the idea. --- // | ||
+ | |||
+ | ===== Panel Plugin ===== | ||
+ | |||
+ | A button, which looks like the Applications Menu button and toggles visibility of an AppFinder widget. | ||
+ | |||
+ | The AppFinder widget is displayed next to the panel (like applications menu), without window borders and without " | ||
+ | |||
+ | AppFinder preferences are available through a plugin context menu. | ||
+ | AppFinder plugin preferences (icon, visibility of a label etc.) are also available through the context menu. (a separate dialog?) | ||
+ | |||
+ | ==== Implementation ==== | ||
+ | |||
+ | [[dev: | ||
+ | |||
+ | |||
+ | ==== Implementation Constraints ==== | ||
+ | * To save memory the panel applet shares the model (app data) with the xfce4-appfinder process (if any). Possible solution: | ||
+ | * The plugin requests opening the widget over DBUS. | ||
+ | * The widget is rendered by the xfce4-appfinder process. | ||
+ | * The widget is embedded in a widget opened by the plugin in order to add some padding, hide the widget etc. | ||
+ | * (alternative) The widget is not embedded and its position and visibility is controlled over DBUS. | ||
+ | * The panel plugin is shipped with AppFinder (building and installation should be optional and enabled by default). | ||
+ | |||
+ | ==== Comments ==== | ||
+ | |||
+ | * I don't see what makes this easier then popping up the window. I feel more for a verve-like launcher for this. --- // | ||
+ | * Well I think it's mostly about the look' | ||
+ | * Answering the " | ||
+ | * Two observations related the dbus support in appfinder: 1) xfce4-appfinder doesn' |