[thesite] alternate color schemes

[jeff]

rudy,

:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
: From: rudy
:
: > one must select at least one favorite.
:
: well, sure, except the page logic has to be
: prepared to handle the case if you didn't do
: that -- if the query to pick one of your
: favourites comes up empty, the page could
: then pick either one of yours at random (or
: the first one), or else pick one of the defaults
: at random...
:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

i'd prefer to handle it even further back than that.  at least one of the
schemes is selected as a favorite no matter what.  this should be handled by
the tool that facilitates the user's interaction with schemes and
addint/editing/deleting favorites.

:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
: > how do you propose that i, as a user, could
: > select on of isaac's schemes as my favorite?
:
: two ways, an easy way and a hard way -- but for
: both, we first need a "browse other users' schemes"
: function which allows you to view isaac's schemes
: and press a button to select one  of them as one
: that you want to use
:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

of course.

:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
: you could stop right there (with no further
: functions) and simply load those values into
: the variables to be used throughout your session
: -- but to use this scheme again on a future
: session, you'd have to go view isaac's again
: and select it again
:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

yeah, how annoying.

:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
: to go on, though, and save your choice, there's
: an easy way and a hard way -- the easy way is to
: copy the rows from isaac's and store them as
: yours, while the hard way is to have another
: database table (or tables -- this would be a
: many-to-many relationship) that lets you "point"
: to isaac's
:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

the easy way would generate *tons* of data rather quickly if this system
gets used as much as i think it'll get used.  it also is akin to
plagiarizing another user's hardwork.

personally, i'd prefer, for a number of reasons, to do it the hard way.  in
fact, to me, the "hard way" seems more like the easy way when it comes to
actually implementing it in the cf.

:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
: i'd much prefer the easy way, because once the
: rows are copied over to yours, you could then go
: in and tweak them, including marking it as one of
: your favourites
:~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

i don't want to make it that easy to steal another user's hard work.

i'd much rather see an association table between schemes and users.

scheme_favs

pk   id        numeric(8) NOT NULL
fk   userid    numeric(8) NOT NULL
fk   schemeid  numeric(8) NOT NULL

it's super easy to enforce a favorite now.  if they don't pick any then we
insert the schemeid of the default evolt scheme as their favorite.

thanks,

.jeff

name://jeff.howden
game://web.development
http://www.evolt.org/
mailto:jeff at members.evolt.org