Quote:
|
Originally Posted by weedfreak
I am not interested in adding new features until the current code works correctly and consistently, search and replace is totally inconsistent for example.
|
Part of the issue here is search and replace has to run very differently over book and code views. The other issue is, it needs some work.
Quote:
|
Originally Posted by wedfreak
Once the current code works it would be nice to be able to find unused css entries in the css or css entries in the book that are undefined.
|
This would be a nice plugin.
Quote:
Originally Posted by JeremyR
Yikes. If you take out WYSIWYG (or even just de-emphasize it), I really don't see the point of Sigil anymore.
That is its main appeal, it's basically a word processor for ebooks. You can load and edit (or make) a book for the most part without having to know HTML or muck about with it.
It seems to me that most of these power users already have book creation tools, and only use Sigil as a last step. Is that really the main audience for Sigil? People who think of it as an afterthought, rather than a main tool?
|
From what I've learned those people are either using Atlantis Word Processor, Jutoh, or running their Word doc (saved as HTML) though calibre. People use the WYSIWYG editor but the general response I've gotten is people use Sigil like Jabby does.
When I say de-emphasized I don't mean mean reduce it's feature set or remove it. I mean in terms of when you open Sigil the default won't be WYSIWYG. There are plans to improve the book view. One thing that charleski suggested that I plan on exploring is using
TinyMCE instead of a QWebView in edit mode.