> > In any case, the users should not required to be aware of the javascript > libraries it uses. > We only have a limited set of components as is, no use fragmenting this.
End-users shouldn't, but we can expect a little more from developer, right? :o) I think most people working with Tapestry, care about quality and performance. So injecting two different JavaScript frameworks into the HTML is avoided if possible. This was the main reason I started looking at this issue in the first place, since I don't like forcing over 160KB of JavaScript onto the end-users while my own components only require a 56KB JavaScript framework. Even the fact that the files are cached on the client doesn't really help, since you are still letting the other framework use up a lot of resources on the client by including it. The browser has to parse it all, create models in memory and existing Elements are extended. regards, Onno
