Sounds like an opportunity. Maybe a name/brand search tool dedicated to software projects that gives a report on conflicts that costs a few bucks or is ad-supported.
This is awesome, great work! However, and I don't mean to be rude, lemme just give you a tip about your documentation.
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":
- How about some installation instructions?
- 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.
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.
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.
It's not totally clear from the project page, but I'm pretty sure this particular project is for RubyMotion, and you'll need to be writing your apps with that to benefit. You wouldn't be able to integrate Kiln straight into an existing Objective-C/XCode flow, unlike DCIntrospect. Someone do correct me if I'm wrong on this though.
Thanks! PonyDebugger is solid, though, and much more useful from when you're at a computer. This project is all about getting debugging information from your device.
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!)
[+] [-] spicyj|13 years ago|reply
[+] [-] shawn-butler|13 years ago|reply
[+] [-] colinta|13 years ago|reply
[+] [-] coolsunglasses|13 years ago|reply
[+] [-] mion|13 years ago|reply
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":
- How about some installation instructions?
- 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.
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.
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.
[+] [-] jkubicek|13 years ago|reply
https://github.com/domesticcatsoftware/DCIntrospect
[+] [-] colinta|13 years ago|reply
Different, though, because Kiln is meant to be more generic, and pluggable.
[+] [-] objclxt|13 years ago|reply
[+] [-] spicyj|13 years ago|reply
[1]: https://github.com/square/PonyDebugger
[+] [-] colinta|13 years ago|reply
[+] [-] colinta|13 years ago|reply
https://github.com/colinta/motion-xray
[+] [-] blueprint|13 years ago|reply
[+] [-] unknown|13 years ago|reply
[deleted]
[+] [-] sergiotapia|13 years ago|reply
[+] [-] film42|13 years ago|reply
[+] [-] graue|13 years ago|reply
[+] [-] zachlatta|13 years ago|reply
[+] [-] thomasfl|13 years ago|reply