Restructure the project to be ready for plugins
IMO we should restructure the project to provide clean support for plugins.
We need a library for plugin developers to link against, and to turn our actual services into plugins.
Blueprint information
- Status:
- Started
- Approver:
- Eduard Gotwig
- Priority:
- High
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- Santiago Ocamica
- Definition:
- Drafting
- Series goal:
- None
- Implementation:
-
Good progress
- Milestone target:
- None
- Started by
- Santiago Ocamica
- Completed by
Whiteboard
I have done some work but I'm having trouble with cmake. I'll push and link my branch.
- santi698
I saw some nice conepts, that you already made in your branch, santi.
However; IMHO I think we have to cover in the first place all sort of usecases and arts to save the different states and properties globaly for every Service/Widget.
Please see my new work items list. Please also improve my list, or discuss and add ideas, what can be improved.
- gotwig
I'm not sure if using GLib.Settings for that is the right way to go since it doesn't support saving more complex data structures than a string array. IMO it would be better if we could create a settings structure (Object) and serialize and deserialize it or something like that.
- santi698
Work Items
Work items:
Rename last-positions to service-geometry, this key should save every possible globaly covered state for Services like the rotation degree (I want to introduce this feature as well), and the zoom level : TODO
Dependency tree
* Blueprints in grey have been implemented.
