Dear Wiki user, You have subscribed to a wiki page or wiki category on "Tapestry Wiki" for change notification.
The following page has been changed by NickWestgate: http://wiki.apache.org/tapestry/Tapestry5Roadmap ------------------------------------------------------------------------------ I've been struggling with the following choice: * Keep backwards compatibility and evolve the code base (give or take) + * Sacrifice backwards compatibility, but create the simpler, less ambiguous (easier to learn) framework people want - * Sacrifice backwards compatibility, but create the simpler, less - ambiguous (easier to learn) framework people want I'm prototyping some stuff right now that I'd have to call Tapestry 5. - I don't think there's a way to remove inheritance in the Tapestry 4 + I don't think there's a way to remove inheritance in the Tapestry 4 code base without distorting many interfaces and breaking backwards compatibility. @@ -33, +32 @@ + I'm starting to focus beyond that, on Tapestry 5. I'll be drawing out the code from Tapestry 4 and providing new code. My vision is: - I'm starting to focus beyond that, on Tapestry 5. I'll be drawing - out the code from Tapestry 4 and providing new code. My vision is: * Annotations based. JDK 1.5. * No XML for pages and components. Just HTML and Annotations. * Concrete, not abstract, page and component classes * No inheritance imposition - * Transforming class loader driven by annotations (i.e., @Persist on + * Transforming class loader driven by annotations (i.e., [EMAIL PROTECTED] on the field, not the method) - the field, not the method) - * Change detection; automatic invalidate and reload of changed objects + * Change detection; automatic invalidate and reload of changed objects (including Java classes) - (including Java classes) - * "Modern" templates: Templates as wellformed XML, using a namespace + * "Modern" templates: Templates as wellformed XML, using a namespace for Tapestry attributes and elements - for Tapestry attributes and elements * A "preview" mode for pages * Partial rendering of pages (for Ajax operations) * Improved management of page state (including dynamic state during the render) @@ -61, +56 @@ The Command will be executed during the render. + The interface for Command will probably be {{{void execute(IComponent component);}}} the control layer will store and - The interface for Command will probably be - - void execute(IComponent component); the control layer will store and serialize a ComponentAddress; during the subsequent request, it will use the ComponentAddress to reaquire the component and pass it to the Command. The Command impl will downcast and invoke. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
