Jesse, in the new tapestry, is there some chance to see an Ajax @PropertySelection?
On 5/14/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote:
Hah....Hadn't even noticed how dojo.event.connect() is already very similar to Howard's direct listener method stuff...As in the parameters are optional but will be automatically filled in for you as you define them... Wish more people realised what kind of innovation has already been created in tapestry as it exists today. All of these new features are starting to just naturally plop in where they make sense, because the framework was already designed that way. How cool ! :) On 5/14/06, Jesse Kuhnert <[EMAIL PROTECTED]> wrote: > > Starting to do more logic similar to > http://tacos.sourceforge.net/components/AjaxEventSubmit.html, and was > looking for input from people on how they like the interface. > > This is what I'm starting with for now..In the pasted in example below I > have one "Autocompleter" component defined on my page, and this listener > method: > > /** > * Invoked when an item is selected from the project > * selection list. > */ > @EventListener(events = {"selectOption"}, > targetIds = { "component:projectChoose" }) > public void projectSelected() > { > > } > > Input on anything at all is welcome. Even small detaisl like the naming of > parameters. (targetIds accepts string constant values or OGNL expressions ). > I'm also going to bind it on the client side in such a way that if I had > defined the appropriate String/event parameters to projectSelected() that > the javascript method arguments would also be matched. For example, the > client side event I'm binding to has a function that looks somewhat like: > > selectOption: function(evt) { > ... > } > > I could then change my direct listener method to look something more like: > > /** > * Invoked when an item is selected from the project > * selection list. > */ > @EventListener(events = {"selectOption"}, > targetIds = { "component:projectChoose" }) > public void projectSelected(JsEvent event) > { > if (event.isMouseClick() || event.foo()) > } > > This is an extreme example, as the client function parameter is actually a > js event, but there are many other scnerios where the parameters will be > other things, like Strings / dom nodes /etc,....I don't know.... > > It's basically going to try and provide as much functionality as makes > sense to encapsulate dojo.event.connect. That means that specifying > "before" / "after" etc style AOP logic will also be possible. > > This is a really important feature to get right, so please provide input > if you can :) > > -- > Jesse Kuhnert > Tacos/Tapestry, team member/developer > > Open source based consulting work centered around > dojo/tapestry/tacos/hivemind. > -- Jesse Kuhnert Tacos/Tapestry, team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind.
-- Thanks, Henri.
