I'm Ward Bell, I'm VP of technology and a founder of

IdeaBlade, a company in the Bay Area.

And I'm here to talk about Angular and Breeze.

Breeze is our product and Angular is a Google product,

and they work really well together when you're building

CRUD apps, which is Create, Retrieve, Update, Delete,

something like that.

Anyway, if you business apps are a very

typical part of this.

I come from the Microsoft arena.

We build a lot of business apps there.

And so building business apps is kind of what

I know a lot about.

I don't know how to build games, but I know how to build

business apps.

And because I don't know how to make games, I can't be

Huggy Bear, because I can't do a lot of bling.

So I have to do the thing that a lot of business developers

get paid for, which is to build business applications.

And you can call them Line Of Business applications, that's

LOB, and CRUD apps.

They kind of go together, because they're all about

asking for data and saving data and stuff like that.

And the typical category is ERPs, and I wish I could--

Enter source, Resource.

You know how you know the acronyms, you

don't know the words.

CRM, Custom Resource Management, asset tracking,

call centers.

The kinds of apps in which users sit in front of them for

long periods of time and they answer questions like, I've

got to go find all the orders and I've got to fix them.

Or I've got to book a premium three-week vacation or renew

rail cars, or something like that.

These are the typical tasks that people sit in front of

them all day long.

And really what the modality is that's pretty common across

all of them, is that the user sits there are tries to find a

target data set to work on like orders and

something like that.

And then the application pivots around that data set,

looking at it from different angles as they process it.

So they're not surfing all over the place.

They just find what the customer is interested

in and go at it.

And so from a computing perspective, it's really a

small set of data.

But from their perspective, it's not so small, because

it's about what fits in their head, fits in

their attention span.

So they usually just grab onto a chunk of data and then sit

with it for a long time.

Now because they work all day long doing that kind of thing,

the most precious resource is the user.

And so the whole idea is to say, let's move all the

computing right there.

Let's have client side computing,

client centered computing.

Another term for this might be SPA, Single Page Application.

You could think of it as Ajax applications, HTML JavaScript

app, whatever you want to call it.

We call it SPA a lot where I come from.

That's it.

And Angular JS ought to be really good at it because of

what you just saw.

And it turns out it really is.

And so what's happening is that a lot of people who are

in the Microsoft space are seeing this Angular thing

coming, and they're kind of interested in it.

And one of the reasons--

well, there's a list of reasons about why they are.

For one, it's comprehensive.

So it does a whole lot of things.

You don't have to buy a whole lot, or get a

whole lot of libraries.

It does screen.

You can handle screen management, and dependency

injection, and a whole bunch of other things that you can

learn about.

It's really elegant to work with, which is nice, because

there are some other comprehensive ones that just

seem like you write, and write, and write, and write,

and write, and write, and write, and you can't figure

out what their head was about.

So it's nice and terse.

Some people really like that it isn't sitting there

listening for observable, so I don't have to have special

purpose objects that raise notification events.

And it has a lot of momentum.

There's a lot of people working to make Angular better

all the time.

And it's getting a lot of traction.

So lots of reasons.

And there are people in the Microsoft space who are very

well-known there who are writing about it, like my

friend Scott Allen here.

So anyway, you start to do it and you're the captain of your

Angular luxury cruise liner.

And really your job is to make sure everybody has a good

time, and you don't end up on the rocks.

That's really your only responsibility.

Just keep it moving.

Keep them happy.

And so once you're doing it, you'll see that really if we

think about that liner, there's the entertainment

section up above, which is where you do the presentation.

And that's where Angular is really super strong.

And if you're doing the line of business stuff, there's all

that data access stuff.

And that's where Breeze is going to come in.

So you could say we're going to help you build applications

from A to B, except that doesn't sound right.

Anyway, so remember it's fine to target data set and

pivot around it.

So it's a lot about data.

And what do I mean by pivoting around it?

