My Schedule / Favourites

[peirix]

List:

• All sessions someone has marked as a favourite
• Should have the ability to "drill down" to the "Session detail/info" screen

[yornaath]

I propose two models for the program data storage. Either we use localstorage/indexDB and store it locally, then the user don't even need sign up to start marking his/hers program.

Or we store this in the backend so the user can view it on multiple devices. Though then we need the user to register. using twitter/ or Facebook for example.

[alexyork]

I vote for HTML5 local storage. It is simpler. I don't think people expect to log in to a conference app, and remember their data between devices: I think people will use it on their phones the day before the conference to plan what sessions they will go to, and then refer to it during the conference to see what they are going to next :-)

[yornaath]

I personally wouldn't mind the sync. I tend to sit and plan in front of my laptop or desktop then use my phone during the day to check my schedule.

On the other hand, i feel this is a "nice to have" and not overly important.

[peirix]

We can start with local storage, and then expand to include login if we have the time and people request it.

[alexyork]

Agree, local storage for now. Keep It Simple :-)

[yornaath]

I have implemented the following:

TrondheimDC.Models.Session.prototype.favourite Save the sessions id in a serialized array of favourited sessions in localstorage.

TrondheimDC.Models.Session.prototype.unfavourite Remove the sessions id in a serialized array of favourited sessions in localstorage.

TrondheimDC.Models.Session.prototype.timeslotConflictsWith Takes a session as parameter and checks if there is a time slot conflict. Returns boolean

Have also implemented a checkbox in the template for sessions and event listeners for toggling the session models favourited state.

[alexyork]

I am closing this issue because it works. Any tweaks or changes can be created as new issues.