From: Verdon V. <ve...@ve...> - 2006-03-07 15:40:48
|
This sounds sensible. I like the box model too :) In that manner, if I wish, I can id things in my theme.tpl file along the lines of leftCol, centerCol, rightCol and can get quite specific in my css by using selectors like #leftCol .box-title h1, #rightCol .box-title h1 {do something} #centerCol .box-title h1 {do something different} verdon On 7-Mar-06, at 10:00 AM, Matthew McNaney wrote: > Hey, > > I have made some style sheet changes for Fallout: > http://res.stddev.appstate.edu/cvs/fallout/themes/default/ > > http://res.stddev.appstate.edu/cvs/fallout/themes/default/theme.tpl > As you can see, there are now style sheet links inside the theme.tpl > (as > I said it would). The {STYLE} tag is still present for module includes. > These go first to allow theme styles to overwrite them. > > You will also notice that the style.css in just an include file. This > is > something that really stuck with me from the training. The theme > framing > is in position, basic holds my font, spacing, borders, etc., and > default > holds my colors. Before this commit, all my work was in just two files. > > I ran into one small snag. NakedDisplay in Layout (usually used for > pop-ups) would use a little header file with your style settings. Since > those settings were removed, the pop-up blocks were devoid of style. To > compensate, you can create a "blank.tpl" file in your theme and layout > will use it instead. If it is not present, layout uses its default > template. > > One more quick discussion. I have been trying to simplify the box model > but I believe I will have to stick to this format: > > <div class="box"> > <div class="box-title"><h1>Title</h1></div> > <div class="box-content">Content here</div> > </div> > > I can't style just the h1 because sometimes modules will insert other > data in the title bar. Blog, for example, has the author and date in > the > title header. If I controlled the font with box-title alone, those > entries would inherit the style. If I classed the h1, then I would have > to create a class for the other elements as well. I also need the > box-content because there isn't a suitable replacement. I can't use > p.box-content because the content may have a <p> tag itself. > > I think the current box model is a good balance between simplicity and > control. > > Thanks all, > Matt > > -- > Matthew McNaney > Electronic Student Services > Appalachian State University > http://phpwebsite.appstate.edu > > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting > language > that extends applications into web and mobile media. Attend the live > webcast > and join the prime developer group breaking into this new coding > territory! > http://sel.as-us.falkag.net/sel? > cmd=lnk&kid=110944&bid=241720&dat=121642 > _______________________________________________ > Phpwebsite-developers mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwebsite-developers > > |