Quote:
Originally Posted by DiapDealer
So it bugs me that a needlessly crippled version of sigil has been rushed to being packaged by a software repo. Even if it is an older QtWebKit version.
|
In this I do not agree with you. The version is working and performs its main functions. Without any plugins.
The plugins forum clearly shows that plugins still have problems and errors. Why do I need this?
Let me remind you that you yourself write about plugins:
Quote:
Plugins are developed and provided by third parties. ... We cannot be held responsible for what a third party plugin that you the user actively installed and ran.
Also, realize that Plugins are separate from Sigil and have their own authors. They aren’t part of Sigil. If you have an issue with a plugin you’ll need to take that up with the person(s) who made the plugin.
Again, we at Sigil have no control over plugins and what they actually do.
|
After that, what are we talking about? In your place, I would use plugins as a source of ideas for further development of editor functionality. If you implement everything that they do in Sigil itself, they will automatically become useless and unnecessary. Then maybe Python would be unnecessary, pure Qt would remain. Fewer compatibility and portability issues.
This whole situation reminds me of a story with BookView. You have decided to remove this mode from the editor, and if you don’t like it, tell everyone who is not happy, work on the old version. I also did not like it, but I reconciled with reality. I have been using Sigil for quite some time. The main mode of operation of CodeView and only occasionally to evaluate the result I use the viewing mode. Formerly BookView, now F10. I consider PageEdit a useless tool, a waste of your time and energy.
Sigil is a great editor in its purest form.