Kiln is already a well-known software development tool from Fog Creek: <a href="http://www.fogcreek.com/kiln/" rel="nofollow">http://www.fogcreek.com/kiln/</a>. I wonder if the author knows.
This is awesome, great work! However, and I don't mean to be rude, lemme just give you a tip about your documentation.<p>I'm not a "documentation expert" or anything, but IMHO I'd say there is too much information on your "landing page" and not a clear "call to action":<p>- How about some installation instructions?<p>- Basic usage? (addressing the main features, those which most users will probably use most of the time)
If I were you I'd put the details about plugins somewhere in the Wiki.<p>I don't have a lot of spare time to check out your thing, so the project becomes increasingly unattractive as I have to waste more and more time to figure out how to use it / how to get it up and running for a basic test.<p>Again, IMHO, I believe this applies to most hackers, and to open source documentation in general. Very often I see great hackers who can code 1000x better than I do, but fail to write 'attractive' documentation for their projects.
As cool as that looks, I've been using DCIntrospect for a year or two, and it's nearly everything I need in a live UI inspection tool.<p><a href="https://github.com/domesticcatsoftware/DCIntrospect" rel="nofollow">https://github.com/domesticcatsoftware/DCIntrospect</a>
This looks like it gives a lot of what I hoped PonyDebugger [1] would be when I first heard about it. Cool!<p>[1]: <a href="https://github.com/square/PonyDebugger" rel="nofollow">https://github.com/square/PonyDebugger</a>
name is resolved, so all the trolls and snipes that are hung up on the NAME instead of the PRODUCT, please continue your trolling and sniping, but on a new topic (like this comment! it's perfect!)<p><a href="https://github.com/colinta/motion-xray" rel="nofollow">https://github.com/colinta/motion-xray</a>