Initial commit
added default eclipse android project (Hello World). We might want to change some settings about what versions our app will support, or maybe even start a new project from scratch, but at least here's something.
added ideas
added quick, basic debug logging facility
added some rough mockups
apparently not everything was visible in the mockups. fixed
added a bit to Logging functionality, also added some more empty Activities. Made a very basic model for the LoginActivity
reorganized things into packages, tweaked UI a little, and added a skeleton Account class to handle login and such. I should make my commits more focused...
added a bit to friend activity
added some quick and dirty skeletons of Friend and Movie classes
Trying my best to get a mock server up and running. It's not going to well so far. Also, I know the python implements a socketserver, and the java is trying an httpclient, I'm in the middle of some things, I know it won't work right now. I don't think we really need an httpclient, maybe just switching to a socketclient in the app will make everything easier. Then again what do I know. JON HELP
on second thought... I actually got the http client mostly working. Obviously the socketserver isn't entirely functional with it, but it receives http data just fine. Maybe it's easier to convert the python to a httpserver. Note though, GlonnyServerProxy really shouldn't itself be an AsyncTask, I need a private inner class to be an AsyncTask, since we need a new instance of it for every async request.
client/server http communication actually seems to be working... now to make it do something sort of useful
fixed "AsyncTask" thing, so we can have more than one in a single run of the app. Should really make it more generic though
Nice. Glonny is communicating with the mock server via JSON-over-HTTP, and managing to call a remote function and get a return value, determining whether login is accepted or not.
so... I set out to unhardcode strings, especially ones shared between the client and server (ie, method names, JSON parameters, etc). Went really well at first, the android API has some nice localization stuff that made it easy to abstract out the strings, and it's stored in xml, so the python side can just parse the file and always have the same values as the app. Sounds pretty good in theory... but in the end I think I have just as many hardcoded strings (the lookup keys), plus another layer of abstraction. Didn't really work out how I imagined. Still could be useful I suppose, in case for some reason we need to change some of these values we only have to do it in one spot instead of two... but I think that's highly unlikely... about as unlikely as it is that we'll have to change the lookup keys now (which obviously still takes 2 spots to change). Anyway.... I'm leaving this for now becuase screw it, we can always revert later if it proves to be bothersome and doesn't yield any benefits.
added buttons onto mainactivity to go to movielist and friendlist, just so we can start using/modeling/debugging those
added (empty) settings activity, and tied the other activities' settings menu items to it
removed a bunch of trailing whitespace in vim, because I hate trailing whitespace. Stupid eclipse
Added GlonnyActivity as a subclass for all our activities. Not much in it yet, but could be good place for commmon code