Re: [Slashcode-development] css_types?

[Shane <sh...@lo...>]

On Oct 27, 2005, at 2:25 PM, Tim Vroom wrote:

> After talking to you online I'll just add the text and link to the  
> FAQ you
> added since that covers all the possibilities well.
> [...]
> user_theme is one of the last css types called so basically would  
> allow a user
> to override a site's look and feel.  Right now this is used for  
> simpledesign,
> and lowbandwidth types.
>
> You could for instance add a preference that allowed a user to set  
> their
> sitewide theme to one of 5 choices.  Right now the theme selection in
> getCSS() in MySQL.pm checks for a user's simpledesign preference
> and picks a css file based on that, or if that's not set falls back  
> to $user->{css_theme};
>
> If you had a preference which updated that, you could have user  
> selected
> themes, simpledesign being one option, that's currently controlled  
> by a different
> preference.
>
> The skeleton is there to allow for such things, however we may need  
> to separate
> out simpledesign into its own thing if we want to allow for both  
> simpledesign, and
> a user_theme to be triggered at the same time.

Oh, very cool. Talk about skinning the skins :)

Now all we need is a method for users to supply their own css, and  
save that as a byte-limitted txt field such that when they hit the  
site it'd pull that push it is to the end of the css-list. Hence, the  
user html trumping the base/plugin/theme css.

I don't if that's where all this was headed. I'm just rambling. But  
I'd think with /.'s geek traffic it'd be like an easy or lite way to  
do a greasemonkey effect.

  Shane