> Again folks, write tests - don't think your compiler is helping you > much. Use reflection anywhere you like, just test your use of it.
Ok, reflection is as testable as anything else - it does however, open a Pandoras Box for an unskilled programmer to make a mess. What I like about Java over C++ was removing a lot of the pitfalls that required experience and discipline to avoid. > You really ought to give RoR a try then. It lives up to the hype of > productivity gains. Thank's, I'll take a look. > Definitely possible. I looked at using the core of Spindle to do > this at point, but it is very connected to the Eclipse API, making it > prohibitive to create an Ant task that Tapestry could ship for such > things. A good idea, and a pity. This is the challenge vs .NET isn't it, building productive tools. If you ever used MS Access, you may remember how smart it was at prompting everything. I don't mind if the whole build environment is Eclipse based, or whatever, so long as it offers an integrated set of useful tools to make up a comprehensive set. All these frameworks to be stuck together is what makes Java flexible, but too geeky. After Tapestry 4 is final, the next project needs to be to create a comprehensive developers toolset IMO. It's the wizards and autopromts that get the beginners roped in. Spindle would seem to make a logical place to start. John --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
