Add the posibility to wrap content in DIVs
Very often, I find myself in the need of wrapping several paragraphs/headings/etc in a div. Right now, the only possibility seems to be switching to HTML view and adding it there.
For less experienced users this would be close to not-doable. How about adding the possibility to choose DIV in the Format box?
Any other ideas of what else could be added?
Now - the answer to your question may lie within your question.
If a user wishes to wrap some of his/her post inside a <div> tag it would assume that user is fairly okay with HTML and has a basic understanding of it's layout and writing/coding in HTML. Therefore that user will have no problem in using the HTML editor to add a <div> element to their post.
For the less-technical savvy user a <div> tag means what? Division? Divider? Dividend? You see, the name of the tag does little to support the power that a <div> tag actually can posses and therefore it would be of little benefit for the end-user who is not code-savvy.
The way the editor is currently written actually is more intuitive for less code-savvy users. It's much more like a word processor where what you see is what you get. For those of us who wish to intervene with extra HTML tags then we can dive into the code view and add our own tags, classes and all that.
In my view it would be a bad idea to have any sort of HTML tag as a 'button' in the editor window - it would add confusion. The solution would be to code a plugin to add such a button if you use it on a regular basis.
Thanks for your thoughts on this! Now I see, I was explaining this the wrong way...
What I actually look for is the possibility for the user to select several items (headings, paragraphs, etc) then choose a global style for these. On its turn, the editor should insert a div around the selected elements, with the specified class/ID. The default setup, will insert the selected class/ID to EACH element in the selection.
I hope that makes more sense :)
Ah I see! Now I understand what you are aiming for.
There are two thoughts to this:
1. The current set up is probably more semantically correct in that adding an extra element isn't probably good coding when you can add class to each element in turn.
2. Perhaps then the system needs to handle inserting these classes better? I do not know from experience but does changing from one style to another remove the old classes from the element(s) before appending the new class? If not then this issue needs to be addressed so as not to end up with conflicting and unnecessary CSS classes for each element.
RSS feed for this topic
You must log in to post.