It's now that we have our neighbor and manager set up here how do we then see at least something.
Because we are printing these data list which should have our adjacent payload.
Well let's go to our content view here.
Now it's easy for us to think that well we can come down here and say net working manager like that
and hope for the best.
Well if you save this try to run we're going to have issues.
The reason why is because network manager doesn't return a View and anytime here in central body we
have to show something that returns a view.
So this wouldn't work.
But what we can do is actually come here as a var called is net working manager as such.
It's gonna be equal to net working manager like this.
Now that we've instantiated it save this and run.
Hopefully we should see something in our console.
Now we have to actually open our console to the bottom here.
And while I can see looks like I see something there.
Let's make sure this is a little bit bigger.
And voila.
So we're getting the information folks.
That is indeed good news.
That means we are getting stuff as you can see a lot of information there.
All right.
That's always encouraging.
But the problem persists here.
Yes we have our information because we see that we printing it out here instead of a dispatch to main
a sink.
But then the question persists how do we then show in a list that information showing here at List.
Well at this point is very simple.
We can put in a list.
Remember list and I'm going to pass data here.
What data do you need.
Well it's going to be network manager as such and anything vote in that data list.
Right.
Because a network manager has the data list and then here what I'm going to do is I'm going to put inside
there and when I say data in and I can say text it's going to be equal to data Dot.
Let's see what properties we have.
Let's go back to our data list entry here.
Let's get a title.
Why not.
So data dot title like this now can save and give it a run right.
Looks like we have a problem here.
Right.
So it says here it says member data lists cannot be used on type network manager.
Now one of the things that we have to realize here is because we understand that networking manager
is indeed of type observable object.
Now because we want to make sure that this is actual connect or a content view which is the part that
we show the data.
Right.
The view per say we actually have to come here and say observable or observed object.
OK.
Again which is why we have to do this because these network manager here let's jump to that number.
We said this is observable object meaning that it's something that can be observed.
However when we actually calling it we need to make sure that there's a variable that we attaching this
information to is glass to be these at observed object.
That way that way this view here will know that.
OK.
Whenever we get this network manager is going to return something for us which means then me in this
case as a content view.
If you do show something I'll have to redraw myself with new data if need be.
All right.
Now the problem I have here is that I'm calling the actual type.
This has to be this network manager here.
My bad.
So I have to go ahead and add that one we shouldn't have any problems right now because that is the
instantiation that we created there.
So and voila.
Just like that you can see now we're able to get all that information in our list of course is is still
working here.
Can I just put it down there and close it down and just simply we have all the information showing.
All right.
Very good.
Of course as you know we can pass a few modifiers here.
Let's say I want find to be tidal and I want foreground color to be maybe gray can play around with
all that because now we have that data we can do all sorts of things OK here we go good.
Now the beauty here is that our networking manager here we can always use it whenever we want to go
and pass Jason API.
Right.
Because essentially the same thing happens all the time.
There is of course a few changes here and there.
But in essence the process is always the same one thing to notice though and we'll talk a little bit
more about the observable object at a later time with more detail.
The important thing to remember is that we need to mark this as an observable.
So we want to be able to broadcast to other views that hey I am an observable object meaning that you
can look out for whatever that I'm doing.
If I may change my data and so forth and the actual variable that is holding the pass data in this case
has to be published because we are publishing it to whoever is listening.
In this case a view so swiftly why knows that it needs to brashly view with the new data or the data
that it's being received.
OK.
And of course inside of our content view that variable of course we have to also append the observed
object to say that this isn't amplitude that's being observed meaning hey great we have the data we
can always change things and as things change the UI will also change accordingly to do data that is
being served.
That's it.
And just like that we we're able to fetch data from a distant remote api.