NeighborsViewController Part 3

Loading...

En provenance du cours de University of California, Irvine

Toward the Future of iOS Development with Swift

74 notes

Explore Related Videos

At Coursera, you will find the best lectures in the world. Here are some of our personalized recommendations for you

University of California, Irvine

Toward the Future of iOS Development with Swift

74 notes

Cours 5 sur 6 dans Specialization iOS Development for Creative Entrepreneurs

An introduction to the Swift programming language. This will prepare you for more extensive iOS app development and build a foundation for advanced iOS development topics. Upon completing this course, you will be able to: 1. Associate the relationship of Swift and Objective-C and their use in iOS and Mac (OS X) programming 2. Develop the ability to read and write Swift code 3. Distinguish how both programming languages can be used together in applications 4. Demonstrate how to write applications entirely in Swift with the help from several iOS programming samples 5. Determine how Swift can be used for development on new platforms such as Apple Watch and Apple TV 6. Create a working client-server iPhone application with location services that you can add to your portfolio.

À partir de la leçon

iPhone Applications and More

In this last week of the course, you will follow along and create a more full-fledged application called HoBshare. This is a more complex application that is intended to help you use many of the different techniques and language features introduced in the previous weeks and see how they can be used as tools to develop an application. We will also explore some of the new and exciting consumer technologies that developers can now work with using Swift.

NeighborsViewController Part 17:00

NeighborsViewController Part 26:11

NeighborsViewController Part 39:32

NeighborsViewController Part 411:09

NeighborsViewController Part 510:46

NeighborsViewController Part 611:48

Rencontrer les enseignants

Justin-Nicholas Toyama
UCI Extension Instructor
Lead iOS Developer at Smilefish Corporation
Frank Ayars
UCI Extension Instructor
CTO and Director of Software Development at Smilefish Corporation
Ralf Brockhaus
UCI Extension Instructor
Founder and CEO at Smilefish Corporation

[MUSIC]

All right, so let's move on now.

Let's go ahead and implement this fetch users for hobby function.

All right, so I'm just going to start us off with this method,

and make sure that I have my curly braces balanced, just so

we don't get distracted by errors as we're going through it, okay.

So here we are, and we're inside of our fetch users

with hobby function now that we're creating.

So look at the function signature here, we say func fetchUsersWithHobby, and

then the argument is called hobby, and then so type hobby, it makes sense, right?

So now the first thing we want to do is make sure that we don't

run into bad conditions.

So I have a guard statement here, and

it says go get the CurrentUserId out of our standardUserDefaults, right, so

NSUserDefaults.standardUserDefaults().val- ueForKey,

the key name CurrentUserID that we used when we stored it in there.

And again, remember, spelling and capitalization count.

And then I'd take that value and see if it's convertible to a string and not nil.

If it is, then I can look at the number of characters in that string.

So characters.count and make sure that the user ID actually

has some letters and numbers, actually has some characters in that string.

So you can make sure that it's not an empty string, because it could be none,

nil, but be an empty string, and so that's not a valid user ID either.

So now that I made sure I have a current user ID, and

we have more than zero characters in that string,

we have a pretty good chance that we have a valid current user ID now.

But if that's not the case, then we'll get inside of this guard statement.

So we need a good user ID to go to the server and

say, hey, server, give me some lists.

Here's my user ID, so that you know that I have permission to ask you for things.

And also, because you're going to need to pass in your latitude and longitude,

and that way, we can give you users who share your hobby that are near you.

And to make sure that you get some results or help make sure we've defined

near you as within 1,000 miles of you, which is a pretty big scope,

but want to make sure that you can be pretty successful.

So define near you as within 1,000 miles of you, and also,

since we are passing in your lat and long, we take that opportunity to go update your

lat and long inside of the user's table in the database in the backend.

So if you change your location and you press a hobby

on the scene with the map in it, then your location should also get updated.

It says you're working on this project, maybe you're working on it with a friend,

or maybe you have two devices, or a simulator and a device, and

you want to play with the application a little bit.

Just be aware that your location will get updated when you make this call to go

fetch users with hobby.

Okay, so, now that we've made sure we have

