>On 5/21/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
>I'd love to see more comments. Honest comments about your experiences
going
>from 3 to 4, your thoughts on better adoption, how you feel about
Tapestry 5
>(especially if you are in a situation where you'll need to upgrade).
Please
>av
On 5/21/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
I'd love to see more comments. Honest comments about your experiences going
from 3 to 4, your thoughts on better adoption, how you feel about Tapestry 5
(especially if you are in a situation where you'll need to upgrade). Please
avoid any
Annotations are the reason XML went away, which has opened up lots of other
possibilities (including true component subclassing). Once the hurdle of
backwards compatibility was (by)passed, many more and more powerful ideas
have come forwards (case insensitivity, event notifications instead of
list
I dunno, but is the Annotation feature in JDK 5 the reason why T5 change so
radically?
--
Best wishes,
Eko SW
http://swdev.blogs.friendster.com/my_blog/
+1
> Howard,
>
> Tapestry development is a great responsability, with good and bad comments
> from everywhere.
> We have some app in T3, others moved to T4, and new projects are already
> using T5, I think that you''re on the right direction, doing a great job.
>
> like Jesse said, "T5 is everythi
Howard,
Tapestry development is a great responsability, with good and bad comments
from everywhere.
We have some app in T3, others moved to T4, and new projects are already
using T5, I think that you''re on the right direction, doing a great job.
like Jesse said, "T5 is everything we've always w
I don't really want to add my comments to a blog but I guess I can make some
here.
Specifically - I'll just go down the list he referenced at the top as being
concerns of sorts:
-) JSF - Yes, there certainly is a lot of news about JSF all the time. I
hear that some people are actually using it
