[Tapestry-developer] Reducing the time of the development cycle.

[Simon Robins]

Happy New Year All!

Now that I feel comfortable with Tapestry, one of the areas of improvement for me would be to reduce the development cycle - code, compile, deploy, test, code...

One of the problem areas is also one of the most powerful - namely the dynamic nature of Tapestry. For example, forgetting to add an accessor which is referenced in a .page or .jwc document isn't spotted until the test cycle, also forgetting to add a component to the same documents isn't spotted until the .html page is referenced. Also an invalid xml document is also a problem area. Obviously a validating XML editor would solve this one - but I tend to hand write xml documents as I haven't come across an XML editor that integrates well with my development environment.

To this end I'm thinking of writing an Ant task altough initially it will probably just be an application. Firstly it would check the validity of the relevant XML document, then it would do it's best to check that the relevant accessors were available in the matching .java file. It would also check that any jwcid attributes within the HTML file had matching components. Lastly it could check that any string-binding's had matching entries in the properties file including the <span key=""/> HTML tag. Plus anything else that comes to mind.

I'm interested to hear any suggestions - would anyone else find it useful, have I missed anything, etc.

Cheers,

Simon



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Tapestry-developer mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/tapestry-developer