> -----Original Message-----
> From: Erik Hatcher [mailto:[EMAIL PROTECTED]
> Sent: Friday, May 06, 2005 11:21 AM
> To: Tapestry users
> Subject: Re: As a User, which two items would you personally most like to
> see in the next Tapestry Release?
<snip>
> Patrick - first, your e-mail replies are not clearly separated from
> what you quote, so it is hard to follow what someone else said versus
> what you add.
Sorry, I'm using outlook for email and I hadn't bothered to set carot
quoting yet on my laptop. Hopefully this will be easier for everyone to read
:).
>
> Next - Mindbridge is asking you so that he can help alleviate the
> issue you've brought up - so if you could bear with him and ensure
> that his components fix the issue then he'll integrate them into
> Tapestry 4.0!
>
I'm happy to help test and/or answer questions. As you've no doubt
guessed the rewind cycle is my personal bugaboo so anything I can do to help
improve its handling is a good thing :).
On the specifics of the rewind cycle, I think it's really two
distinct things that I find "unnatural".
A) The rewind cycle is frail and can get confused unless you use
techniques like Mindbridge suggested. I'd love to see those sorts of
"guaranteed-safe-rewind" components become the default for 4.0 (maybe
deprecate foreach?)
B) On a parallel but slightly unrelated note I still have trouble
with the order of operations of listeners where they get called during
rewind. As Dennis mentioned it requires sort of weird programming juditsu to
have listeners fire *during* rewind. I'd love to see my listeners always
fire after rewind when it was safe to do things.
In any even I'm glad to hear it's being looked at for 4.0. It may be
a relatively minor issue for some people and some sorts of apps, but for the
kind of stuff I do (which works with lots of users and highly volatile data
sets), it's definitely the top of my personal wish list.
--- Pat
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
