Hi Rob or however you are!
Nice to see you spicing up this list ;)
Your comments are always very thoughtful so everybody on this list can
feel how you from your deepest heart care about people on this list as
well as the evolution of Tapestry. Thank you for your invaluable
contribution!
Reading your answer to Andys post one thing came to my mind and I really
would appreciate you answering my question:
Did you realize that Andy asked very concise questions?
He didn't ask should I or should I not use Tapestry but in fact he was
going well beyond the surface. If you'd the mental elasticity to surpass
your innate denial of Tapestry and come up with concrete answers to
concrete questions I would even like your posts more.
Regards,
Michael
Rob Smeets schrieb:
Hi Andy,
Be wise and dig around the Internet to find answers to your questions and
don't turn to this list since they won't offer you a non-biased answers. For
a starter go to theserverside.com where recently a discussion was held on
Tapestry. The link is:
http://www.theserverside.com/news/thread.tss?thread_id=48743
Personally, I won't advise you to go with Tapestry due to it's bad record on
backward compatibility.
Rob
On Sat, Mar 29, 2008 at 11:44 AM, Andy Blower <[EMAIL PROTECTED]>
wrote:
Hi there, I'm evaluating Tapestry (among others) for the web framework
we'll
use at my company for the next 5 years or so. We've used Struts 1 for the
last 5-6 years and it's served us well, even if it was higher maintenance
than was first apparent. I have spent over two days reading about Tapestry
history and general thoughts about past and future which has proved rather
distracting. I'm really not sure whether I should evaluate 4.1 or 5
because
the documentation and intro/tutorial material isn't ready yet for 5 and
I'm
completely new to component oriented frameworks. If I evaluated 4.1, would
that be valid for us still to go on to use 5? It's really hard to get a
handle on the differences of two things you don't yet understand!
I have three (more specific) questions:
1) What methods are known for implementing webpage templates in Tapestry
(e.g. banner, nav, sidebar, content, footer) and is there one considered
'best practice'?
2) How easy is it to add custom AJAX interactions? I'm thinking of
interactions like checking a checkbox to mark a search result, return
success and visually change the appearance.
3) Is it practical to have base classes containing common functionality,
which are extended by very terse page classes along with actual page
templates or am I thinking about this wrong?
With the only T5 examples being so trivial, it's really hard to get a
bigger
picture view at the moment, but I am very intrigued.
--
View this message in context:
http://www.nabble.com/-T5--Tapestry-evaluation-%2B-questions-tp16368331p16368331.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
