Weblocks already has css file concatenation at the widget level. But that
means writing css, of course.

I do know that when I wanted something to just work, I put it in the render
fn as inline CSS (:style attribute).

So I think your idea is very promising.

On Tue, Jun 5, 2012 at 12:05 PM, Leslie P. Polzer
<[email protected]>wrote:

>
> Scott L. Burson wrote:
> > Hi all,
> >
> > As we probably all know, CSS as a language has its limitations,
> > notably the complete absence of any abstraction mechanisms.  I've been
> > meaning to check out some CSS compilers, but haven't yet.
> >
> > But in the course of fiddling with my site the other day, I
> > experimented with some layout by just supplying :STYLE attributes
> > inside WITH-HTML, rather than by assigning classes and adding clauses
> > to the CSS files.
> >
> > And then it struck me.  Why do we Weblocks users need CSS files at
> > all?  We're generating the HTML anyway -- why don't we generate the
> > styles at the same time?  We would have all the abstraction
> > capabilities of Common Lisp at our fingertips and we wouldn't need to
> > earn yet another language.
>

-- 
You received this message because you are subscribed to the Google Groups 
"weblocks" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/weblocks?hl=en.

Reply via email to