At this point it seems like you could have a Tapestry5-jquery.jar and a Tapestry5-prototype.jar and Javascript support becomes like Hibernate vs JPA. You just include none/one/both depending on your needs. I would think something that could happen in 5.4 by just moving the prototype code into it's own jar.
-- View this message in context: http://tapestry.1045711.n5.nabble.com/prototypejs-is-dead-time-to-bring-t5-jquery-in-tp5073709p5075694.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
