[Seaside] CSS dinamycally manipulated

Boris Popov boris at deepcovelabs.com
Sat Jun 9 22:07:12 UTC 2007

+1, the whole reason behind css is to separate it from content, why mash them back together? Instead we should remove #style: and go the other way.


(Sent from a BlackBerry)

----- Original Message -----
From: seaside-bounces at lists.squeakfoundation.org <seaside-bounces at lists.squeakfoundation.org>
To: 'Seaside - general discussion' <seaside at lists.squeakfoundation.org>
Sent: Sat Jun 09 15:04:34 2007
Subject: RE: [Seaside] CSS dinamycally manipulated

> I believe that having a dynamic css doesn't urge the 
> designers to program it. 

Of course not, because designers don't program.

> I don't like much this old way of 
> thinking: code and coders at one side, design tools and 
> designers at the other one. Data vs code.

It's not old thinking, it's reality!

> Coders and designers should do there work orthogonnally 
> without annoying each other and with their own point of view. 

Agreed, hence HTML for programmers, and CSS for designers.

> But why not doing this on the same language core. 

Because if designers understand the language we work in, they aren't
designers, they're programmers.

> It would even be nice for designers to have a bit of coding 
> possibilities like macros. This standard philosophy results 

Then they become programmers, not designers.

> to the failure of Lisp. I hope the trendy solution like 
> XML/XSLT would give us a future way of composing 
> page/wiki/application in a more DSL fashion.

You have a design DSL already, it's called CSS.

Seaside mailing list
Seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20070609/825ce460/attachment.htm

More information about the Seaside mailing list