On Feb 22, 2011, at 9:18 AM, NiL wrote: > >> I don't mind adding the additional themes to the base distribution though, I >> guess when the packages was started, there weren't more. It's your call. >> > > > thanks for your reply, I was more thinking the other way round, > tw.uitheme holds themes, only themes and no widget. > tw.jqgrid and tw.jqmultiselect have it as a dependency so they can be > designed. > > anyway it was only a suggestion :)
I had a look, but it doesn't work that way. abl.jquery.ui declares themes based on a key, and you select one. So if anything, tw.uitheme could hook into that, not the other way round. The reason is that we want a simple way of configuring the used theme. And we need a way to filter out unwanted theme CSS when aggregating CSS - which tw.uitheme doesn't allow in the current state. So I think the best way would be to put the themes into abl.jquery.ui itself. Diez -- You received this message because you are subscribed to the Google Groups "TurboGears" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/turbogears?hl=en.
