Hi list,
I found that's quite troublesome using dreamweaver to edito tml pages,
any better solution?
Thanks
John
-
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail:
Using invisible instrumentation its very easy. For example replace:
t:pagelink page=myPageFoo/t:pagelink
by
a t:type=pagelink page=myPageFoo/a
On Fri, Feb 11, 2011 at 10:08 AM, onj888-tapes...@yahoo.com.hk wrote:
Hi list,
I found that's quite troublesome using dreamweaver to edito tml
But what is the reason why invisible instrumentation is not the only option.
I have always thought that for a presentation framework having clean
html files as tamplates is a major advantage.
Il 11/02/2011 10.25, Igor Drobiazko ha scritto:
Using invisible instrumentation its very easy. For
On Fri, 11 Feb 2011 07:35:32 -0200, Ivano Luberti lube...@archicoop.it
wrote:
But what is the reason why invisible instrumentation is not the only
option.
I don't know.
I have always thought that for a presentation framework having clean
html files as tamplates is a major advantage.
Il 11/02/2011 11.15, Thiago H. de Paula Figueiredo ha scritto:
I have always thought that for a presentation framework having clean
html files as tamplates is a major advantage.
Tapestry does have the advantage of clean HTML files as templates.
Just use invisible instrumentation always.
On Fri, Feb 11, 2011 at 3:35 AM, Ivano Luberti lube...@archicoop.it wrote:
But what is the reason why invisible instrumentation is not the only option.
I have always thought that for a presentation framework having clean
html files as tamplates is a major advantage.
Because if you aren't
Maybe, but as you try to write java code as clean as possible, I cannot
see why you shouldn't do the same thing with your html code.
Even because usually you want to show your html static pages to the
customer before starting to implement something else.
Il 11/02/2011 14.51, Mark ha scritto:
