AwnSettings should be readable and writeable by applets
AwnSettings contains many variables which applets could use, but they do not have access to them (other than reading them via gconf, but this is not a good solution).
In libawn-effects branch the awn-gconf module was moved libawn, so applets can at least read the values, but it makes unnecessary copy of the data (plus more dbus traffic). Also they cannot change the values, which would be particulary useful for changing the 'hiding' value (you move your mouse to applet's awn-dialog, and awn wouldn't autohide... I'm sure we'd find many more use cases).
I suggest putting the AwnSettings into shared memory block (shmget / shmat...) and use a spin-lock for locking (because lock/unlock sequences will usually be very fast).
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Undefined
- Drafter:
- Michal Hruby
- Direction:
- Needs approval
- Assignee:
- black
- Definition:
- Obsolete
- Series goal:
- None
- Implementation:
-
Beta Available
- Milestone target:
- None
- Started by
- Michal Hruby
- Completed by
- Michal Hruby
Related branches
Related bugs
Sprints
Whiteboard
05/01/08 : Is this have been merge to trunk ?
These changes are already implemented in awn-curves branch, though without the locking.
15 Feb 08: We're half way there as AwnSettings is in trunk now. However, I'm not sure about the shared memory right now, as I hope to thin-down AwnSettings during the rewrite, as some settings should be private.
Work Items
Dependency tree
* Blueprints in grey have been implemented.
