Difference between revisions of "SpecLPEPlugins"
Romain2Boss (talk | contribs) m (Add category Proposals) |
Johanengelen (talk | contribs) (→TODO) |
||
| Line 24: | Line 24: | ||
== TODO == | == TODO == | ||
- (simple) rewrite Effect creation as proper factory, to which LPE's can register themselves. (Johan should do that, ping him) | |||
- clean up the LPE interface. This is important. Over time, some cruft has crept in, especially in the on-canvas visualization. | |||
== Discussion == | == Discussion == | ||
[[Category:Proposals]] | [[Category:Proposals]] | ||
Revision as of 22:40, 21 July 2014
Launchpad Entry: https://blueprints.launchpad.net/inkscape/+spec/lpe-plugins
Summary
Right now, LPEs are compiled and linked together with inkscape. It would be much nicer if LPEs can be compiled into libraries (dynamically linked libs) that Inkscape can load. Then people can download new LPEs from others independently of Inscape releases!
Release Note
Rationale
Now, new LPEs only become available when a new Inkscape release is made. It would be much nicer if they were independent.
The LPE API is very small and simple. Yet it is powerful enough to make complicated effects. Because of the small and simple API, it is possible to make an "LPE develop package" with only a few header files in it, which can be linked as a DLL, and then put on some website for download for others.
Design
User Interface
No changes. It should be invisible for the user whether an LPE is linked with inkscape, or loaded from a dll
Back End
More ideas
TODO
- (simple) rewrite Effect creation as proper factory, to which LPE's can register themselves. (Johan should do that, ping him) - clean up the LPE interface. This is important. Over time, some cruft has crept in, especially in the on-canvas visualization.