Work on #110

@primehunter326 @milus16

It seems like the issue has something to do with the adapter getting
ready to load the next page and trying to optimize memory or something.
Looking at the stack overflow I put onto the issue suggest to use a
TabAdapter.

I've implemented one here. But it's being troublesome. It does load up
the right pages on the right tabs being clicked no problem. So it would
resolve the issue, however the view is not being displayed. If we can
get the view to display on this branch then we could modify the main
android branch to use it and close the issue.

Anyone more familiar with the tab adapter then I am? I can't really see
why the view wouldn't be instantiated here. The documentation where I
got the sample code from is here:
http://developer.android.com/reference/android/support/v4/view/ViewPager.html
Merge branch 'develop' into android
Merge branch 'android' into issue_110
Got the tabAdapter to work correctly.

@primehunter326

The tabAdapter is now working properly and we are not experiencing the
issue where the comments load when clicking the map icon. If this is the
last commit you pull, the data populating the comments page is synthetic
and not pulled from the API.
Merge branch 'issue_110' into android
Began work on home page

Added start and stop svg's to generation script. Added logo to low res
files becuase it's currently a PNG and not an SVG to generate from.

Created basic layout for the home page, with logo, text and toggle
button. No functionality yet. Once I have internet connection again I
can take a look at the mock-ups and try to get the tab to look correct.
Updated graphics of start button

The start button now alternates between red and green as well as
changing text when clicked. Also, the id's in the start_page xml have
been updated to be a bit more descriptive
Updated main page with layouts

Updated main page with layout and chronometer. The problem from #110 has
shown up again and I'm not sure why.
Added more logging to find #110

Added more logging into the methods being used that might be causing
issue #110

http://stackoverflow.com/questions/13214063/getitem-calling-multiple-time-in-fragmentpageradapter?rq=1

That stack overflow seems to be what we're experiencing. Multiple calls
to get item when clicking a tab. It seems like the android os is
pre-rendering the next frame, which unfortunately, causes our network
connects to boot up and fire away. This is unfortunate to say the least.
We could instantiate all the fragments and keep references to them on
application start up and make sure not to load any data into them. And
then when we detect the view is the fragment we could ask it to load
everything. This seems like it would work, but also knowing android, it
seems like we're just as likely to get null pointers and inflation
problems with views not being present when we're trying to add
information to them. A major refactor is needed of the android code. The
API code needs to be completely asynchronous. Each Fragment needs to be
stubbed out so it's view can be made without reliance on the data being
placed into it, and then methods to populate the data itself need to be
created and used. You'd think we could use the onCreateView, but I'm
pretty sure the pre-rendering is hitting that too. We're probably going
to have to call methods on each fragment to populate from the page
handler selecting the item itself.

@primehunter326 What do you think?

Also I commented out the logging code for the comments, I was tired of
scrolling past every comment's information.
updated the C Sockets Library into the project, made changes to the push method which is now succseffuly pushing batch points to the server
started working on Gg on the GET method which is pulling back the correct NSString, now we just need to parse it into objective-c objects and store it in memory
removed old xml, removed viewpager from tabadapter

Removed viewpaging listening code from the tab adapter because it wasn't
actually called at all. Also deleted the old activity file that wasn't
being used anymore.
Added more logging #110

loggin to show that getItem and onTabSelect are NOT in sync
Moved pager listener into tabadapter

Moved page listening into the tabadapter so we don't have any conflicts
between the main activity trying to change the page and the tabadapter
trying to do the same.
.
Moved comment loading to onStart

In Feed fragment, moved loading to be in onStart so the comments only
load when the android expects to show the page to the user.
Unfortunately, the pre loading causes this to be when you're on the map
page.
Merge branch 'refactor' into android
Removed logging and change onStart to onResume
Merge remote-tracking branch 'origin/android' into android
created CSocketController for an easy objective-c interface between the c socket library
going to get develovelop updates