[dojo-contributors] squid theme

Eugene Lazutkin eugene at lazutkin.com
Fri Aug 17 17:41:22 EDT 2007

Hash: SHA1

Obviously Dijit doesn't depend on DojoX, so it doesn't make any sense to
include CSS rules of DojoX components into any Dijit files, including
themes. But Dijit depents on the core, and the DnD is a part of the core
- --- it is a different case.



Tom Trenka wrote:
>     > .tundra .dojoxWidgetName { }
>     > .soria .dojoxWidgetName { }
>     > .squid .dojoxWidgetName { }
>     What if somebody adds new theme? Now we have to deal with a bunch of CSS
>     files scattered through Dojo. Have this declarations in, say, tundra.css
>     makes it simpler to maintain, and ultimately a theme creator will know
>     what visuals to style just by looking at one file.
> That's true, but at the same time if someone is writing a DojoX widget
> that's not part of Dijit (and probably won't be ported over), I don't
> know that there's a choice.
> I think what Pete is proposing here is definitions in the widget's CSS
> file that might or might not take into account Dijit themes, as opposed
> to adding these definitions to the Dijit theme file.  It's not ideal but
> it keeps it separate and simple--and it puts the onus on the widget
> author to keep it up to date, which is something I'd prefer happen in
> DojoX anyways.  You know--"and hey, it works with Dijit themes, too!"
> trt
> ------------------------------------------------------------------------
> _______________________________________________
> dojo-contributors mailing list
> dojo-contributors at dojotoolkit.org
> http://dojotoolkit.org/mailman/listinfo/dojo-contributors

Version: GnuPG v1.4.7 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org


More information about the dojo-contributors mailing list