From Hendrixxxxxxxx -
Quote:
Wondering if it would be possible/easy/feasible to invisibilize (if that's not a word, it should be!) the html tags in code view (with maybe image tags excepted) - so they are still there, but invisible. Code view would look like a simple text editor while the tags are invisible.
This would get around the issue of trying to read around tags for those who compose in Sigil (maybe with automatic </p><p> tags inserted for each carriage return).
|
From Hitch -
Quote:
|
In reading what Cliff's written, it seems to me that he and his cronies--who are clearly more sophisticated than a lot of the folks that a) come here seeking help or b) that work with companies like mine--have worked out a viable solution for their own process. I understand why he works that way, having read his full explanation. {shrug}. It works for them, and I can see why. I wouldn't work this way--but there's no reason they can't. Or shouldn't. I can also see why removing BV would, in fact, harm their method.
|
From Hitch -
Quote:
|
I don't know--I can't speak for the guys. If it's easy, that's one thing. If it's not, it's a long way around, to address the users like Cliff. More importantly, even though it would eliminate the "distraction" issue (of using the HTML editor full-bore), it wouldn't address the paste-issue.
|
Yes, Book View as it is currently implemented works well for us, with some tweaking of the results occasionally in Code View. BUT, there may be more than one way to skin a cat! We understand that there are trade off's.
Joining in on the brain storming, Hendrixxxxxxxx's idea of being able to hide tags in Code View may be interesting (if this solution is viable from the perspective of the developers and saves them headaches).
On the negative side it would not be the wysiwyg rendering of the current book view which is nice. Would hiding the tags look like plain text? Or could it show Bold, Italics and Headings? Are there any editors already out there that have this type of functionality that we could evaluate and learn from?
On the positive side it seems like some of the quirky behavior exhibited by the current implementation of Book View could be eliminated. More consistent behavior would be nice.
For sure there is room to deliberate on the tradeoffs. Lose some (but not all) of the wysiwyg and distraction free goodness, but gain more consistent behavior. This is worth considering. Even though Book View works well for us it would be nice to eliminate the need to periodically clean up unintended tags in Code View. Also, I understand how non-technical users would find the behavior of Book View frustrating as it is currently implemented. This no doubt leads to some complaints.
And like Hendrixxxxxxxx said there are other issues to consider, such as retaining the current copy & paste functionality of Book View.