cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bruno Dumon <br...@outerthought.org>
Subject Re: cforms: events on widget instances
Date Fri, 30 Apr 2004 14:01:01 GMT
On Fri, 2004-04-30 at 14:30, Vadim Gritsenko wrote:
> Sylvain Wallez wrote:
> 
> > Bruno Dumon wrote:
> 
> ...
> 
> >> And now the practical side: example usage in flowscript:
> >>
> >> form.getWidget("test").addActionListener(newActionListener(function(event) 
> >> {
> >>        print("hi there");
> >> }));
> >>
> >> where the newActionListener function is as follows:
> >>
> >> function newActionListener(listenerFunction) {
> >>    var listener = {actionPerformed: listenerFunction };
> >>    var adapter = new
> >> JavaAdapter(Packages.org.apache.cocoon.forms.event.ActionListener,
> >> listener);
> >>    return adapter;
> >> }
> >>
> >> Question: do we add these newActionListener and newValueChangedListener
> >> functions to the (javascript) form object, or as separate functions next
> >> to it? 
> >>
> >
> > It could also be an additional method of ScriptableWidget, which would 
> > take care of the adaptation.
> 
> 
> Agreed. And syntax should become then simply:
> 
> form.getWidget("test").addActionListener(function(event) {
>        print("hi there");
> });

Saw my message about the v3 api?

there I've implemented it as:

form.model.test.onActivate = function() { print("hi there"); }

which is still more readable and (I think) flexible enough.

-- 
Bruno Dumon                             http://outerthought.org/
Outerthought - Open Source, Java & XML Competence Support Center
bruno@outerthought.org                          bruno@apache.org


Mime
View raw message