Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionNext revisionBoth sides next revision | ||
dev:garcon [2009/08/17 09:38] – 145.225.60.4 | dev:garcon [2010/10/02 17:26] – external edit 127.0.0.1 | ||
---|---|---|---|
Line 3: | Line 3: | ||
There are some issues in garcon (previously libxfce4menu, | There are some issues in garcon (previously libxfce4menu, | ||
- | Specifications: | + | **Specifications: |
- | Sources: [[http:// | + | **Sources:** [[http:// |
===== File Monitoring ===== | ===== File Monitoring ===== | ||
We'd like the give the library build-in support for monitoring menu changes. This means we monitor the .menu file(s) for changes (for example made by Alacarte) and the .desktop file directories for added/ | We'd like the give the library build-in support for monitoring menu changes. This means we monitor the .menu file(s) for changes (for example made by Alacarte) and the .desktop file directories for added/ | ||
+ | |||
+ | |||
+ | ==== GarconMenuDirectory ==== | ||
+ | **Description: | ||
+ | |||
+ | ==== GarconMenuItemCache ==== | ||
+ | **Description: | ||
+ | |||
+ | Maybe a signal when a item is added or removed to the pool, but I doubt this is very useful. | ||
+ | |||
+ | ==== GarconMenuItemPool ==== | ||
+ | **Description: | ||
+ | |||
+ | Maybe a signal when a item is added or removed to the pool, but I doubt this is very useful. | ||
==== GarconMenuItem ==== | ==== GarconMenuItem ==== | ||
+ | **Description: | ||
We're not going to implement file monitoring on this level. However there will be some new API to reload a desktop entry (possibly from a new location) and the possibility to watch changes (signal, property notifications). | We're not going to implement file monitoring on this level. However there will be some new API to reload a desktop entry (possibly from a new location) and the possibility to watch changes (signal, property notifications). | ||
Line 23: | Line 38: | ||
Will do the same as '' | Will do the same as '' | ||
+ | ==== GarconMenu ==== | ||
+ | **Description: | ||
+ | This is where we will do all the monitoring work. We will setup monitors for the menu file itself, as well for the merged files and the desktop entry directories. The object will probably get some signals when an item is added/ | ||
- | ===== Misc | + | ===== TODO ===== |
- | + | * < | |
- | A couple | + | * < |
* Always return a reffed object in the _get_ functions and mention this in the API docs. | * Always return a reffed object in the _get_ functions and mention this in the API docs. | ||
+ | * Because we always ref and because of the implementation of the singletons: we also return reffed items in the GList' | ||
+ | * We could add a helper: ''# | ||
* A couple of structs need to move to the header. | * A couple of structs need to move to the header. | ||
+ | * We need to reserve space if we do this. | ||
* Personally I find the gio helpers a bit ugly in the public api, maybe we can make this private (preferred) or rename them to start with garcon_. | * Personally I find the gio helpers a bit ugly in the public api, maybe we can make this private (preferred) or rename them to start with garcon_. | ||
- | * Possibly drop '' | + | * <del>Possibly drop '' |
- | * Implement '' | + | * <del>Implement '' |
- | * Get rid of '' | + | * <del>Get rid of '' |
- | * People only need to call '' | + | * <del>People only need to call '' |
- | * Don't know about '' | + | * <del>Don't know about '' |
+ | * < | ||
+ | * < | ||
+ | * < | ||
+ | |||
+ | ===== Future===== | ||
+ | |||
+ | * We currently support desktop files with the type Application and Directory, but not Link. |