search

martasmith / HackTheHood

1 stars 0 forks source link

Create local persistent objects as per schema #14

Closed ravirani closed 10 years ago

martasmith commented 10 years ago

Could someone volunteer to take this ticket tomorrow and implement some really basic functionality by Monday before class? Should this go to you, @TomHarte as it seems like the logical continuum of the schema creation? Is this something you are willing to take on?

TomHarte commented 10 years ago

I’m happy to do the local side of things, with persistence by whatever means, but we’re not using parse unless Ravi doesn’t succeed with his Google Sheets task. So I think this may be two tasks in one, one of which may never be needed. So I’ll split it and take the first part.

On 12 Oct 2014, at 12:05 am, martasmith notifications@github.com wrote:

Could someone volunteer to take this ticket tomorrow and implement some really basic functionality by Monday before class? Should this go to you, @TomHarte as it seems like the logical continuum of the schema creation? Is this something you could take on?

— Reply to this email directly or view it on GitHub.

martasmith commented 10 years ago

Sounds good, Thomas! I agree. Would creating model classes for the project fall under this category, or does that need to be a separate task?

TomHarte commented 10 years ago

Yes, I consider this task to be to create local model objects matching the schema (once that’s complete) and to ensure they persist. Which I will do tomorrow.

On 12 Oct 2014, at 00:11, martasmith notifications@github.com wrote:

Sounds good, Thomas! I agree. Would creating model classes for the project fall under this category, or does that need to be a separate task?

— Reply to this email directly or view it on GitHub.

martasmith commented 10 years ago

Sounds great! Thanks, Thomas.

TomHarte commented 10 years ago

Model objects are sketched out and I'm going to add a getTestUser factory method that creates an example user with an in-progress web site, so that other segments are not blocked upon the completion of either persistence or login/signup (i.e. user creation, which will need to wait for a determination on the web services).

TomHarte commented 10 years ago

I've performed what I believe to be the necessary ActiveAndroid steps and added a factory method, getTestUser, that:

• if no test user has yet been created, it creates one with a website with three pages and saves it to the store; • otherwise it retrieves and returns the existing test user.

Obviously the relevant Activity when complete will accept a User as part of its Bundle. But for now I'd suggest that it just call User.getTestUser() and proceed with that, as progress will otherwise be blocked on the Parse side of things (if that's how we're going to authenticate users; we'll discuss it tomorrow as I have only a vague notion about this side of things) and on my completion of the Login/Register page.

I didn't actually do persistence for any of the homeworks and I used SQLiteOpenHelper for my TODO app so this is my first run at ActiveAndroid. Issues may therefore be forthcoming. But we'll see. I'm going to close this issue with the expectation that we can reopen if latent mistakes become apparent.