How about a 3.0 compatibility flag (off by default) that would let
you use old 3.0 DTDs (or at least most of them). That way new users would
start out in the new file structure, but current users would have a crutch
to transition them into the 4.0 world without having to rewrite lots of XML?
It's not worth worrying about if you're the developer and know
what's going on, but 4 or 5 of these little "not worth worrying about it"
changes can make a user who upgrades from 3.0 to 4.0 pull his hair out and
kick the dog in frustration.
It's like when Sun decided they were going to change the way
timezone formats were stored between 1.4.2 and 1.4.3 (if memory serves) and
broke a bunch of my code. Sure, it was easy to fix, but first there was the
three hours of disbelief that upgrading my JVM would cause my code to light
up like a Christmas tree, then the hour spend on the change notes to find
what the heck they'd done, then the ten minutes to fix it.
--- Pat
> -----Original Message-----
> From: Gregg D Bolinger [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, May 10, 2005 9:22 AM
> To: Tapestry users
> Subject: Re: 4.0: listeners
>
> I think that there is a trade off between making things easier for 3.0 app
> transition and making things easier for new 4.0 development. It's probably
> a
> catch 22. Just typing the actual listener method name is much shorter and
> less likely prone to fat fingering than the 3.0 way.
>
> I'd say it's really not that big of a deal either way and definately not
> worth worrying about. ;)
>
> Gregg
<snip>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
