> Also, at the moment > javascript files (and other resources) are nicely packages, but there are no > mechanism for javascript namespaces (i'd like to see all component-related > javascript to reside in its own private namespace on the client, so there > are no conflicts).
How should that work though. Currently, Java script support is pretty free form. Which can be explained from the fact that Wicket is not primarily a Javascript library and the design goal we have that you can plug in any javascript library you want. But maybe you can expand a bit on where the lack of name spacing is giving you problems right now? Eelco ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Wicket-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/wicket-user
