[SPAM] [kpax-devel] class and id for generated web form fields

Sven Van Caekenberghe scaekenberghe at common-lisp.net
Fri Jul 13 09:52:31 UTC 2007


Maciej,

On 04 Jul 2007, at 16:01, Maciej Katafiasz wrote:

> Hello,
>
> I've been playing with KPAX, and so far it works pretty nicely (save
> for a couple of SLIME and misc issues I will be detailing in another
> email). However, I've now arrived to the point where I'd like to use
> DEFWEBFORM'd forms. It all looks very nice, but it seems that default
> renderers have no ability to specify arbitrary attributes, in
> particular that means no way to specify `class' and `id' for elements,
> and that makes attaching CSS hard.
>
> So, is there an easy way to attach those attributes to fields I'm
> missing? I am aware I can elect to use my own renderers, but I really
> don't want to recreate all that logic. Looking at the definitions of
> generate-text-area and friends, there's no way to inject any more
> parameters than they're already taking. In case it really needs
> hacking on KPAX source, is there any obvious approach? And what
> sources/version should I use as the basis? My installation of KPAX
> reports "$Id: nkpax.asd,v 1.26 2004/11/10 15:20:55 sven Exp $", but
> that's an obvious lie, in any case it was asdf-installed 2 days ago.
>
> Cheers,
> Maciej
> _______________________________________________
> KPAX-devel mailing list
> KPAX-devel at common-lisp.net
> http://common-lisp.net/cgi-bin/mailman/listinfo/kpax-devel

The way KPAX interacts with CSS is a bit old school (let's say pre- 
AJAX hype).
Currently only hooking CSS on the existing classes and ids is possible,
although there is a form-id option to defwebform.
But you are right: some extra per elemment specs would be welcome.
The whole defwebform concept is layered on top of the core KPAX  
functionality,
so changing/hacking it is certainly allowed.

Regards,

Sven
  



More information about the kpax-devel mailing list