-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wednesday lab #3
Open
robert-hatfield
wants to merge
33
commits into
master
Choose a base branch
from
wednesday-lab
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Incomplete... I'm not doing anything with the results yet.
We're using a placeholder array of data until we can get data from Firebase on the TV and Watch platforms.
This is initially assigned as an NSNumber of zero when new todos are created and sent to Firebase. On retrieval, the NSNumber is cast into the Boolean equivalent for readability in client-side code.
The destination view controller receives a Todo object, and uses it to define it's own title.
I moved logic for Firebase and a "database" of todos into a singleton class. Using NSNotifications to advise observing views of changes to the data.
This view controller subscribes to NSNotifications from the singleton TodoDatabase.
Note that there is currently no user authorization since Firebase Auth doesn't currently support tvOS.
I also removed the NSNotification center property, since it's not needed elsewhere in the class.
This isn't an ideal UX, but the functionality is there. I'd like to present a subview with editing options instead. Quite a bit of work to this end was done on an experimental branch, but I couldn't get it working tonight.
Work in progress.
Crashes when attempting to validate user email. The dictionary object for each user is being interpreted or cast as a string object somehow.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Lab Assignment
Todo
objects on Firebase, add thecurrentUser
's email to eachTodo
.currentUser
on Firebase, which was given as an alternate solution in lecture. I feel this is much cleaner and keeps this property coupled to the user reference, rather than to eachTodo
object.Todo
s from Firebase in your TVOS application.TVOS
application first launches, before loadingTodo
s into thetableView
, you should prompt the user for their email, and populate theUITableView
with only their associatedTodo
s.GCD
for your operations instead ofNSOperationQueue
.