From: Shane <sh...@lo...> - 2005-10-25 04:37:33
|
question regarding the css_type table: currently I see these types defined: mysql> select * from css_type; +------+------------+----------+ | ctid | name | ordernum | +------+------------+----------+ | 1 | base | 1 | | 2 | page | 2 | | 3 | theme | 3 | | 4 | user_theme | 5 | | 5 | print | 6 | | 6 | skin | 4 | | 7 | handheld | 7 | +------+------------+----------+ 7 rows in set (0.13 sec) if a plugin adds a .css file, what should the type be? (I thought maybe 'plugin', but there's no such type). what's the 'user_theme' for? Shane |
From: Tim V. <tv...@va...> - 2005-10-27 18:25:21
|
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. http://slash.lottadot.com/faqster.pl?op=view&fid=2#q110 -------------------------------------------------------- If the plugin's css file is to be shown only when your plugin's perl script is run (ie plugin.pl) then you should create the plugin with type='page'. If the plugin's css file is to be shown when another script is run, then it should still be 'page'. If the plugin's css file is to be shown all the time, then use type 'base'. That way, a site's theme can still over-ride the plugin's style sheet. -------------------------------------------------------- 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. --Tim Shane wrote: > question regarding the css_type table: > > currently I see these types defined: > > mysql> select * from css_type; > +------+------------+----------+ > | ctid | name | ordernum | > +------+------------+----------+ > | 1 | base | 1 | > | 2 | page | 2 | > | 3 | theme | 3 | > | 4 | user_theme | 5 | > | 5 | print | 6 | > | 6 | skin | 4 | > | 7 | handheld | 7 | > +------+------------+----------+ > 7 rows in set (0.13 sec) > > > if a plugin adds a .css file, what should the type be? (I thought > maybe 'plugin', but there's no such type). > > what's the 'user_theme' for? > > Shane > > > > ------------------------------------------------------- > This SF.Net email is sponsored by the JBoss Inc. > Get Certified Today * Register for a JBoss Training Course > Free Certification Exam for All Training Attendees Through End of 2005 > Visit http://www.jboss.com/services/certification for more information > _______________________________________________ > Slashcode-development mailing list > Sla...@li... > https://lists.sourceforge.net/lists/listinfo/slashcode-development |
From: Shane <sh...@lo...> - 2005-10-27 20:22:58
|
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 |