View Single Post
Old 12-16-2015, 02:44 PM   #11
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,884
Karma: 6120478
Join Date: Nov 2009
Device: many
Hi JSWolf,

Not a chance. Sigil is not in the plugin development business. The only exception is the flightcrew plugin which was previously part of Sigil. Sigil has no interest in controlling or centralizing plugins for plugin developers. As volunteer developers, we simply do not have the time to keep up or manage a repository for plugins.

The key for Sigil is to keep the interface as simple as possible and to allow plugin developers full reign in their own world to do what they want as long as they do not violate the plugin launcher interface.

As for plugins dying off, we only have 18 or so plugins, and as far as I know, they all still work. I have been careful to make the plugin launcher interface as backwards compatible as possible while still fixing bugs.

In other words, if you want to check for updates you do it for your own plugin with whatever code you want. It is only handful of lines in python to do the above.

KevinH
KevinH is offline   Reply With Quote