[thesite] Additions to default CSS file

[.jeff]

aardvark,

><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> From: aardvark
>
> > agreed.  and so long as we're the only ones providing
> > the stylesheets for the site it will likely not be an
> > issue.  however, if we allow users to create their own
> > *then* it will become a problem.
>
> this is true, but it goes back to the relationship
> between elements that i tried to create, so that only a
> few colors would be needed, which would then color a
> number of elements a piece... the vestigial comments are
> still in isaac.css...
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><

agreed.  most of that is still in place.

><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> since, however, i think the approach now is to let the
> user customize every element regardless of other
> elements, then yes, there is the potential a user could
> make something disappear... but if we're going to give
> the user that control, then he/she should be capable of
> not fixing those things... i don't think we need to
> idiot-proof it for our audience...
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><

i disagree.  here's why.  we're giving the user the ability to style the
background color of three different cells.  for one of those cells the user
may decide they'd like to set the background color to be the same as the
foreground color for the links in the main content area -- as is the case
with evoltoldschool.css to recreate v1.0 look and feel.  however, without
giving them the ability to color the links in the upper two cells
independently of the links in the content area, but instead forcing it to be
the same color as the links in the main content area, we've unnecessarily
made it impossible to do without hiding key elements/functionality of the
site.

><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> i still like stealth better -- namely because no one
> else who saw it could read anything...
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><

select all and you can read it just fine.  ;p  only a geek would think of
that though.

><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> and yes, i see your point...
>
> i think a better solution, however, is ensuring the
> predefined CSS files don't make that mistake...
>
> the fallback should be classing...
>
> IOW, my preferences/arguments still stand... (like
> allowing our users to mess it up because we trust
> they might actually go and fix it)...
>
> er... am i making sense now (so sleepy)?
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><

yes, but i think you're answer dodges the current situation.  in other
words, how are we supposed to make evoltoldschool.css work with the existing
site while still maintaining the old v1.0 look and feel?

i've offered my solution to the problem.  i'd like to hear yours.

thanks,

.jeff

http://evolt.org/
jeff at members.evolt.org
http://members.evolt.org/jeff/