View Single Post
Old 02-07-2018, 12:55 PM   #319
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,804
Karma: 6000000
Join Date: Nov 2009
Device: many
Any Interest in a pseudo-official set of pre-installed Plugins?

We have almost 50 Sigil plugins now. I am really happy with the range of plugins and would like to thank all the plugin authors for their great work!

When we designed the plugin interface, I was hoping it would bring the simplicity and power of python to help spur growth and developer interest in Sigil. I think we have achieved that!

So what are your feelings about pre-packaging/installing a small number of plugins into Sigil itself as sort of "official" plugins? The idea here is that they would still be plugins but whose code (not preferences) would come pre-installed and live inside the Sigil application directory someplace and not have to be downloaded and installed by every user. Plugin preferences would still be specific to the local user.

Ideas for official pre-packaged plugins might include one for docx input, one for kindle input, FolderIn/FolderOut, FlightCrew, epubcheck, font subsetting, css checking, and whatever else most people would find useful.

We would bring these into an official plugins tree on github open to plugin developers or something along those lines, and when the release apps are done these would be included in the main installer package or maybe in a single secondary installer. Making them official would allow us to free up those quicklaunch plugins with official icons while still allowing 5 additional user installed quicklaunch plugins.

Obviously if any plugins include 3rd party code they would have to have compatible licenses if they were to be included in an official tree.

Or is all of this just a waste of time and we simply stick to what we have now?

All comments welcome ....
KevinH is online now   Reply With Quote