Re: WAComponent to PDF

Otto Behrens wrote:
>We took all our CSS out of Seaside and put it on disk. We use less and
>what not to "compile" it and get the web server to produce it. Mainly
>because 1. Seaside is too heavyweight to serve (dynamically created)
>CSS up as well as the HTML and 2. The tools are a but scrappy to deal
>with CSS properly (but would be nice if we had a Seaside-like library
>that helps with CSS).

Did you check:  http://gcotelli.github.io/RenoirSt
for Pharo?

Bye
T.