Quoting Igor Lobanov [EMAIL PROTECTED]:
Anyway, Jonathan's suggestion about ease of CSS use is the most appealing to
me, because nowadays CSS finally became the most powerful facility for
determining style and position of elements on a page.
I've got to say that this is not so important to
Dear community,
Could you tell me what are benefits of using pure HTML approach to
creating templates for your pages? As I understand it is one of primary
selling points of Tapestry framework. However I failed to find any
justification for this approach other that you can give it to your HTML
on this issue for me.
First of all, why wouldn't you want to use pure HTML templates?
What are the benefits of using something else or even something new?
Even though I (almost) never look at the templates using a special html
editor or browser, there are two advantages:
1) If your editor knows about
Hi Igor.
In addition to the $remove$ suggestion from Jonathan, I'd like to point
out that conversion from your designer's html to a Tapestry template is
much simplified when compared to JSP etc. In many cases, but not all,
the result (including components) are still editable by the designer.
Christian Haselbach wrote:
First of all, why wouldn't you want to use pure HTML templates?
What are the benefits of using something else or even something new?
Even though I (almost) never look at the templates using a special html
editor or browser, there are two advantages:
1) If your
