On Mar 29, 1:14 pm, Vyacheslav Akhmechet <[email protected]> wrote:
> On Sun, Mar 29, 2009 at 4:19 AM, Leslie P. Polzer<[email protected]>
> wrote:
> > What's so horrific about it?
>
> Everything :)
>
> > Where's the problem here?
>
> Non-lisp dependencies complicate the deployment process. It's fine,
> but if I can get away with using pure-lisp libraries, I prefer to do
> it.
>
> > On the lower level we don't need to agree on a format.
>
> That's true. I sent this mail mostly to find out what (if any) tools
> people are using so that I could save myself some time trying
> different alternatives. I didn't mean to suggest that this aspect
> should be standardized (although one good way of doing it should be
> provided out of the box at some point).
Maybe I'm missing the point of this post, but CSS is actually pretty
easy to generate... basically you have a pair-list nested into a list
with a class definition.
i.e. (class (attribute val attribute val attribute val)) == class
{attribute: val; attribute: val; attribute: val;}
or ((type class) (attribute attribute attribute)) == type.class
{attribute:val; attribute: val: attribute: val;}
It would be nice to be able to generate 'themes' and then whenever we
encounter a class in render body it changes the class to match the
theme currently selected by the user.
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
