Quote:
Originally Posted by varlog
Qt itself has a add-a-plugin ability - see "The Lower-Level API: Extending Qt Applications". I am sure the developer/s know it and have already considered it in the past and have perfect reasons for not implementing it. I suppose one of the reasons is amount of work involved. What I would like to know are the other reasons, if any, which are perhaps obvious when one knows insides of Qt and Sigil - but not to outsider like me.
@user_none: I would really really appreciate some response... please?
|
Yes Qt provides plugin support. Two issues using it.
The first and smaller issue is language support. You basically have a choice between C++ and QtScript. Which goes back to the whole people actually need to know C++...
The second and larger issue is there is more to plugin than loading them. That's what the system Qt provides does for you. It makes it easy to load plugins. A plugin can't do anything if there aren't hooks for it to tap into and actually do anything. That's the hard part that's going to take the most amount of effort.