Suppose I had an application that was for scheduling a code

camp and there were sessions.

Chances are you're going to have to pick your session or

edit a session or do something like that.

Well, the session keeps occurring from screen to

screen to screen to screen.

And you're really talking about the same session as you

look at it from different angles and

make different changes.

So here we have this class by [? Scott Gould ?]

appearing in four different screens.

And when you finally look at one of the items that's in it,

you'll find that the data that are behind it, it's not just

one object.

It's usually backed by a SQL relational database or

something like that.

So it has relationships to other things.

So sessions have tracks that they're on, and time slots,

and rooms, and speakers.

And you have this sort of network of related objects.

And that's part of the LOB space.

So how are you going to deal with that if you're going to

do it on the JavaScript side?

So I'm going to propose to you that you're going to need to

do queries.

And some of them, because you're going to be on mobile

devices, and some of them, because you're going to keep

looking at them from one view to another, you'll need those

queries to be both local and on the server.

You'll want to be able to cache data.

You'll want to be able to deal with those object graphs I was

describing.

You'll want to be able to do change tracking, because

they're going to be making changes.

And you're going to hold them.

You're not going to just save them right away.

You're not have a save button.

And you're going to want to make those things that you're

dealing with like sessions and stuff, you want

them to have behavior.

They're not just data bags.

If you just read them in out of the database,

they're data bags.

But no, if you're going to use them, they're

going to have behavior.

So you could roll your own framework around this.

This is really what ends up happening, whether you call it

an official framework or not.

And then your ship can run aground.

Or you can use Breeze.

And that's my commercial.

It is open source.

It's MIT licensed.

It's on GitHub.

Enjoy it.

So back to this Angular thing.

And Angular and Microsoft, and Google and Microsoft, cats and

dogs living together, what's that?

But yes, it does happen.

And not only that, but there is now a in the box Visual

Studio is the dot net IDE of choice.

And right in the box now, you can get a Breeze Angular

template that shows Angular working with Breeze inside of

ID, the Visual Studio.

As you can see, they're talking about it on a

Microsoft address.

Not on my site.

Of course, I talk about it, too.

So it's a two-page app.

It's really simple, but it illustrates a lot of

capabilities, both of Angular and of Breeze.

And this is what it looks like when it runs.

And we're going to do a demo of it.

And then at the end, I'll show you more about what you can

learn more.

So--

oh my--

this is later in the day.

No, no, and no.

OK.

Because we're going to build that app later.

So if I were to spin up a new version of the

Visual Studio IDE--

and there it comes--

and I wanted to create a new application, I can do these

template kinds of things.

And there in the web, ASP MVC, I can do that.

And ooh, what's this?

Yeah, there's the Angular SPA, right in there.

So if I just keep on clicking, I'm going to end up with an

application that looks like this.

And just to save you the effort of watching this thing

running away, to fill it all in, it will end up

looking like this.

And this is the a ASP.NETMVC4, if you know that world, which

has a lot of stuff in it.

But the net of it is that your client side application is

right here in these JavaScript files and HTML files.

And if I run it--

and I have to run the right thing, not that one.

Get the right keys.

It comes up.

And I've highlighted some things, because

I've been here before.

So I have my to-do list, and my never-to-do list, and who

knows what that one's going to be.

And I could learn--

here you see I've learned--

no, I'd better learn it again.

Learn Angular.

Turn it off.

By the way, every time I'm going anywhere in here, you'll

see that it's saving.

See?

Save changes.

And I could do a bunch of stuff like that.

And if I say, oh no, see, there's the

validation of all kinds.

Yeah, that's not good either.

And I can switch over here on the second page

and see what I did.

And really, the second page is only about logging

what's going on.

And you can see it saved all these modified things.

So it has some idea of change tracking and error handling,

and it's all reporting that.

And you'll notice that it was initially going remote, but

now it's going locally, whatever the heck that means.

But that means that it could be kind of fast as I flip back