Maybe I'm just disagreeable today ... :-) I like autocomplete, especially as a new user to a framework, showing me what I can/should override. With T5 I have to hit the documentation and guess. Do I need setupRender() or pageAttached() or ... With autocomplete, I at least can see a list of methods to help me get started in that process (and see the JavaDocs for each one to decide which method to try). And, since the source code is available if you inherit functionality, you can easily look at it and see precisely the order things are called. Automagic methods are much more sealed off.
Thanks, mrg On Thu, Nov 19, 2009 at 10:19 AM, Robert Zeigler <[email protected]> wrote: > *I have enjoyed Tapestry 5's "POJO" approach to development, but even there, > I enjoy it more as a committer, for the flexibility it affords in evolving > the framework, than as a user. The only real bonus as a user is that > autocomplete works a lot better since the only methods in the class are the > ones I've defined, rather than a bajillion superclass methods. ;)
