Jesse Kuhnert <jkuhnert <at> gmail.com> writes: > Hmm....I can't really have a "very" strong opinion here as I'm not as > familiar with the T5 codebase as I'd like - but if nothing new has > been realized / seen in your research / branch then I would find this > idea extremely concerning...Esp as T5 is still barely starting to > waddle around on two legs, it'd be a shame to start making it smoke > and drink when it has so much more potential in life. ;)
I don't know if you would consider the following new, they are the advantages that I found: 1) compile time checking. 2) IDE auto-completion. 3) IDE refactoring. 4) IDE code generation for embedded components (a simple code template will do). 5) fits in well with generics (TextField<Date> will only accept a Date). 6) javadoc is the component doc. People can just press a hot key in IDE to go straight there (eg, Shift-F2 in Eclipse). 7) no need to remember parameters names or lookup any doc as the IDE will tell you the available parameters. 8) no need for special ordering of parameters when deciding their defaults. 9) related objects such as validators are just POJO's. 10) easy to learn; no need to learn binding prefixes as they only need to work with POJO's. The whole purpose of having a branch is to experiment with it, not just by me, but by users. Why not let users try it and see if they like it? Quite some users have expressed their strong desire for IDE support. This branch is the IDE support. We can and should state that this branch is just an experiment and is not guaranteed to exist in the stable version. Then, how can having an experiment hurt? -- Author of a book for learning Tapestry (http://www.agileskills2.org/EWDT) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
