On 7/27/06, Sam Gendler <[EMAIL PROTECTED]> wrote:
One of the reasons I didn't release it wednesday. The familiar "ResponseBuilder" interface is now stored in the IRequestCycle. Call cycle.getResponseBuilder().updateComponent(String compId) to get your select box updated.
I'm trying to start "small" with features and work my way out from there. I thought about adding updateComponents to EventListener but just haven't gotten around to it yet. (or had a chance to think through this kind of logic as thoroughly as I'd like)
Nothing has changed from a "user" perspective other than the dialog vs alert box changes. Under the hood is quite a different story.
The source is in the apache tapestry svn repo, like everything else.I plan on running a demo version of TimeTracker when I release tapestry. (hopefully Friday now)
As much as I would like more people to use Tapestry 4.1, if you are under tight deadlines with no room for error upgrading to 4.1 might not be the safest option right now. I can't promise I'll be able to respond to all of your deadline needs as timely as you'd like as I also have my own deadlines.
I finally had a chance to read through the new documentation, and it
is really helpful, but raised a couple of questions that, if answered,
might allow me to start playing around with Tap 4.1 (if I could ever
figure out how to build and use it, anyway). The new features look
like a huge step forward, so I am anxious to start playing with it, so
that any eventual conversion of our current projects will be smooth.
First, going back to a question I asked a week ago or so - I asked
about updating a select list based on a value chosen in another list,
and you suggested EventListener. I see now what your intent was. The
one thing I don't understand from the documentation, however, is how I
would update the other select box. I was hoping to find a parameter to
the annotation which allows me to specify the set of ids to be
updated, similar to an AjaxForm, but I don't see any such parameter.
So if I have two select lists - select1 and select2, how do I set up
an EventListener on select1.onChange (or whatever the event is
actually called), update the model for select2, and cause select2 to
be redrawn? I am sure it is possible, as this is exactly the kind of
functionality ajax is for, but I'm not seeing it.
One of the reasons I didn't release it wednesday. The familiar "ResponseBuilder" interface is now stored in the IRequestCycle. Call cycle.getResponseBuilder().updateComponent(String compId) to get your select box updated.
I'm trying to start "small" with features and work my way out from there. I thought about adding updateComponents to EventListener but just haven't gotten around to it yet. (or had a chance to think through this kind of logic as thoroughly as I'd like)
Second, the client-side validation stuff looks very interesting, but
it wasn't entirely clear how it is intended to be used. I assume that
a profile is automatically generated by the various validators added
to a tapestry form, so that behavour on existing forms won't change
when moving to 4.1 from 4.0, except for how the validation messages
manifest themselves.
Nothing has changed from a "user" perspective other than the dialog vs alert box changes. Under the hood is quite a different story.
The form validation docs include a screenshot of Tapestry TimeTracker
app built in tap 4.1. Where would I find the source for this app, or
better yet, a running sample so I can check out tap 4.1 functionality
without having to struggle through maven and such.
The source is in the apache tapestry svn repo, like everything else.I plan on running a demo version of TimeTracker when I release tapestry. (hopefully Friday now)
Finally, while I'm sure the download documentation is sufficient for
someone who knows their way around maven, would it be possible for you
to provide instructions for those of us who just want to use maven to
download the jar files before adding them to their old projects? I
tried to deal with maven, but I couldn't get a number of things to
work correctly, and I'm certainly not about to change to a new build
system on my existing projects - at least not until we are under less
tight schedule deadlines.
As much as I would like more people to use Tapestry 4.1, if you are under tight deadlines with no room for error upgrading to 4.1 might not be the safest option right now. I can't promise I'll be able to respond to all of your deadline needs as timely as you'd like as I also have my own deadlines.
Thanks.
--sam
--
Jesse Kuhnert
Tacos/Tapestry, team member/developer
Open source based consulting work centered around dojo/tapestry/tacos/hivemind.
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ Tacos-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tacos-devel
