Hi all, currently we don't have a clear solution how to handle a dependency on prototype: - wicket-contrib-scriptaculous includes its own script file - other subprojects have a comment 'you need to include prototype.js by yourself' - if I work on my own custom components, I need to include prototype.js or rely on other components to include the javascript for me.
IMHO we should have a new project wicket-contrib-prototype, which sole purpose is to provide prototype.js as a JavascriptResourceReference. This would give us a clear dependecy in a project's pom. What to you think? Sven -- View this message in context: http://www.nabble.com/wicket-contrib-prototype---tp17270378p17270378.html Sent from the Wicket - Dev mailing list archive at Nabble.com.
