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 ErikVullings: http://wiki.apache.org/tapestry/Tapestry4 ------------------------------------------------------------------------------ + ## page was renamed from Tapestry31 #pragma section-numbers off - = Tapestry 3.1 = + = Tapestry 4.0 = - Right now (March 11 2004), work on Tapestry 3.0 is ''finally'' coming to a close, and much thought has already gone into what comes next. + Work on Tapestry 3.0 has ''finally'' come to a close, and the focus is now on what comes next. - Hopefully, Tapestry 3.1 will not drag on for as long as Tapestry 3.0 (a year and a half!). + Hopefully, Tapestry 4.0 will not drag on for as long as Tapestry 3.0 (a year and a half!). More information is available on the Tapestry31Status page. + + ''Woops! Guess it did! -- Howard'' + + Tapestry is now using HiveMind's build system ... heres notes on BuildingTapestry31. + A number of ideas are floating around, rough areas in 3.0 (or even earlier) that need to be addressed. - - Part of the solution to all of these issues will involve HiveMind. In that HiveMind itself is nearly ready for prime time, to some degree Tapestry 3.1 is already under development (in fact, there's a Tapestry 3.1 branch that was created months ago). = Reworking Component Parameters = @@ -25, +29 @@ I would think that {{{render}}} is the best default for a component parameter cache. + '''Update''': Parameters have been ''fixed'' and are better and more efficient than ever. Parameter direction is gone. There isn't a choice in terms of caching, its the equivalent of {{{render}}} above, and I think that is more than sufficient. + = Modularized Applications = Tapestry 3.0 expects all Tapestry pages and components in the application to be within a single directory. This causes some scalability problems ... when your application has dozens or hundreds of pages, its not good to have them all in a single directory. @@ -35, +41 @@ On top of this is the desire to maintain WYSIWYG preview ... this will likely entail having the Shell component render a <base> tag. + '''Update''': This has started, and page names can now have one or more folder names, i.e., {{{admin/threads/ThreadAdmin}}}. This would locate a page specification as {{{/WEB-INF/admin/threads/ThreadAdmin.page}}} and an HTML template in the same folder, or as {{{/admin/threads/ThreadAdmin.html}}}. The Shell component now renders a <base> tag. + = Improved Testing Story = Testing Tapestry pages and components is too hard. Because the classes are often abstract, it isn't easy to instantiate them for testing purposes. Tapestry has a fairly good test suite that needs to be ''productized'': documented, improved, stabilized. + '''Update''': The Creator can instantiate abstract components, a HiveMind 1.1-alpha supports mocked classes via the EasyMock class extension. So unit testing pages and components, and even the integration of different pages and components is feasible (and widely used inside Tapestry's own tests). However, providing a good, efficient, ''integration'' test framework would still be a huge boon ... the start of one is there, but I've switched gears to use EasyMock instead. + = HiveMind Integration = - The DTD will be extended to add elements related to HiveMind, such as <service-binding>. HiveMind-like things, including <extension> and <service> will be deprecated. + The DTD will be extended to make it easy to access HiveMind objects, using <inject> to inject services, configuration or whatever into pages and components as read-only properties. The <extension> and <service> elements will be deprecated. + '''Update''': Yep, that's in there, and works great. + - = Offline Content Generation (3.2?) = + = Offline Content Generation (4.1?) = This has come up ... the idea of using Tapestry to generate ''static'' web pages. This is a technique used by many high-volume web sites ... much of the content is neither fully dynamic nor personalized. It changes at fixed intervals and might as well be a static web page that is auto-magically updated. + An alternative is to use your preferred http server's error handling mechanism to ask your app server to generate the static page (when possible): if the page is here, ok the http server serves it, otherwise it redirects the request to your app server (which in turn saves the final response). If you want to update, delete the static files. + ... + = Portlet Support = + Supporting porlets in Tapestry 4.0 is gaining an ever higher priority. + --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
