Re: Re: [PROPOSAL] 'Region' generated ID set

On Fri, 19 Mar 2004 16:01:22 -0500, Chad Whitacre  
<[email protected]> wrote:

> Right. So for example in #portal-top, the seven elements in there are  
> named semantically, right? E.g., #portal-logo, #portal-skinswitcher,  
> etc. Now what happens when I need something else in the header? I  
> customize global_skinswitcher. But now it's not being used as a  
> skinswitcher anymore, and so I've violated the semantics. Yes, I could  
> use a different id name, but a) this is less efficient, and b) the pt  
> name is still unsemantic.

Chad,

If you add an element that isn't part of the existing semantics, you  
shouldn't re-use an existing class, but invent your own that reflects the  
new element. That's why you customize main_template

I would also appeal to Michael to lay down the Nameageddon II-crackpipe -  
a name change for all the IDs *again* is out of the question. Plone 2 will  
have identical IDs until Plone 3 arrives. Feel free to plan the perfect  
scheme for Plone 3, but it's not going to change in Plone 2. It's hell for  
skin writers, documentation writers - everyone.

-- 
__________________________________________________________________

  Alexander Limi   ·   Interaction Architect   ·   Plone Solutions

  Development · Training · Support · http://www.plonesolutions.com
__________________________________________________________________

  Plone Co-Founder   ·   http://plone.org   ·   Connecting Content



-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click