[thesite] Bio, User Pages, CSS

[aardvark]

> From: ".jeff" <jeff at members.evolt.org>
> 
> > I'm in favour of this approach ..
> ><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> 
> as am i.

+1... but if it is just in the template, and not embedded in the 
content, why waste CPU cycles parsing that for every user when it 
can just be in the template?  it *is* a nice approach, but is it 
programming just for programming's sake?  who's time will it save?  
is it that hard to class them vs. write the function?

> ><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> > and in fact wondered why it was done the current way.
> ><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> 
> me too.
> 
> ><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> > I'd really like to get Adrian's opinion on this.  I'm
> > wondering if there's a prob with NS4.x not inheriting
> > properly, and that's why the current approach was taken.
> ><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> 
> good question.  i don't personally know of any issues with nn4 and
> this approach, but i've been known to learn a thing or two new once in
> a while.

i *did* have problems with inheritance, and i think it was NN4.x.... 
however, i can't recall exactly... if i had time right now, i'd mock it 
up and test, but i suggest you try a couple links without it on teo, 
maybe with the cascading style in the head temporarily, so we can 
get more users than just me to test it (don't have NN4.x at home 
anymore)...

> ><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> > Now my question is, displaying the user's bio on the
> > user's page .. like we discussed, then that part of the
> > user's info on their user's page (link, not edit) will
> > need to be within the class="side" container?
> ><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> 
> ok, yes.  i wasn't considering adding the classes to the links in the
> bio in the display process but rather in the add/edit process so it
> only happens once.  that way, any other place the bio is displayed
> it's already got the classes on the links.

huh?  as long as you don't mean hardcode classes into the 
content, just the template...

> i like the approach of changing the css though.  that's a much better
> idea and solves the issue of wanting to show the bio without being in
> a container with a class="side".

try it... lemme know... won't be around for a couple days, though, 
to test it...