Plugin system
Currently when compiling Diodon one has to decide whether e.g. the unity lens needs to be installed or not. However this can not be done when installing from the ppa. That way the Unity Lens will always be installed as the indicator.
Therefore it would be great to have a plugin system where each component can be activated independently. This way it would be possible to have different debian packages for the core and the plugins.
Future features can than easily be implemented as well without adding more complexity to the core itself. Even 3rd party plugins would be possible.
The current question is if there is a suitable plugin system available for Vala?
Blueprint information
- Status:
- Complete
- Approver:
- None
- Priority:
- Medium
- Drafter:
- None
- Direction:
- Approved
- Assignee:
- Diodon Team
- Definition:
- Approved
- Series goal:
- Accepted for trunk
- Implementation:
-
Implemented
- Milestone target:
-
0.6.0
- Started by
- Oliver Sauder
- Completed by
- Oliver Sauder
Related branches
Sprints
Whiteboard
http://
http://
I was reading more about LibPeas. Do you think it is developed and stable enough for us to use? The Shotwell folks apparently are still holding off switching to LibPeas and are still using their own system (http://
Well, the version available in Oneiric is used by gedit and totem and seems therefore pretty stable. However, as noted in the shotwell Issue, the version for Natty and lower are definitely not stable enough for us either.
The question here is, if such a plugin system needs to be available on older system as well or if should make a cut here. Another way would be to backport the Oneiric version to Natty.
We have a similar issue with gtk3 which is needed to implement Blueprint key-combination. Even though gtk3
runs on Natty there is no gtk3 Ambiance theme available therefore Diodon looks pretty misplaced.
~sao (2011-8-16)
