View Single Post
Old 07-21-2014, 11:51 PM   #52
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: 9,146
Karma: 6565346
Join Date: Nov 2009
Device: many
Hi DiapDealer,

It is should be quite straightforward but I have never looked that closely. We should be able to simply never read out the code from the QWebView widget family and only set it. There is an attribute with QWebView to make the loaded web page un-editable and you effectively have a visually linked preview pane.

That said the wysiwyg nature seems to be what brings most novice users to Sigil. Perhaps we could do both by allowing the user to select in the Preferences how they want to use Sigil - code editing with live previewing mode vs wysiwyg editing mode.

All that said, user_none would be the one to ask as he understands the entire architecture while I only understand pieces here and there.

Take care,

Kevin
KevinH is offline   Reply With Quote