Hi Amit,
1) For exmple:
<t:parameter name="deleteCell">
<t:if test="bean.condition">
<a t:type="actionlink"..../>
<t:parameter name="else">
<span>whatever</span>
</t:parameter>
</t:if>
</t:parameter>
2) You can use whatever you want as long as you manage to pass the data to
tapestry and back. Look at the wiki
http://wiki.apache.org/tapestry/Tapestry5HowTos for examples about GWT for
example.
3) Tapestry is component oriented, while the others are mvc frameworks.
Pages in Tapestry are effectively not controllers in the MVC sense, but more
aggregators of components and services which in turn can consist of
components and services, which in turn... In Tapestry you build your own
building blocks or use predefined ones to assemble the functionality that
you want. If you do more complex things this differs quite much from the MVC
approach where controllers tend to get bloated (at least they do for me ;)
). Furthermore you have a completely different programming model thanks to
the annotation driven approach and the Tapestry IOC which makes many things
just so much simpler. RoR I cannot say much about, since I don't program in
Ruby. Grails is certanly a nice choice for applications which have only one
database, but it is somewhat more difficult to debug thanks to the dynamic
nature of Groovy (no static typechecking can lead to interesting bugs very
easily). I guess the same goes for Ruby. What is better for you in certain
circumstances or for a specific jobs is nothing wich anyone here could
answer, though.
2009/3/20 Amit Nithian <anith...@gmail.com>
> Hi all,
> My apologies if my questions are ignorant or have been answered already, if
> so, a link to the answer is more than satisfactory for the question.
> Basically, I am interested in learning one of the many web frameworks and
> have narrowed to looking at Java frameworks since I don't have enough
> experience in PHP, Python or more recently Ruby (and Rails) and I am a Java
> developer. In looking online, I came across Tapestry and am using that now
> to write a simple web application for work and ultimately, I am interested
> in learning how to use Tapestry to write larger scale web applications.
>
> I understand the MVC pattern to some end as it applies to Ruby on Rails
> (and
> subsequently Grails). My questions are as follows;
> 1) With Tapestry, I understand the Controller is effectively the Page and
> Components with the View being the template files. I haven't seen any
> examples of complex "scripting" in the templates where you can build
> complex
> views. Is that by design or am I missing something? For example, I am using
> the GridLayout component and I added an extra "delete" column; however, I
> would like to only enable the "Delete" link inside this phony column only
> if
> some condition on the current bean is true. How would I go about that?
> 2) I saw some discussion regarding JQuery vs Prototype etc which is fine (
> I
> don't know either one well) but how does one go about writing complex UIs
> using Tapestry and template files? Do you use YUI components inside a
> <t:form>? How do people build nice looking, complex front ends with
> Tapestry
> backends?
> 3) What are the differences conceptually between Tapestry and Grails or
> Ruby
> on Rails, Spring MVC etc and why is Tapestry better?
>
> Thanks for reading and I am excited about using Tapestry!
> - Amit
>
