cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hochsteger Andreas /INFO-MA <Andreas.Hochste...@oeamtc.at>
Subject RE: [CForms] - No @id generation for <wd:output>
Date Wed, 18 Feb 2004 08:12:21 GMT
It will also allow us to write client JavaScript functionality in a
"standard" way.
Perhaps this would also allow us to "plug in" client side functionality
which is compatible with all Cocoon Forms and you only do it if you really
need it.

Andreas Hochsteger

> -----Original Message-----
> From: Hugo Burm [mailto:hugob@xs4all.nl]
> Sent: Wednesday, February 18, 2004 8:47 AM
> To: dev@cocoon.apache.org
> Subject: RE: [CForms] - No @id generation for <wd:output>
> 
> 
> I already changed my own Woody version with the same 
> modification for the
> same reason. So I think we need it.
> 
> Hugo Burm
> 
> > -----Original Message-----
> > From: Antonio Gallardo [mailto:agallardo@agssa.net]
> > Sent: Wednesday, February 18, 2004 6:37 AM
> > To: dev@cocoon.apache.org
> > Subject: Re: [CForms] - No @id generation for <wd:output>
> >
> >
> > Joerg Heinicke dijo:
> > > Though it's only one additional element I would not like to
> > have it in
> > > the default stylesheets. You can simply extend them for
> > your usage and
> > > overload the template for the @type="output" widget and add
> > there your
> > > span element with the id.
> >
> > I know I can add this just for my own version. But AFAIK, JS
> > client-side
> > is a MUST if we are looking for a good UI in webapp. In this
> > way is better
> > to add an @id. The <span> tag is not a must. But I prefered
> > to add it just
> > to follow the same tree structure as the other fields in the CForms
> > rendering.
> >
> > WDYT?
> >
> > Best Regards,
> >
> > Antonio Gallardo
> >
> >
> 
> 
> 
> Wurde auf Viren ueberprueft!!!
> 
> 
> 
> Wurde auf Viren ueberprueft !!!
> 

Mime
View raw message