A foundation for the app

[Eric Mill]

Hey guys,

So I forked the repository tonight and my work eventually became
something like a complete reboot. My forked repo is here:
http://github.com/klondike/We-Have-We-Need-Android

I've made the home activity a tabbed set of lists, of the latest
Haves, and the latest Needs. They load in from the network each time
you boot up the app, straight from JSON, and put up a loading dialog
while it downloads. The activities are robust and you can flip the
screen as much as you like while it loads. It parses out most of the
interesting data (I still haven't done timestamps) from each post and
displays them in a custom list view.

It's just the two tabs, and tapping the list items doesn't do
anything. I figure that could be a good spot for you guys to pick up
from?

I put up an APK you can download to quickly test it out and see what I
mean if you want, it's at the following URL. I also attached a QRCode
to this email that is also the link to the APK, for quick scanning.
It's signed using the Android debug key, so it *should* just install
on top of your existing one. If you have problems, uninstall your
current one first.
http://cloud.github.com/downloads/klondike/We-Have-We-Need-Android/wehaveweneed.apk

I'm more than happy to explain any of the things in there - it's
pretty much my boilerplate for custom list activities with a network
backing, forged and evolved through long struggle. :) I tried to keep
the code clean and the object separation intuitive.

Let me know if you guys would like to work off of this foundation.

-- Eric

[Eric Mill]

Any thoughts here? If I don't hear anything, I'm just gonna keep
pushing forward on it...

-- Eric

On Jan 26, 1:21 am, Eric Mill <kproject...@gmail.com> wrote:
> Hey guys,
>
> So I forked the repository tonight and my work eventually became
> something like a complete reboot.  My forked repo is here:http://github.com/klondike/We-Have-We-Need-Android
>
> I've made the home activity a tabbed set of lists, of the latest
> Haves, and the latest Needs.  They load in from the network each time
> you boot up the app, straight from JSON, and put up a loading dialog
> while it downloads.  The activities are robust and you can flip the
> screen as much as you like while it loads.  It parses out most of the
> interesting data (I still haven't done timestamps) from each post and
> displays them in a custom list view.
>
> It's just the two tabs, and tapping the list items doesn't do
> anything.  I figure that could be a good spot for you guys to pick up
> from?
>
> I put up an APK you can download to quickly test it out and see what I
> mean if you want, it's at the following URL. I also attached a QRCode
> to this email that is also the link to the APK, for quick scanning.
> It's signed using the Android debug key, so it *should* just install
> on top of your existing one. If you have problems, uninstall your

> current one first.http://cloud.github.com/downloads/klondike/We-Have-We-Need-Android/we...

>
> I'm more than happy to explain any of the things in there - it's
> pretty much my boilerplate for custom list activities with a network
> backing, forged and evolved through long struggle. :)  I tried to keep
> the code clean and the object separation intuitive.
>
> Let me know if you guys would like to work off of this foundation.
>
> -- Eric
>

>  qrcode.png
> 1KViewDownload

[jeremy freeman]

Hi Eric,
Sorry for the lack of response sooner! That sounds great to me. I
should have some time to work on this tonight. Anything in particular
you'd like me to work on?

Thanks,
Jeremy

[Eric Mill]

I think I'm going to work on the post detail page tonight and get that
going. You could start work on the post form, even though there's no
post API endpoint set up yet. The fields you'll post are going to be
exactly the same as the fields you get from the API's read endpoints.
It'd still be worth designing and building the form. Another idea:
you could add a settings activity that stores one's username and
password, for future use in authentication.

Also, we've got to unify our repos somehow. My changes are broad
enough that they're not going to merge cleanly if you try to just
bring it into yours. Any ideas on how you'd like to handle that?

-- Eric

[Ranjit Chacko]

To enable posting do you think we might want to use the Open Data Kit?
http://code.google.com/p/open-data-kit/

It looks like they've solved a lot of the problems for capturing form
data at the mobile phone and uploading it already. But I don't know
how easy it would be to integrate into WHWN.

Also for the Boston people, do you think you'd all want to meet up in
person this weekend? I'll find out later tonight, but I don't think
there's going to be another CrisisCamp here.