You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cocoon.apache.org by Mark Lowe <me...@gmail.com> on 2005/02/15 11:05:24 UTC
Dispatching flowscript commands
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
Re: Dispatching flowscript commands
Posted by Mark Lowe <me...@gmail.com>.
Interestingly form.submitId or the old
form.getWidget().getSubmitWidget() or form.getSubmitWidget()..
Its a pretty basic question is there no one who knows how to do this?
Mark
On Tue, 15 Feb 2005 11:05:24 +0100, Mark Lowe <me...@gmail.com> 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
Re: Dispatching flowscript commands
Posted by Mark Lowe <me...@gmail.com>.
> I see you're getting into the true cocoon spirit!
Perhaps reluctantly yes..
I solved that problem, I'm still trying to distingish between whats up
with cocoon and the code these crack addicts wrote..
The nature of my problem is that I didn't reflect on how flowscript
works with showForm() the submitId wont appear until the submission
gets passed that bit of the code. I was errornously thinking that
submitId was just a wrapper around the request parameters, but when i
viewed the source there was no way that could have been the case.
I haven't found a way of mapping buttons to functions so I could have
a crud.js with save,delete and so on run on different button presses
(at least without client-side javascript which I don't like doing).
Thanks for the replies
Mark
On Tue, 15 Feb 2005 15:38:30 +0100, Jorg Heymans <jh...@domek.be> wrote:
>
>
> Mark Lowe wrote:
> > Guess its more trial and error looking at the source code and the
> > fragments that are commonly refered to as documents..
>
> I see you're getting into the true cocoon spirit!
>
> ;)
> Jorg
>
> ---------------------------------------------------------------------
> 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
Re: Dispatching flowscript commands
Posted by Jorg Heymans <jh...@domek.be>.
Mark Lowe wrote:
> Guess its more trial and error looking at the source code and the
> fragments that are commonly refered to as documents..
I see you're getting into the true cocoon spirit!
;)
Jorg
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org
Re: Dispatching flowscript commands
Posted by Mark Lowe <me...@gmail.com>.
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 <me...@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
Re: Dispatching flowscript commands
Posted by Mark Lowe <me...@gmail.com>.
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
Re: Dispatching flowscript commands
Posted by Jorg Heymans <jh...@domek.be>.
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