I hate typing I am not Sam G :-)
Gosh, my first day back on the list in any significant way in nearly two months, and I stumble into a reference to me. I must be famous ;-) I don't have any real comment to add to the initial question since I have no familiarity with Tap5 development, but I would like to point out that when developing a framework, assuming that a mechanism is sufficient purely because an external IDE can simplify the task is not going to lead to good design in the long run. IDEs evolve and development environment requirements vary from project to project. the only IDE I use is vi, and while I do type fast, I have no interest in typing any more than is necessary. Relying on completion in order to justify very long variable names strikes me as a bad strategy. Heck, printing the source code is argument enough against allowing super long variable and method names wherever possible, never mind that I work with a 79 character line in all my code purely for on-screen readability and xterm compatibility. My biggest gripe with Tapestry in general (I'm in Tap 4.0 except for some experiments in 4.1) is the lack of compile time error checking for much of the tapestry 'code' you wind up writing. As a project grows, the init time for the application can become significant (as can the compile time) and build/deploy/test cycle can become unbearably slow when it turns out you've got some stupid typo that wasn't caught because a file wasn't compiled (and the PermGen thing effectively prevents working with caching disabled, since things get unpredictable). So while I don't understand the nuance of the question that started this thread, if one option results in better compile time error checking, I'm all for that one. --sam --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
