From: Matt B. <ma...@ma...> - 2005-10-13 10:25:40
|
On Thu, 2005-10-13 at 11:00 +0100, John Kershaw wrote: > What I'm proposing (and using on some of my ancient phpwiki 1.3.0's) > is 100% about keeping markup separate from content. CSS classes and > ID attributes allow my users to add semantic meaning to their content > without having to worry about how it's going to presented, either now > or after some future site-wide stylesheet alterations. OK. At least we're heading for the same goal here, 100% agree that good classes and IDs on attributes are necessary, but I have some reservations about allowing arbitrary specification.... > For instance, my <div> code looks like this: > > ==== pullquote > What a great idea > ==== <snip other examples> > BTW The markup used is entirely up for discussion - I'm only talking > about the validity of the approach. OK. I think you've mostly convinced me that I do agree with what you're proposing, I probably misunderstood the initial post a little. I'm still vaguely uncomfortable with the idea of allowing users to add arbitrary classes to objects. I can't pinpoint exactly why though. I guess it's the whole trade off between flexibility and correctness. If you let users define arbitrary classes/ids you can bet it's going to be misused quicker than you can blink your eye. I'm not sure that that is a strong argument against your proposal though... just thinking aloud here. Could it be split into two parts? - Some extra syntactical features to define some commonly used page elements - An extra plugin that when included allows precise specification of class names / ids for attributes. Regards -- Matt Brown ma...@ma... Mob +64 275 611 544 www.mattb.net.nz |