From: Bharat M. <bh...@me...> - 2006-08-25 20:42:02
|
Awesome. So I've created modules/core/data/gallery.css which will be loaded for every page. It can be the location for any CSS that we want to be common across the entire application, which means that we can probably refactor anything common across all of our current themes up to this location. It also means that when we roll out a new feature we can just put the CSS here. I think this will simplify our lives a fair bit. Felix, once this is in you can put your color picker CSS in there also. I have a little more work to do on the rest of the code, but I'll commit this when I get back from Vegas. -Bharat Jesse Mullan wrote: > If yui.css is linked first and then the theme's css second, the theme's > definitions for the yui css will take precedence, so the module should > just insert its css before the theme. You don't need to worry about > !important or specificity, just ordering. > > Bharat Mediratta wrote: >> 2. Add the CSS in the module code, but let the themes override it. >> Pros: Themes have control. Themes don't need to be updated unless >> they want to override the default CSS >> Cons: We have no means currently for themes to override CSS provided >> by modules, except via using the !important CSS marker, and I don't know >> how effective/portable that is. > > > > ------------------------------------------------------------------------- > Using Tomcat but need to do more? Need to support web services, security? > Get stuff done quickly with pre-integrated technology to make your job easier > Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo > http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 > __[ g a l l e r y - d e v e l ]_________________________ > > [ list info/archive --> http://gallery.sf.net/lists.php ] > [ gallery info/FAQ/download --> http://gallery.sf.net ] |