Hi, It was just an idea without knowing the inner workings or workflow of the bytecode manipulation. I just saw something which looked like the JavaScript problem on first glance without looking into the mechanics.
Regards, Daniel -----Ursprüngliche Nachricht----- Von: Lance Java [mailto:lance.j...@googlemail.com] Gesendet: Freitag, 17. April 2015 14:02 An: Tapestry users Betreff: Re: Tapestry 5.4 bytecode manipulation On second thought... Why would you want to swap out the the bytecode provider? With clientside javascript it makes sense to choose the provider since you will be directly using jquery or prototype in your own code. Having a single provider reduces the scripts downloaded by the client. But with plastic, the whole idea is that you can do everything in plastic and never need to reference the provider directly (ie ASM). Plastic actually repackages ASM so that another library can include ASM without conflicting. So, as a plastic user you don't need to care about the ASM usage at all. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
