Hi, Personally I like the "documentation solution" better than the "explicit code" version you posted.
I think you could create your own version of what you suggest (without too much hassle) and make that public to your team/others that prefer that style. My guess is that its not necessarily something that warrant framework changes. -- Chris On Wed, Aug 24, 2011 at 8:09 PM, Lenny Primak <[email protected]>wrote: > For example: > core.getServiceFiter().contribute(myTimingFilter) > core.getComponentResources().xxx(); > core.getApplicationDefaults.set(); > core.getJavaScriptSupport().importLibrary(); > core.getFormSupport().xxx(); > > Basically, an interface that makes up 'core' services. > Obviously, not complete but I think the you can get the idea here. > > Basically, a simple, one entry-point into the guts of tapestry via an API > that's well defined > rather than having to hunt for cookbooks/javadocs/example code, etc. > > >
