Just thinking out loud. So much of the code that you're likely to want to edit is stored in tiddlers as plugins or systemConfig code which gets evaluated *after* the core code has loaded. So I don't think you can find it in the FireBug code window. Anyway, I wasn't able to use FireBug on any of the code I was writing. But maybe there's some special technique. I suppose it would be possible to temporarily park code in the Markup section so that it would get evaluated like "real" javascript. Then move it to its containing tiddler once its been debugged.
Mostly I've used FB to help me see what styles TW is applying. In the code itself I use alerts to let me know where the code is executing, and what key variables have been set to. I've found in other environments that debuggers often gets in your way more than they help. Mark On Feb 11, 4:09 am, Mike <[email protected]> wrote: > Looking for a TW experts point of view on how to use Firebug with > TW. . . > > Not sure if anyone has the time or energy to put something together, > but I think it would be a good contribution to the general knowledge > base. This also would be a good resource for people learning how to > troubleshoot and write their own scripts / macros / plugins. > > Slowly making all of us users into mini experts :P > > Any Thoughts? > > Mike -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywiki?hl=en.
