Hot answers tagged libraries
Remember, you should only publicize your app if it can actually be used! I'm working on an idea for an app. In true "customer development" fashion, I'd like to publish the idea, with a screenshot of what it will look like, to see what kind of reaction it gets and what features people want it to have. It's not difficult to implement, but I'd rather not ...
A library should take an app key, not have an app key. Don't register it. Also, make absolutely sure your wrapper demands an app key at initialization. You don't want a user locked into the No Key request limit erroneously. If libraries had keys an application abusively using your library (through no fault of yours) could get every application that uses ...
Historical Note StackList is no longer available - the features that made it an attractive supplement to listing your app here have found their way into Stack Apps itself. This answer remains for historical purposes. Don't forget to also publish your app on stacklist.quickmediasolutions.com (404 Not Found) The site is shaping into a nice user-...
This would be a good idea, as it would immediately clue developers into the resources that are here specifically to make the API easier to use.
No need, the "apps" tag pulls anything tagged "app" or "library" already. Alternately, just click library and browse all the libraries. (sorry, this change has been in for a while, we just hadn't deployed.)
StackOverflow.Net uses the technique you described of having the API calls return the object or list of objects you are interested in. For example, GetQuestions() returns a list of Question objects. So if you like to read C# check it out.
Honestly, I don't think it is a big enough deal to warrant all of this attention. I don't see why posting code samples should be Community Wiki, but if a Moderator believes that they should be, then that's fine. It was getting a bit annoying to see C# code samples posted all over the active question's page. I think a few is ok, but in my opinion, it was ...
As Jeff mentioned in the comment of my other answer, this information would be best put elsewhere... so... I have set up a MediaWiki installation for this here: http://stackoverflow.quickmediasolutions.com/wiki/ Update: The stackoverflow.quickmediasolutions.com subdomain appears to have been dead for a while. Here's what's left of the wiki at the Internet ...
This will eventually turn into the entry for my app. It didn't! See my other answer. Support: the page at http://stackoverflow.quickmediasolutions.com/stackad/ is having some trouble pulling answers. // an url built with soapi-explore... // http://api.meta.stackoverflow.com/0.8/questions/53346/answers?body=true&min=6&order=asc&sort=votes // ...
I was going to write this as a comment, but it got too long: I've got about 50% of the way through my JS app using your wrapper, but I'm heading back to work after some extended leave and there's no way I'm going to get it finished. That said, what I used worked great, only one suggestion, it would be great if the requests could be synchronous (rather than ...
Having earned some rep. from the "dev-tip" questions myself, I can honestly say that I probably would not have put in the effort knowing I would never get rep. from it. I think the CW-requirement needs to be relaxed :)
Only top voted, non community-wiki answers of a minimum length are eligible