It's not only our own components, we're using GoT5 and wanna extend some components, as they use @Import on the class i can't use placeholder methods. For some of our own components it's worth considering. Generally we've the paradigm to only use @Import except the JS needs to be loaded due to some condition for which we use the JavaScriptSupport. We introduced RequireJS to our project a while ago. It would also solve this problem nicely but as we wanted to cleanly separate the JS files it didn't really make a lot of sense as 99% of our dependencies are jQuery Plugins, which by their nature are globally available once loaded (using jQuery.sub was too bad for performance and would have required to adapt jQuery UI plugins), so we removed RequireJS again. Anyways, wouldn't it be generally better if the @Import obeys the parent child order when loading JS. I couldn't think of any case when the current behavior would be needed.
-- View this message in context: http://tapestry.1045711.n5.nabble.com/Inheritance-and-the-order-of-loaded-JS-tp5714430p5714442.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
