Quote:
Originally Posted by treadlightly
I didn't export then re-import, but I don't have to browse for the file now, so yes, more streamlined!  And maybe Sigil had the feature where you saw the code on one side and the print view on the other, but like I said, I was just learning how to use it so I didn't have that enabled. Edit Book had it enabled by default. |
Sigil actually goes a step further. It's WYSIWYG. You can enable the WYSIWYG view by double clicking on the tab of the file. (Obviously doesn't work with CSS code.)
Kovid has already said he will probably never implement that, as it's a lot of work to get right, and editing in WYSIWIG can make you accidentally remove underlying code, breaking the book (I've done it in Sigil...).
A preview pane is fine; edit code on one side, immediately see the result on the other side
A great benefit of this approach is that you will actually learn what the code you are changing does. Strangely enough, when using WYSIWYG, you're actually working blind, changing code you can't see. Very nice for a beginner, but after a book or two changing the code directly (using regex, and other nice stuff) becomes way faster.