Hi,
As I said before here, I'm working on a port of tapestry.js to jQuery.
Instead of just having to recode tapestry.js, I'm too often obliged to fork
core components for a little and annoying thing : the
@IncludeJavaScriptLibrary and @IncludeStylesheet annotations, just in order
to be able to change path of theses assets.
As it is made for Autocomplete mixins, why not using this kind of coding
style for JS and CSS inclusion:
/**
* @param config
* parameters object
*/
protected void configure(JSONObject config)
{
}
In the current case, it may look like:
protected void include()
{
renderSupport.addScript("script.js");
renderSupport.addStylesheetLink("style.css", "print");
}
It would provide easier extensibility for components, mixins and pages.
Anyway, this is just my feedback about this technical aspect of Tapestry 5.
:)
Regards,
Robin
