Xfce Wiki

Sub domains
 

Differences

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

Link to this comparison view

releng:4.8:roadmap:garcon [2009/08/20 03:06]
jannis
releng:4.8:roadmap:garcon [2010/10/02 17:26]
Line 1: Line 1:
-====== Garcon Roadmap for Xfce 4.8 ====== 
  
-Please note that garcon is not a core component (only an essential dependency) but it is especially relevant for the Xfce 4.8 development cycle for two reasons: ​ 
-  - It's (going to be) used everywhere (xfce4-panel,​ xfdesktop, xfce4-appfinder,​ ...) 
-  - It's not finished (main thing missing is monitoring) 
- 
-===== Fine-Grained Monitoring (Tough) ===== 
- 
-libxfce4menu 4.6 used a dead simple approach for menu and menu item monitoring: destroy existing menus upon changes and require applications to rebuild their menu from the bottom up. This is very inefficient. Now with garcon we have a proper, very detailed representation of the menu tree and its elements in memory. We can use that to handle many of the changes that can be made to the file system. Everything from the destroy-and-recreate approach up to menu tree patching and fine-grained menu monitoring is possible. 
- 
-This is discussed in more detail on [[dev:​garcon]]. 
- 
-Completed: 0% 
- 
-===== Menu Editing APIs (Tough and 100% Optional)===== 
- 
-I've presented some of the ideas I have in mind for making it possible to write full-fleshed menu editors on top of garcon on [[http://​gezeiten.org/​post/​2009/​02/​Thoughts-on-libxfce4menu-for-Xfce-48]]. This is optional for this cycle as it is not required by an core components of Xfce. 
- 
-Completed: 0%