a good user ID, and we can get down here.

Otherwise, if we don't have a good user ID, then we'll just throw up an alert

onto the screen and say, please log in before selecting a hobby.

If you don't have a current user ID, that means you probably didn't log in and

it probably didn't get stored into NSUserDefaults, so when we try to get it

out of UserDefaults here, it'll be nil and will fall into the discard statement.

So it makes sense to say, please log in before selecting a hobby.

We need to add an OK button, so that the user can get rid of that alert.

So, we say, let okAction = UIAlertAction,

title will be Dismiss, so they can dismiss the alert.

The style will be a UIAlertActionStyle.Default, so

it should just look like those little white pop-up boxes that we're all used to.

And we need a closure for our handler.

So, we can say when they press the dismiss button,

then we call alert.dismissViewController, and we set animated to true.

And then the alert will, in an animated fashion, go away,

and once the alert goes away, we don't need anything else to happen, so

we can just say completion: nil.

All right, so now that we have the OK action defined,

we can add it to the alert, alert.addAction(okAction).

And now that we have our whole alert configured,

we can say self.presentViewController.

The alert is what we're presenting, and we want to present it in an animated fashion,

set this to true.

And once the alert comes onscreen, we don't need anything to happen, so

again, here, completion can be nil.

And then we want to return out of this fetch users with hobby function,

we don't want the rest of the function to be executed,

so we have to make sure to say return here.

All right, so now that we've taken care of what's happening with our guard statement,

let's look at what happens when things are working right,

when we do have a good current user ID.

So we're going to make the REST call now, make the web service call.

So we're going to say, let requestUser =, the new instance of our user class.

And we'll say, requestUser.userId =,

the user ID that we go and pull out of NSUserDefaults,

which, by the way, we've already made sure up here is going to be good, right?

Now we can say, requestUser.latitude = currentLocation,

if we have it, its coordinate.latitude.

And our requestUser.longitude = same thing,

our current location if we have it, its coordinate.longitude.

Okay, so you saw a little one of my instructions to self.

So [LAUGH] you don't need that comment in the code.

But here now, we're going to go ahead and

call the fetchUsersForHobby data provider function, which we still have to write.

We'll go write it after we do this.

So we'll see a little error for another minute.

But just so we don't get too distracted going to different places,

we're inside of the neighbor z controller.

This is the fetchUsersWithHobby call inside of our view controller, and

we're going to call out to our data provider, right?

So we'll say userDP().fetchUsersForHobby.

We need to know who's making the request, so we put in the requestUser.

And we need to know which hobby we're talking about here.

So we need to put in the hobby.

And then here's our completion closure, right?

So we use that, again, trailing closure syntax, so

you don't see like the word completion call in and then some stuff.

We can just close this with the parenthesis and

then use an open curly brace.

And we know since completion is going to be the last argument in this list

of arguments for the fetchUsersForHobby function,

we can use this drill enclosure syntax, right?

Okay, so when we go make the call to the server,

it's going to give us back a list of users.

So we call that returned list of users, right?

We say, requestUser, that's when we send it, and returnedListOfUsers.

That's when we get information back.

Again, uses words request and returned

object in your code to help you keep track of what's going on.

All right, so now here, we're inside of the closure.

If I return the list of users,

because that's the object that the server is giving us back,

returnedListOfUsers.status.code == 0, that means everything went well.

Then we can say, self.users, remember which is our instance

property we put on this class, = returnedListOfUsers.

All right, so now we put the returnedListOfUsers.users

survey into self.users, so that up here,

when a user taps on one of the cells in the collection view,

we can see if there is anything in the self.users array.

And then if there is something there,

we know that we should remove the map pins before we add the new map pins.

So that's how that works.

[MUSIC]

Explorer notre catalogue

Rejoignez-nous gratuitement et obtenez des recommendations, des mises à jour et des offres personnalisées.

Coursera propose un accès universel à la meilleure formation au monde, en partenariat avec des universités et des organisations du plus haut niveau, pour proposer des cours en ligne.

© 2019 Coursera Inc. Tous droits réservés.

Télécharger dans l'App Store

Disponible sur Google Play