Re: [Phpwebsite-developers] Fallout Selectors

[Matthew M. <ma...@tu...>]

On Tue, 2006-02-28 at 14:57 +0000, Shaun Murray wrote:

> The boxes are usually then just...
> 
> <div class="box">
>    <h3>{title}</h3>
>    {content}
> </div>

Originally I did that, however I had problems because the content might
contain the same tags. For example, the css would say
div.box h3 {}

and that would work fine for the title. However if the {content} had a
h3 in it as well, I may not want it to use the same style.
Also with div.box-title I could put background-color, background-image,
etc. in the div. Headings don't work that well with those type of
stylings.

The same goes for the content area. I may want to color it and styling
on the <p> would cause goofiness. 

> I do the same for modules too, just adding eg. <div  
> class="announce">...</div> around a template. It'd actually be useful  
> if those were there by default in fallout for me anyway.

Good point. I was doing that, then I started slacking off :P I think it
should be a standard. I'll try to get back in the habit.

> The other thing that might be useful is adding insertion of a class  
> for a category into the top of a template so you could have different  
> css depending on the category. At the moment I don't think you can  
> return the category name without it being a link in 0.10.x.

On category listings? Not sure if I get what you are saying.


> I'd also like to see some standard classes defined for menus (first,  
> last, selected, enabled, disabled etc) although perhaps those should  
> be in menuman and then overridden? And for elements such as dates and  
> bylines which are common across many modules.

Good plan. Indicate where it is needed in code and I can implement.

-- 
Matthew McNaney
Electronic Student Services
Appalachian State University
http://phpwebsite.appstate.edu