[thesite] themes milestone plan?

[rudy]

> when the style from the library is chosen, it just creates the
> schemelements associated to that user (um, I hope I said
> that right. I haven't looked over this part of the schema yet).

yeah, there are some tables just sitting there waiting to be used

to be honest, i haven't looked at them in a while either

> Rudy/jeff/etc, do you think it would be a bad thing to have a
> user in the database for each default site scheme? If so,
> what do you propose we handle default schemes? Surely
> not hard-coded or redirecting to a weodefault.css file, I hope.

this sort of came up recently when we decided to delete the user with
userid=0

not exactly sure where the defaults should go, and whether to tie them to a
"default" user or not, but you're right, no way we want them hardcoded

the original concept was that a user would be able to save a unique scheme,
and then other users would be able to pick this scheme, subject to PRIV
constraints, either to use just for viewing (so the scheme id would have to
be saved in the cookie) or to use as a basis for designing a new one...

if i could only get out from under this pile of backlogged work i have, i'd
give it some more thought and design something more comprehensive for the
defaults...

i have no problem responding to specific questions, though, so if anybody
has further ideas or input on this subject, please, fire away...


rudy