tools docker etc in plan

[Pierre Stirnweiss]

To be honest, I think we should think a bit further. My impression (when I
was looking into tools/plugins loading mechanism for the (still unfinished)
change tracking tool) is that the system is very rigid and basically depends
on the developer knowing what plugins are there what plugins would be
usefull. There also is the case where some tools of one particular plugin
does not make sense (expl, the change tracking tool of the textshape plugin
doesn't make sense outside words, because odf does not foresee change
tracking outside a text document).
I think we should revisit how our plugins/tools are loaded and allow more
flexibility at runtime to set which are the plugins to be loaded (also by
users). After all, the whole point of the plugin system is to allow external
plugins to be designed. So there should be a way to set this up, other than
calligra core developpers explicitely allowing/disallowing plugins/tools.

On a side note, it seems that at application startup, all the plugins are
loaded serialised and only when this is finished will the application load
further. That's ok when we have only a handfull of plugin installed but the
system does not scale very much. Can't we have non critical plugins load in
parrallel to further application startup?, in a different thread?

PierreSt

On Tue, Jan 25, 2011 at 10:49 AM, Dag Andersen <danders at get2net.dk> wrote:

> Atm I don't have any use for the tools docker nor actually any other docker
> except the Scripting docker in plan.
> This *may* change in the future of course, so it would be nice to have a
> way
> of controlling which plugins should be loaded. AFAICS it's possible to
> *disable* plugins if you know their id. I'd rather have the possibility to
> *enable* those I use and have everything else disabled.
> Anybody knows how this could most easily be achived?
> --
> Mvh.
> Dag Andersen
> _______________________________________________
> calligra-devel mailing list
> calligra-devel at kde.org
> https://mail.kde.org/mailman/listinfo/calligra-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/calligra-devel/attachments/20110125/fced94ea/attachment.htm>