3 comments
A visual editor containing the parsed version of 80kB source code can only be worse.
Why? Remember that the "parsed version of the source code" is essentially the same as "the read tab". Essentially you're saying you're happy for readers to have to wade through a huge amount of text, but not editors. This means (a) we're probably serving our readers poorly, but more obviously (b) we'll be stopping editors from seeing the context of the area that they are editing.
(Playing devil's advocate a little. :-))
You've got a point in that summary style should be occurring if it is going to be difficult to edit in a full page mode; however, readers can also jump around using the TOC. When you are editing, I assume that you won't be able to. Section editing also helps reduce edit conflicts.
Reading the 80kb of (static) parsed code is different from having a script to interact with that same amount of code.
And for the purpose of editing a section, the VE could just keep the other sections intact, to provide you some context, but still parse/interact only with that only section (and in case you change your mind and also want to edit more section after that, it could edit the whole page - or a group of sections, if that was possible).
+1. An editable box consumes many many times the amount of client hardware power compared to a read-only page with the same amount of pretty content in it.
I think this is because "insert" and "input hardware interaction" consume lots of processing power; but I'm not a developer for this project so I'll let them speak.
"And for the purpose of editing a section, the VE could just keep the other sections intact, to provide you some context, but still parse/interact only with that only section (and in case you change your mind and also want to edit more section after that, it could edit the whole page - or a group of sections, if that was possible)."
Please! This would be a great feature.
