Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
design:appfinder [2011/06/27 22:55] – jvilk | design:appfinder [2012/02/07 14:42] – [Comments] ochosi | ||
---|---|---|---|
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 71: | Line 72: | ||
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:// | ||
- | The IDs are prefixed with //A// for // | ||
- | The status cells are color coded: | ||
- | * a //white// background means the feature is not implemented yet, | ||
- | * a //green// background means the feature is supported, | ||
- | * a //orange// background means the feature is being worked on, | ||
- | * a //grey// background means the feature is partially working but is not developed any further. | ||
- | |||
- | | **ID** | **Description** | **nick/ | ||
- | | 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: Done | | ||
- | | I01 | Store settings in Xfconf | @palegreen: Done | | ||
- | | I01.1 | Window size and pane position. | @palegreen: Done | | ||
- | | I01.2 | Last category? | @palegreen: Done | | ||
- | | I02 | Investigate dbus daemon, profiling shows a lot of time is spend in starting Gtk (theme/ | ||
- | | I03 | Save successfully launched commands | @palegreen: Done | | ||
- | | I04 | Simple extension framework. | -- | | ||
- | | 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. | @palegreen: Done | | ||
- | | I06 | (icon) theme changes: reload cached pixbufs. | @palegreen: Done | | ||
- | | I07 | Bunch of clever key combinations to speed-up navigation. | -- | | ||
- | | I08 | Obey show-image-on-button setting for launch button. | @palegreen: Done | | ||
- | | I09 | Sort custom commands before desktop-file commands in the completion. | @palegreen: Done | | ||
==== Ideas ==== | ==== Ideas ==== | ||
* [[releng: | * [[releng: | ||
Line 107: | Line 80: | ||
* 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 114: | Line 88: | ||
* 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 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' |