View Single Post
Old 09-16-2019, 05:10 PM   #48
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,859
Karma: 6120478
Join Date: Nov 2009
Device: many
Again pull requests for the Sigil User Guide welcome. If anyone wants to write a PageEdit User Guide we would be happy to include it.

If someone wanted to create a Quick Start document for either package, we would include it.

FWIW, We have never followed the normal versioning number system. And removing a broken "feature" like BookView could not wait until we reach 1.0.

So again, people can complain, moan, pester, etc about their particular itch but given how busy we are with major changes, do not expect much unless somebody additional steps up to help somehow.

Just since DiapDealer and I started Sigil has:

- gained the ability to preserve entities
- designed and implemented an entire plugin system and interface to it
- embedded a Python Interpreter to support plugins and extend Sigil
- fixed many many many crashing bugs and other bugs
- replaced the broken parser with our own gumbo based parser to allow for html5
- added support for mathml in Preview
- added support for editing epub3's
- improved support for audio, video, javascript, etc
- wrote many plugins to extend Sigil (along with many other people here! - Thank you!
- ported away from an old and broken QWebKit to a supported QWebEngine
- removed a broken BookView that encouraged novice users to break things and then blame us when it did not pass epubcheck

And now we are working to remove the requirement to use use Sigil's standardized structure.

So if anyone else wants to get involved and help Sigil, we would welcome the offer. Right now we are at the limit and all these "suggestions" to do more or change things really are not helping.

We are focusing our attention on getting a Sigil 1.0 out there that serious users and epub developers can use to create high quality epub2 and epub3 epubs. Novice users who know no css and no html really are not our worry nor our target at this time.

If you feel differently, then volunteer to pitch in and help in some way.
KevinH is offline   Reply With Quote