Re: CSS Framework?

I do the same as Damir. Although I am new to css (and html) I feel that the whole approach (including 'rules') is still in a state of transition. So I think that keeping our Smalltalk code (which is stable) separate will protect us from css changes and minimise maintenance.

A+

Damir Horvat wrote:

Janko Mivšek wrote:
  > Now we have a strict separation and this is good every time you are
  

working with web designers. they just need to provide a CSS for a design 
and you put that in one css method and that is.
    

I'm doing it this way - one css method for all css. Like you said, 
designers will always give you one or two .css files. And this is just 
copy'n'paste. It can't get simpler.

If designer is cheating and using inline css (like I do :-) then maybe 
css generated by Aida could be an option.

Css is still untamed beast. I'd go with simpler solution as keeping 
up2date with all browsers and CSS specs is IMO just to hard.

br,
Damir
_______________________________________________
Aida mailing list
Aida@...
http://lists.aidaweb.si/mailman/listinfo/aida
  

_______________________________________________
Aida mailing list
Aida@...
http://lists.aidaweb.si/mailman/listinfo/aida