Yeah, I thought the most common default behaviour would wanting debug on - so that's what I've done...If people find this to be counter-intuitive I'll disable it by default.
You can control the log levels, as well as whether it's on at all via the @Shell component "debugEnabled" parameter. http://tapestry.apache.org/tapestry4.1/components/Shell.html On 10/3/06, Martin Strand <[EMAIL PROTECTED]> wrote:
Hi all. How can I make Tapestry (4.1.1) suppress these dojo DEBUG messages? >> DEBUG: Opera is not supported with dojo.undo.browser, so back/forward >> detection will not work. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Jesse Kuhnert Tapestry/Dojo/(and a dash of TestNG), team member/developer Open source based consulting work centered around dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
