I welcome all discussion on the topic and I will also try to put together some sort of proof-of-concept, if nobody will beat me to it.
A proof of concept would be more than welcome :) I don't see the big picture of how this would fit into Wicket though. What would the concrete goals be? I can imagine delivering a more strongly typed version of the wicket-ajax.js file, which is something we talked about a little bit a while ago but is something we haven't really found time for. But your proposal goes much further than that, and implies that arbitrary parts of Wicket components/ behaviors can be compiled to Javascript? Maybe a good start is to provide a good use case with an example of how it would be used? Eelco
