I just thought I'd throw an example of a power tool in to the mix of blogging conversations. I've just finished the first pass at a tool that lets you dig right in to the guts of what a with:Style widget is doing/is up to/wants to do/thinks its doing/thinks it should be doing/etc...

Basically, debugging is great, inspecting is great, but we have a recursive dynamic system, so we need an easy way to get in and have a snoop around and engage the debugger/inspector at more appropriate spots (sort of like what David Buck was explaining).

So, without further a do, and with not too much more dis-explanation, take a look at this screenshot: [Diagnosing with:Style>http://www.softwarewithstyle.com/screenshots/ws1.png]