Thanks. I can now see the readable dojo.js. However, I guess things didn't work the way I thought. I am using firebug to try to see what goes on in tapestry's js calls (like the form stuff). However, that stuff is loaded by dojo.js asynchronously. Is there some way (using firebug or some other tool) to actually trace through the tapestry javascript?
On 2/8/07, andyhot <[EMAIL PROTECTED]> wrote:
Your @Shell component includes that. http://tapestry.apache.org/tapestry4.1/components/general/shell.html See the dojoSource parameter and use the following asset for it: classpath:/dojo/dojo.js.uncompressed.js Daniel Tabuenca wrote: > Is there a way to make dojo.js more human-readable? I know it's > compressed that way for more efficient network usage, but is there a > way to disable or use the original .js files when we need to debug? > For example, if I want to debug tapestry.form code? > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Andreas Andreou - [EMAIL PROTECTED] - http://andyhot.di.uoa.gr Tapestry / Tacos developer Open Source / J2EE Consulting --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
