-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> From: "rudy" <r937 at interlog.com>
> Subject: Re: [thesite] themes milestone plan?
>
> > 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
Well, I just did (assuming the oracle4.gif file is current for that
section). ;-)
> 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
Would be odd showing up in the user search, but other than that...
*shrug*
> 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...
Ok. Thanks for the clarification, because I obviously didn't get that
from when I looked at the schema last time. There is a field *IN*
SCHEME named USERID. Personally, I would have thought this field
would be in USER from what you describe. IOW, that SCHEME would be
independant of USER rather than being connected to a single user. If
I may ask, why'd ya do it this way? And I'm not sure I see the
usefullness of PRIV here, other than to hide my horrid design skills
from you other members who would laugh your asses off at me. Not that
I'm trying to rekindle old discussions or anything. I'd just like to
understand.
> 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 hear ya.
- --
mattwarden
mattwarden.com
-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 7.0.3 for non-commercial use <http://www.pgp.com>
iQA/AwUBOxKy8XgH0dUmEhrcEQIIqQCgipyXdmMAkudyRC4fz5FWYqnN/hgAn2Ku
edkMLDWHVJB5mVZy2OOuUDC+
=uLWm
-----END PGP SIGNATURE-----