Hacker News Reader

Comment by aaronbrethorst | Hacker News Reader

I'm the creator of the site. I'm not sure why this is showing up on here right now, but I'm certainly not complaining!

Please let me know if you have any questions, I'll check back on the thread throughout the day.

You're doing good stuff, although sometimes we have trouble keeping up with the demands from developers; any thoughts on adding "monetization" links? (Guess we could do this in our GitHub readme too...)

By the way, how are you determining license type? What exactly are you scraping on GitHub to determine this? http://www.cocoacontrols.com/platforms/ios/controls/openspri...

Thanks!

Can you be more specific about monetization links? What form would you like to see this take? We do offer the ability to commercially license your controls via our site (e.g. you could dual-license your control and offer commercial support for a fee).

License type: totally 100% manual right now. When the repo is first added to Cocoa Controls, a field is filled out for specifying which licenses the control is made available under. This information may get out of date as time passes (I've seen many instances where a developer changes from GPL -> MIT or Apache 2.0, e.g.).

I actually asked GitHub to make license a first class piece of repository metadata a few weeks ago, but no clue when or if this will ever be added.

> Can you be more specific about monetization links?

I don't mean to confuse this with a license type... we get about a 30 referrals a week from your site (nice traffic for a control!) and just wondering if we can direct them somehow to try the app which actually uses the control. Does Apple have an app store affiliate program? Maybe you can leverage that somehow?

> When the repo is first added to Cocoa Controls, a field is filled out for specifying which licenses the control is made available under

Can this be updated, manually?

Ah, I see what you're saying. Let me think about that a little more, and see if we can figure something out. I'm looking at letting control authors edit their controls without ever having to go through me (I'm planning on setting up an audit log to prevent spam), and I think that—as part of this—I might allow sanitized HTML in the description field for a control. So, that way you'd be able to point people to your website.

> Can this be updated, manually?

By me, yes. By you, not yet. Shoot me an email (it's in my profile), and let me know what you want changed.

Thanks making this available.

My pleasure, glad you like!

edit: hi, fellow Seattleite!

I also have made great use of this great menu of cocoa controls. Thanks for creating it and keeping it up! I do occasionally wonder about the name "controls" for this kind of components. But it seems to be how most people refer to them.

I chose it based on a couple factors:

* I had posted something to my personal blog back in 2005 when I worked for Microsoft that made reference to them as such ('control' is a pretty standard term in MS vernacular). The blog post ended up being ranked #1 on google for the search term "cocoa controls", so I wanted to take advantage of that google juice as much as possible

* The unhyphenated, dot-com domain was available, which was a pretty big deal to me

* I like the alliteration :)

Thanks, and yes, it does roll off one's tongue :)

Reply on news.ycombinator.com