added fix for empty question creation
Merge pull request #174 from CMPUT301F14T14/Sort

Sort Added And add upvotes to the question list, Welcome screen added textview
Fixed list sorting backwards
added camera ability, only save locally at this time. Having problems loading to thumbnail Do not merge
Restrict searches to questions and answers only.
Use default serializers. These work fine, and will handle new data better. Also stores parent usefully.

Sorry I broke data again.
Fixed multiple upvotes question
Fixed multiple upvote answers
Merge pull request #176 from stephenjust/search-restrict

Restrict searches to questions and answers only.
Merge pull request #177 from stephenjust/default-serializers

Use default serializers. These work fine, and will handle new data bette...
Merge pull request #178 from Kopo101/bugfixes

Bugfixes
Cleaned up Adding images
merge
Backend for local image save, thumbnail still causing problems, checks need to be implemented
Added sort so answers appear as highest upvoted
Removed CompleteQueuedEvents() from DataManager

Started working on UploaderService. Seems like everytime Android tries
to help you (like with IntentService), it's severely limited and doesn't
do what you want.
Commit before changing interface.

AbstractEvent will gain a Retry() method. This way, the QueueClearer can
use polymorphism instead of a horrible switch-case.
Added a retry() method to Tasks

No more horrible switches on types. Polymorphism ftw.

If you are implementing a new task in the system, don't worry about what
DataManager dm is for the retry() method. UploaderService supplies it
when needed.
Changed the eventbus to use a BlockingQueue.

BlockingQueue has some nice thread-safe features.  Read the huge block
comment on what I did inside completeQueuedEvents() in the QueueCleaner.
There's some very fancy footwork to prevent infinite looping while
offline.
More updates.

RemoteDataStore.hasAccess() now does stuff and is required.
@StephenJust, take a look in UploaderService.java to see how its needed.
I'm not sure trying something network-related, then catching an
IOException within the logic I have is better than just having
.hasAccess() poll the system.

There's a little bit of sleeping evilness on how the service runs. If
offline, it sleeps for a while, then tries again. Not ideal, but we're
running out of days to do StopServiceOnResult(int), then restart the
service later, and do fancy stuff.