konklone / campyre Goto Github PK

Use APNDroid for simulating this.

Render them in an ImageView that loads asynchronously.

Make it the label, essentially.

Optionally, let the user give an accompanying caption to a photo they're Sharing to the Campfire.

It's got to be done.

Typing an email address with it is difficult.

And grey out or otherwise disable full rooms.

Have a specific item that shows when a file was uploaded, with a link to it.

Shortcuts to specific rooms, with a separate "room" icon.

Render them with the thumbnail image, and a short note to click on it to open it. Have it do whatever the Intent is to send it to YouTube or the Browser.

This means login, room fetching, file uploading, polling, and speaking.

We need to simulate "Remember me", because the cookie is expiring, and one needs to log out and log back in to get the room list to appear again.

Where it's appropriate, call finish() on the Activity afterwards. Where it's not, don't bother with this yet.

They must have changed something server-side. Figure it out.

Have a specific item type for locking/unlocking of a room.

An Activity just for rendering them in their entirety, that the list item links to. Wrap lines by default for now.

If you launch the Login activity (through RoomList or whatever), flip the screen, then hit back, another Login activity is launched. Hitting back again will exit.

Whatever fix you make needs to go in RoomList, RoomView, and ShareImage.

Just take the user right to the room. This applies to making a shortcut, selecting a room for image uploads, and just navigating into a room.

Especially wide screens, thanks to the Droid.

Load all the user data available from the room request when you do it upon joining the room. Will lower the network requests that go into joining a room.

Tiny problem, not usually reachable. Solution is probably to check in RoomList and RoomView's launch mechanism for Login to see if it already launched before launching it.

Find a way to get rid of that.

Easy to do.

Have a specific item for when someone changes the topic.

This will be most corporate accounts - a big deal.

Both its Github project name and its marketing name. Can't launch this thing with a copyrighted name.

That's the only case it happens. Good luck.

Version tests.

Sounds, like trombone. Not sure how to do this, but look at the response data.

The mime-type is hardcoded to image/jpg. Make sure this works with PNGs and other non-JPG images.

Because apparently you can get that far saying you're not on SSL, even though you are, but it fails on joining the room (at some point).

Have the user select which room to upload the image to, from the room list.

Find out what error code this returns, and add it to the case statement in Room.join() as a specific failure message.

Have two item types (one display view, presumably). Does have a user_id, doesn't have a body.

On RoomView, store the room's list and room details on screen flip so that we don't have to re-join.

On RoomList, store the rooms array and don't re-fetch the rooms.

On ShareImage, make sure nothing crazy happens.

Show the topic of the room, the users, and the last 5 uploads.

This includes image and youtube links, even if we're not going to render them properly.

Offer a link or button that opens a web browser to the user's account page, so they can copy/paste the API token.

Instead of adding each item on each line. A mild refactoring.

We still don't have a good app icon for a Market release. Uh oh.

With links to download them, of course.

If it's a 200, bingo. If it's a 302 to the right path but with https in the title, it's bingo, but with SSL. If it's anything else, proceed as usual.

Not "from_phone.jpg".

Try to hold the scroll bar where it is, even though the whole list is being reloaded.

If that doesn't work, then just always scroll to bottom for now.

We have destructive background tasks (speaking, uploading an image, etc.) that we can't have invisibly run twice. We have to figure out proper management of background tasks.

Once everything is in AsyncTasks, we should keep instances of them as member variables on the model when they run, and these should be stored as part of a Holder stored in onRetainNonConfigurationInstance, and reset in onCreate.

The AsyncTasks should each have a pointer to their context, and in onCreate, any restored task instances should each have their pointer updated to be "this". Additionally, before a new AsyncTask is created, it should look at the member variables to make sure there isn't a running instance already.

Each AsyncTask should manage any corresponding dialog internally in its entirety, using dialog variables and avoiding the dialog handling framework.

Generalize it for uploading files, return the USER_AGENT to a private member variable.

With a small popup dialog, see the topic of the room. Possibly merge this with the membership list.

Enter the short guest URL suffix to join a guest room.

Not just images.