cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Lowe <mel...@gmail.com>
Subject Re: Dispatching flowscript commands
Date Tue, 15 Feb 2005 14:14:02 GMT
No thats not the problem, although checging to submits was required anyway. 

Guess its more trial and error looking at the source code and the
fragments that are commonly refered to as documents..

Mark


On Tue, 15 Feb 2005 15:00:24 +0100, Mark Lowe <melowe@gmail.com> wrote:
> I think I just found what the problem is.. These crazy crack smokers
> who build this app are using buttons rather than submits.. Which is a
> shame because they've used form.submitId in places also. They should
> have there fingers broken..
> 
> 
> Mark
> 
> 
> On Tue, 15 Feb 2005 14:25:02 +0100, Jorg Heymans <jh@domek.be> wrote:
> > you can attach flowscript functions in event handlers if this is what
> > you're looking for.
> >
> > for a selectionlist widget you could do eg this
> >
> > <fd:on-value-changed>
> > <javascript>
> >  somewidget.setSelectionList( myflowscriptfunction(), "value",
> > "label"); </javascript>
> > </fd:on-value-changed>
> >
> > HTH
> > Jorg
> >
> > Mark Lowe wrote:
> > > I'm looking through the docs for any mechanism for dispatching
> > > flowscript fucntions from a form.. I'm thinking along the same lines
> > > as JSF where buttons of different names are mapped to a method in a
> > > backing bean..
> > >
> > > Mark
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> > For additional commands, e-mail: users-help@cocoon.apache.org
> >
> >
>

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


Mime
View raw message