Dear all
Tapestry has a short coming when it comes to overriding resources. I recently
worked on a wordpress plugin and found their method of resource import to be
quite useful.
You register a resource with a name
wp_register_script("name", "path");
Then you include it using
wp_enqueue_script("name");
using the same way we can have a service for registering a resource
configuration.add("name", "path");
then import it
@Import("name")
The advantages are :-
1) You can override the configuration and so can override any resource.
2) You can order the scripts
I have not perceived the idea but thought of getting some feedback
regards
Taha
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tapestry.apache.org
For additional commands, e-mail: dev-h...@tapestry.apache.org
