Timeline for Java wrapper for the Stack Exchange API 2.0?
Current License: CC BY-SA 3.0
13 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Feb 11, 2013 at 20:45 | comment | added | Eugen | Hi - any update on bringing the StackWrap4J project up to date and using the 2.0 (now 2.1) version of the API? Would it make sense to perhaps move the project itself onto github so that contributions are easier to do (via pull requests)? | |
Nov 2, 2012 at 11:02 | comment | added | Manny Fleurmond | have we had any news? | |
Sep 9, 2012 at 4:48 | comment | added | Manny Fleurmond | If something comes of this I'll be happy to participate. I've been researching creating a Holo-based Stack Exchange Android app and a Java wrapper is just what I need. Still green on my Java but I'll have a look at the StackWrap4J code and will lend my help in any way I can. | |
Aug 31, 2012 at 21:38 | comment | added | jjnguy | I am! I'll see what I can throw together over the weekend. | |
Aug 31, 2012 at 21:28 | comment | added | Alex Lockwood | @jjnguy I can help out if you need me... you're one of the people who actually wrote StackWrap4J, correct? | |
Aug 31, 2012 at 15:24 | comment | added | jjnguy | I think it's safe to develop against the 2.0 release. Otherwise you end up waiting for a release that isn't even scheduled yet. | |
Aug 31, 2012 at 15:17 | comment | added | Alex Lockwood | @jjnguy Not 100% sure (and last time I checked they hadn't even ball-parked it). API 2.0 has out of beta for about 6 months now so I'd guess sooner rather than later (?). From what I can tell 3.0 is going to be mostly an extension of 2.0 (i.e. the addition of write-only API calls). That said, there are some parts of the documentation that say things like "this could be changed at any time" etc. and I'm not always certain which parts should be trusted. | |
Aug 31, 2012 at 15:10 | comment | added | jjnguy | How soon is 3.0 supposed to be released? | |
Aug 31, 2012 at 15:07 | comment | added | Alex Lockwood | @jjnguy In all honesty, I didn't really end up modifying/extending all that much (I was mostly concerned with badges, inbox items, notifications, etc.). I do feel like I have a pretty good understanding of how StackWrap4J works though (I looked through probably 80% of the source code), so I'd be able to contribute I think. I would hate for v3.0 to come out though and potentially ruin any work we put into v2.0... what would be the best way to write the library given that it will eventually need to be brought up to 3.0 standards? | |
Aug 31, 2012 at 14:05 | comment | added | jjnguy | From what I know about the changes, it will probably be best to only use some of the HTTP stuff from StackWrap4J and probably start over on the rest. | |
Aug 31, 2012 at 14:01 | comment | added | jjnguy | Hey, I'd be interested in getting StackWrap4J up to 2.0 standards. Would you be able to contribute your changes to the Source Forge project? | |
Jul 31, 2012 at 16:19 | vote | accept | Alex Lockwood | ||
Jul 31, 2012 at 16:19 | history | answered | Alex Lockwood | CC BY-SA 3.0 |