I would suggest splitting the documentation.
There should be the reference documentation by the creators/commiters of the
project, whis is organized like a book covering all the different aspects of
tapestry 5 in a reference manner eg like spring or hibernate docs. These are
tied to the release ve
alex,
sorry you are right. I was blown away on points 2 & 4.
2009/5/1 kranga
> For Tap 3, we had a very elaborate form with loop implementation and we
> added Ajax-validation such that you only write validation code once in Java
> and for javascript validation, an ajax call is made to run the s
Should turn that into a pros/cons table in the maven docs. That's a
great list.
Christian.
On 30-Apr-09, at 22:57 , Howard Lewis Ship wrote:
I thought I'd weigh in here on the positives and negatives of
Tapestry.
Don't expect me to go gushing on about community and the generosity of
the
I thought I'd weigh in here on the positives and negatives of Tapestry.
Don't expect me to go gushing on about community and the generosity of
the committers and all that; I stay pretty well focused on the
technology.
Beautiful Things In Tapestry
* Live Class Reloading
Can't live without it. En
For Tap 3, we had a very elaborate form with loop implementation and we
added Ajax-validation such that you only write validation code once in Java
and for javascript validation, an ajax call is made to run the same
validation code and bring back the results. The error handling could
correctly
Thanks a lot for all the input folks. Putting aside my doubt for future
compatiblity for now, I think i might give Tapestry5 a try cause i found it
to be pretty straight forward especially when i come from J2EE, and Jboss
seam background.
And to say that i remember reading somewhere how Tapestry
Agree with Alex on the last comment about proving that issues don't exist!
I have one example of a trivial thing that I have found difficult to
implement in all Tapestry versions I have used(3, 4, 5):
- A form with a loop in it.
This is extremely common in the pages I make, and my mind always st
I will echo Kranga's #1 and #2 and add a couple. I'm all for
convention over configuration, but when you have to dig out the
convention out of source code, mailing list, or somewhere else, I'd
wish I had a well defined interface that I could just implement. The
not-so-pojo aspect becomes too appare
> I am still deciding whether to choose Tapestry5 for my upcoming
> project. I
> was reading a lot how each version of Tapestry isn't backward
> compatible
> with older version and how migrating the code to new Tapestry is a
> nightmare. I like Tapestry declaractive model but my priority in
> choos
> I don't think Tapestry's wiki, http://wiki.apache.org/tapestry, is up
> to the task.
Confluence is available with apache as well. There is already a space
available at http://cwiki.apache.org/TAPESTRY/ ... maybe its just a matter of
adding content to it?
Anyway.. on Tapestry360 someone would
Some interesting points here.
2009/4/30 kranga
> 1) Documentation: It is one thing to remove dependencies on framework
> interfaces but quite another to leave the developer hanging with no
> documentation. Programming by convention is programming in the dark if the
> convention is not known.
Y
>What can I do to get the old behaviour back?
Since you are using 5.0.18 you need to do nothing, this change is for 5.1.
This is the correct behavior, as scripts should almost always be placed at the
top, read this:
http://www.quirksmode.org/js/placejs.html (especially the last paragraph)
Tapes
Am 30.04.2009 16:08, schrieb Peter Stavrinides:
see this page:
http://tapestry.formos.com/nightly/tapestry5/apidocs/org/apache/tapestry5/SymbolConstants.html#SCRIPTS_AT_TOP
SCRIPTS_AT_TOP
Deprecated. since 5.1.0.1; scripts are now always at the top (see TAP5-544)
Oh no.
What can I do to g
see this page:
http://tapestry.formos.com/nightly/tapestry5/apidocs/org/apache/tapestry5/SymbolConstants.html#SCRIPTS_AT_TOP
SCRIPTS_AT_TOP
Deprecated. since 5.1.0.1; scripts are now always at the top (see TAP5-544)
Peter
- Original Message -
From: "Kai Weber"
To: "Tapestry users"
Sen
Am 30.04.2009 15:26, schrieb Peter Stavrinides:
What version of Tapestry? Correct me if I am wrong but from 5.1.0.4 it is no
longer required.
Could you tell me more, what "it is no longer required" means? Scripts
are always placed on bottom of the page?
Regards, Kai
-
Thanks for the solutions. both ways worked.
to get the unique id from server side, I can do:
Client:
var _uniqId="${uniqId}";
Server:
@Component
private TextField text1;
public String getUniqId()
1) Documentation: It is one thing to remove dependencies on framework
interfaces but quite another to leave the developer hanging with no
documentation. Programming by convention is programming in the dark if the
convention is not known.
2) Although Tapestry claims to be POJO, you still have to
Sorry I see you have mentioned 5.0.18
- Original Message -
From: "Kai Weber"
To: users@tapestry.apache.org
Sent: Thursday, 30 April, 2009 13:16:10 GMT +02:00 Athens, Beirut, Bucharest,
Istanbul
Subject: SymbolConstant.SCRIPTS_AT_TOP=false does not work anymore
Hi,
I use 5.0.18 and I ca
What version of Tapestry? Correct me if I am wrong but from 5.1.0.4 it is no
longer required.
- Original Message -
From: "Kai Weber"
To: users@tapestry.apache.org
Sent: Thursday, 30 April, 2009 13:16:10 GMT +02:00 Athens, Beirut, Bucharest,
Istanbul
Subject: SymbolConstant.SCRIPTS_AT_T
2009/4/29 Pedro Januário :
> Anyone would like to have this improvement?
I wouldn't :), but you can create a new binding prefix that pulls the
regex from a database.
Your template would look like:
--
Thiago
-
To unsubscribe,
That agrees well with my T3-4-5 experience over the last five years. Once I
committed to T5, it wasn't as bad as I'd feared from all the mailing-list
discussion. (Note to self: The list is mainly about problems.) It felt
familiar, the "concepts translated well".
Getting accustomed to Maven and
Hi,
I use 5.0.18 and I cannot get SymbolConstant.SCRIPTS_AT_TOP=false to work.
What I found in the sources and by running my app with a debugger:
* TapestryModule sets SymbolConstant.SCRIPTS_AT_TOP to "false" in
contributeFactoryDefaults()
* in TapestryModule.contributeMarkupRenderer()the Sy
I totally agree with Hugo's ideia.
The wiki sounds good and should be a easy to make documentation about common
problems.
2009/4/30 Hugo Palma
> I agree a book would be great, what happened to the tapestry5-book
> project http://code.google.com/p/tapestry5-book/ ?
>
> Still, i think a lot better
As someone that usually tries to "sell" the idea of using Tapestry to
others the main resistance points have been:
- People love drag&drop and autocompletion :o) . It's a major letdown
when i tell people they won't have any IDE integration with this
framework.
- The backwards compatibility thingy
I agree a book would be great, what happened to the tapestry5-book
project http://code.google.com/p/tapestry5-book/ ?
Still, i think a lot better could be done with the online documentation.
I believe the structure of the online documentation should be very
similar to a book, it should start with
I think you hit the nail on the head Carl. The documentation is okay generally
(some bits poor, some very good) but there is not enough to tie it all together
and guide new developers so they know what they can do with T5. I'm not
convinced that the main documentation should attempt this on its
> was reading a lot how each version of Tapestry isn't backward compatible
> with older version and how migrating the code to new Tapestry is a
> nightmare.
I also did the migration... developer time = money, so this is a very valid
concern, but Tapestry 5 is worth it! You will gain in productivit
I had this issue when my tapestry dependencies got mixed.
The project uses T 5.1.04 and an utility module declared T 5.0.7.
in runtime this created the issue, I guess because names changed for the
validators...
I aligned the versions, and the error is gone.
Davor Hrg
On Thu, Apr 23, 2009 at
sodium schrieb:
Hi,
I am still deciding whether to choose Tapestry5 for my upcoming project. I
was reading a lot how each version of Tapestry isn't backward compatible
with older version and how migrating the code to new Tapestry is a
nightmare. I like Tapestry declaractive model but my priority
I came across this same error "Construction of service ... has failed
due to recursion" several times in my T5 developer life. It was always
when upgrading from one version to another, and it was always a
classpath problem. I had to clean everything (quite blindly), restart
Eclipse, clean some
30 matches
Mail list logo
