For now it seems there's broad support for this move. Thanks for that people, I appreciate it.
Quote:
Originally Posted by negiarcian
Yes, and BTW first thing I did after downloading Sigil was to go and get FlightCrew. Would be nice to be offered the option for FlightCrew when installing Sigil.
|
The next version of Sigil will come with FlightCrew integrated. That was the whole point of the FC project.
Quote:
Originally Posted by kiwidude
And yeah I specialise in features that only mean something to me - that's why I love that in Calibre they can be written as plugins that only people who want the feature download it.
However that does require the app being engineered in a specific way, and plugins can only do "so much" so you still have to drive the core of the application for the masses. So my vote is go for it and steer the good ship Ligis as long as you can... |
A system where other devs can easily plug into the GUI or backend at runtime is trivial for applications written in interpreted, dynamic languages like Python in Calibre's case. For compiled applications it's much more difficult, as I'm sure you're aware.
Imagine having to compile a plugin for six architectures: Win x86, Win x64, Mac Intel x86, Mac Intel x64 and then Linux x86 & x64, where there's no way in hell you could provide binary plugins that would work on all the distros. And even for "simple" platforms like Windows, you would still have to match your compiler (and compiler version, and runtime library linked) to the ones used to build Sigil.
Basically you would have to provide sources for your plugins and ask the users to compile them themselves in most cases. Few would know how, and even fewer would be willing to do it.
Quote:
Originally Posted by KevinH
I moved to a model will I simply contribute patches to things I care about and use *only*, with no major stake in any one project.
|
I'm not against this practice at all, even though it might appear that way from the post. If random people come in with sensible patches, great, the more the merrier. You can't ask for or expect a larger commitment when you know just how much time it takes out of you personally. God no.
Even when the patches aren't sensible, it's not a problem if there's one dev who has an idea of what the project is about who's willing to say no.
The problems start when that dev stops working and suddenly, everything goes.