Added stuff.
Merge branch 'master' of github.com:brione/Brion-Learns-OAuth
oops, forgot to remove the old libraries
I inadvertently put my actual token and secret in here. So I created new tokens (I'm the only user) and those won't work anymore.
first checkin of statuses branch before I fall over
this is ultimately a failed branch, showing the inefficiencies of trying to graft a web-based service on a ContentProvider
Put my key and secret in the public repo again...
turned the Keys class into a subclass of MyKeys, which is not archived. That way I won't keep giving away my token and key and having to reset them
decided that ContentProviders really do not have the flexibility to handle something so organic as interacting with Twitter. It was an interesting experiment. In the course of doing it, I made other improvements to the code. The best is that the OAUTH authentication part of the application is now a separate Activity. I was trying to let the normal flow of things get back to the main activity and that never happened. I ended up having to put a startActivity() call into the OAUTH activity to get the BLOA activity back to the top. Maybe someone could help me with that.
merge of the thought-dead statuses branch with the master branch. This update may be the best yet
was informed via the Signpost group that there is some bug in Android that I have not seen that is affecting some people. The workaround is to build the commons version of the provider instead of the default provider. So I made that change and see no change in behavior on my 1.6 version
moved the libraries to lib directory, as per discussion on developer newsgroup. Also some cosmetic fixes to unused variables and functions, adding @Unused pragmas so the warnings aren't there - No software changes
Improved the instructions to reflect Twitter's awareness of SmartPhone's need for a more flexible Url callback format. Also made a promise to clean up the branches soon, providing two branches, one for the "old way" and one for the right way.
Converted to the ThreadSafeClientConnManager to allow a single HttpClient to drive all the tasks.
Added a comment where the code needs to be changed if the user was able to register their real callback scheme with Twitter, instead of a fake callback like I did, which will make this code not work. You do that by passing null as the second argument (the callback Uri) to the retrieveRequestToken() function call.
Series of steps to upgrade the demo and sharpen skills

Working on HttpURLConnection and did some refactoring

Added basic activity tests for sanity checks.

http://code.google.com/p/oauth-signpost/issues/detail?id=71

Working now except for posting new tweets

Have run into some well-known problem.
Some git and Eclipse related cleanup
Decided to bag HttpUrlConnection

Went back to Apache HttpClient and the
app is working in all respects as well as
ever.