the problem is dealing with component merging. two components have named a method or variable the same thing. if we actually parse the JS, we can add a "namespacing" prefix to these names and ensure that no collisions will ever occur. what's more, if we do this, we can also keep the JS code simple and readable (which is often a problem with JS as it is).
Gili wrote:
On Sat, 12 Feb 2005 15:07:21 -0800, Jonathan Locke wrote:
btw, did my comments below make sense (about automatically dealing with CSS and JavaScript)? we'd need to do some work in the parser, but it seems like the right thing (unless i'm missing something...)
I didn't understand the bit about why we need a special parser for scoping or something . . . Why can't we just dump the JS into place like we currently dump the HTML into place without validating it or messing around with its scope?
Gili
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
