Xfce Wiki

Sub domains
 

Differences

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

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
releng:4.8:roadmap:garcon [2010/04/01 23:36]
85.176.137.20
releng:4.8:roadmap:garcon [2010/10/02 17:26] (current)
Line 4: Line 4:
   - It's (going to be) used everywhere (xfce4-panel,​ xfdesktop, xfce4-appfinder,​ ...)   - It's (going to be) used everywhere (xfce4-panel,​ xfdesktop, xfce4-appfinder,​ ...)
   - It's not finished (main thing missing is monitoring)   - It's not finished (main thing missing is monitoring)
-===== Fine-Grained Monitoring =====+===== Fine-Grained Monitoring ​(postponed, for now basic monitoring will do: 100%) =====
  
 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. 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.