[Seaside] CSS dinamycally manipulated

Jason Johnson jbjohns at libsource.com
Mon Jun 11 17:46:10 UTC 2007

Boris Popov wrote:
> <tongue-in-cheek>
> You are joking about expensive editors, aren't you? :) Let's look at two
> most popular CSS editors in terms of developer time at $60/hr,
> http://macrabbit.com/cssedit = $29.95 = 30 minutes
> http://www.newsgator.com/Individuals/TopStyle = $79.95 = 80 minutes
> I bet if they cost 10 or 20 times more, I'd still let my designer
> expense it, wouldn't you?
> </tongue-in-cheek>
> Cheers!
> -Boris
But since these aren't integrated with Seaside I don't see how they
could have the same level of flexibility one could have from within
Seaside.  For example, if CSS became a first class option [1] and a
WYSIWYG style editor was made to replace the style editor we have now
(that big box that just dumps CSS text into a class side method) then
the editor could let one design components [2] individually.  This way,
since the style is something the component itself carries with it, the
component would look how the designer styled it no matter where it wound
up in the web application.  And if a developer used an old component
again in a new set of pages, it still has the same look the designer
gave it originally.

There are a lot of options here, and if no one else is ever interested I
will eventually do it myself because for me and the designers I work
with it would just be too useful not to do.

[1]  NOTE: This isn't me trying to put work on Philippe or Lukas'
plate.  This isn't a priority for them as you stated earlier, and I
don't blame them at all.  This is just me expressing an idea I don't
have time to do right now in case someone else found it interesting
[2]  By component I mean a class or group of classes that make up some
functionality that can stand on it's own.  Examples: a calendar, the
counter, the page display functionality in the sushi store, a big bold
dynamic page title, a PRWidget, etc.

More information about the Seaside mailing list