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
Next revisionBoth sides next revision
releng:4.10:roadmap:xfce4-appfinder [2011/04/19 10:53] – [Other Ideas] nickreleng:4.10:roadmap:xfce4-appfinder [2011/07/10 00:04] – [Discussion Points] nick
Line 2: Line 2:
  
 The idea is to merge the current appfinder and xfrun4 into 1 application that can do it all; but better. To get this working in a fast way a number of custom tree- and list-models need to be written that all work with the same data, which is all loaded in threads and inserted in idles, to keep the interface responsive. The idea is to merge the current appfinder and xfrun4 into 1 application that can do it all; but better. To get this working in a fast way a number of custom tree- and list-models need to be written that all work with the same data, which is all loaded in threads and inserted in idles, to keep the interface responsive.
 +
 +See the [[design:appfinder|design page]] for more information.
  
 Completed: 0% \\ Completed: 0% \\
Line 30: Line 32:
   * See also [[http://gezeiten.org/post/2009/07/Appfinder-Ideas|Jannis' ideas]] and the replies to his post.   * See also [[http://gezeiten.org/post/2009/07/Appfinder-Ideas|Jannis' ideas]] and the replies to his post.
   * Panel plugin that can do the same as the Alt+F2 dialog (which will also obsolete the verve plugin). Might be a good alternative to searching in the applications menu.   * Panel plugin that can do the same as the Alt+F2 dialog (which will also obsolete the verve plugin). Might be a good alternative to searching in the applications menu.
-===== Discussion Points ===== +  * Do not store commands that failed to execute. 
-  * Do we want this to run as a daemon in the background, which xfrun4 does currently. If implemented properly, the instances can all share the same data set and everything will feel more responsive. On the other hand, more data is loaded then xfrun4 did, so it might be more memory hungry. Probably the sanest way is to provides a dbus service (like terminal) and the 2nd instance will spawn from the running one. Then we can always make it optional to keep a daemon running.+