►
From YouTube: PnP SIG JavaScript Weekly - 18 August 2016
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
A
So
hello,
this
is
the
JavaScript
special
interest
group
weekly
meeting
August
18
2016
I
am
Patrick
Rodgers
senior
program
manager
with
office.
365
we've
got
a
great
call
this
week
we're
going
to
talk
about
some
of
the
activities
they've
been
going
on
in
the
special
interest
group
and
then
we're
going
to
spend
a
lot
of
time
talking
about
the
newly
released
developer
preview
for
the
SharePoint
framework,
which
I
think
is
really
exciting
to
get
that
out
there
and
get
that
into
the
world.
A
A
We
start
off
every
week
kind
of
explain
who
we
are
and
what
we
do
we're
the
special
interest
group
focused
on
JavaScript
and
client-side
development,
and
we
live
in
the
larger
sharepoint
patterns
and
practices
program.
We
carry
this
idea
of
worldwide
one
team,
so
anybody
anywhere
in
the
world
can
join
and
participate.
Whether
it's
through
the
social
channels,
whether
it's
through
submitting
code
or
whether
it's
attending
these
weekly
meetings,
everyone's
welcome,
wherever
you
are
in
the
world,
whoever
you
are,
please
join
us.
A
If
you
have
interest
in
special
era
in
client-side
development,
and
then
you
know
the
larger
patterns
and
practices
program,
if
you
have
sort
of
a
more
general
interest
in
SharePoint
and
will
be
spinning
up
more
of
these
special
interest
groups,
as
interest
dictates,
we
have
three
main
ideas
for
the
team.
The
first
is
the
elastic
team.
We
understand
that
some
weeks,
you'll
have
a
lot
of
time
to
participate
in
other
weeks
or
months,
less
I'm.
A
A
great
example
of
that
recently
I've
had
a
lot
of
other
work
stuff
going
on,
so
I
haven't
been,
as
involved
as
I'd
hoped
to
be.
We'll
talk
about
that.
Briefly
later,
we
also
remain
very
community
driven.
So
when
you
have
a
you
know:
feedback
when
you
have
ideas,
we're
open
to
all
those.
So
it's
it's
ideas
about
making
our
documentation
better,
making
our
code
better
missing
methods.
A
We
want
those
folks
have
a
great
experience
joining
these
calls
submitting
code
getting
their
questions
answered,
and
so
that's
sort
of
the
the
folks
that
the
very
smaller
percentage
that
dive
in
and
participate
and
then
the
larger
percentage
is
going
to
be
those
folks
that
consume
our
work.
We
also
want
those
folks
to
have
a
great
experience
consuming
our
libraries
using
our
work
and
Nico.
B
A
So
we
just
double
check
the
mute
on
everybody.
For
me,
if
you
don't
mind
thanks
evidence
so,
but
enabling
all
developers
to
have
a
great
experience,
whether
you're
contributing
to
the
work
or
consuming
the
work,
we
want
all
those
folks
to
also
have
a
great
experience.
So
again,
very
open
all
are
welcome,
and
then
you
know,
if
you
have
time,
we
absolutely
welcome
all
your
contributions.
A
The
wiki
has
a
lot
of
great
information
there
as
well
on
getting
started
so
I
do
want
to
thank
as
we
do
every
week,
all
our
contributors,
Jordan
I'd,
still
love
to
get
a
full
name
for
you,
if
you're
out
there
and
listening,
but
thanks
to
everybody
that
has
contributed
and
will
contribute
in
the
future.
You
make
this
program
possible
and
it's
really
exciting
to
see
all
the
great
work
that
has
been
going
on.
I
did
want
to
mention.
I
know
we'll
talk
about
this
later.
A
There's
a
couple
of
pull
requests
out
there
that
I
haven't
merged,
yet
that
simply
been
a
time
constraint,
not
a
problem
with
the
pull
request,
so
we'll
be
adding
some
folks
to
this
list
for
next
week's
call
moving
on
our
agenda
for
this
week,
we'll
talk
quickly
about
Yammer
and
get
er.
It's
been
fairly
quiet
last
week.
A
So
this
week
we've
had
some
good
sort
of
general
discussions
and
questions
on
Yammer
and
get
er.
Those
have
been
great
I'll
sort
of
address
it.
Now
I
haven't
been
able
to
participate
as
much
as
I've
done
in
the
past
or
wanted
to
I've
been
really
busy
with
some
other
stuff
actual
work
stuff,
which
is
kind
of
crazy.
A
But
do
it's
great
to
see
the
community
kind
of
pitch
in
and
help
each
other
out
I'm
trying
to
get
a
little
bit
more
involved
through
the
end
of
this
week
and
a
little
bit
the
beginning
of
next
week
we
do
have
a
couple
of
blog
posts
have
gone
out.
A
Shanta
again
put
some
blog
posts
there
in
the
am
or
if
you
haven't
been
checking
out.
His
series
on
using
the
core
library
do
check
that
out,
and
then
there
are
some
issues
and
pull
requests
that
ought
to
be
super.
Transparent,
I
haven't
had
a
chance
to
look
at
in
detail,
but
I'll
look
at
those
before,
let's
say
at
the
end
of
this
week,
I'll
try
and
look
at
those.
So
don't
think
those
are
being
neglected.
I.
Just
it's
been
a
time
time
crunch
for
me.
A
So
then,
down
at
the
bottom
you've
got
a
link
again
to
the
Yammer
and
then
a
link
as
well
to
the
git
er.
If
you
know
those
are
both
great
forums,
if
you
have
general
questions
and
if
you
know
just
sort
of
discussions
want
to
ask
a
question
or
how
do
I
get
started
or
you're
having
issues,
that's
a
great
place
to
start
and
myself
and
others
will
try
and
help
you
out
as
best
we
can
with
that.
A
A
A
lot
of
it
is
going
to
be
very
familiar
without
sort
of
letting
the
cat
out
of
the
bag.
We've
been
trying
over
the
last
month's
to
sort
of
prep
folks
for
what
was
coming
without
being
able
to
tell
you
so
now
that
it's
out,
hopefully,
things
will
feel
very
familiar
and
you'll
be
able
to
be
productive
very
quickly
in
that
new
framework.
I
think
it's
really
exciting.
I
think
there's
a
lot
of
great
opportunities
and
we're
going
to
talk
about
that
in
much
more
detail
during
the
discussion.
A
Part
I
think
in
a
blog
post
out
this
week
on
how
we
generate
documentation.
I've
still
got
the
web
pack
trick
that
I
talked
about
last
week
to
do
that.
Blog,
post
and
I've
been
working
on
the
node
console
app
blog
post,
and
that
is
almost
done,
but
it's
a
funny
story
for
all
these
blog
posts.
I
go
through
and
I
do
all
the
steps
that
I'm
writing
down
to
sort
of
validate
them,
and
it
helps
me
get
screenshots
and
code
snippets
and
things
organized
and
so
I
have
the
the
console
app
sample.
A
I
actually
wrote
a
few
lines
of
code.
Besides
answering
a
million
emails
and
fixed
a
few
bugs,
so
we
talked
about
there's
a
bug
in
batching
in
note:
that's
fixed,
not
yet
merged
dev
and
then
there's
a
few
errors.
I
also
fixed
that
I
found,
while
debugging
in
the
console
app
that
works
for
debugging.
So
a
few
little
things
I
didn't
want
to
mention,
I
haven't
had
as
much
time
lately
to
participate
in
this
due
to
some
ongoing
stuff
work,
but
this
is
a
great
opportunity.
I
wanted
to
highlight
this
for
folks.
A
That
might
be
looking
to
get
a
little
more
deeply
involved
in
a
special
interest
group
or
patterns
and
practices
in
general.
A
great
played
great
time
to
step
up
kind
of
maybe
help
drive
to
completion.
Some
of
like
I,
said
I
know.
There's
some
issues
out
there.
I
haven't
had
a
chance
to
look
at
the
the
pull
requests.
I
still
am
the
one
that
has
to
merge
those,
but
you
know
the
issues
or
just
generally
kind
of
looking
through
those
sorts
of
things.
It's
a
great
chance.
A
There
just
wanted
to
highlight
that
if
anyone's
interested
I
also
wanted
to
mention
I'm
going
to
be
out
next
week,
but
you're
going
to
have
a
fabulous
guest
host,
devesa
has
agreed
to
host
the
call
next
week,
and
so
with
the
call
will
go
on
and
it
will
be
visa
and
likely
by
then
you'll
have
plenty
of
Awesome
questions
about
sharepoint
framework
and
visa,
and
others
will
be
there
to
help
out
with
those.
So
the
call
will
happen
next
week,
but
you
won't
get
to
listen
to
my
lovely
voice.
A
A
I
had
was
thinking
about
how
to
get
folks
kind
of
to
jump
into
the
SharePoint
framework
and
develop
some
stuff
I
want
to
encourage
everybody
write
a
web
part
in
the
new
SharePoint
framework,
and
if
you
want
to
and
I
encourage
anybody
who
wants
to
to
do
this,
let
myself
know
or
for
next
week
let
they
said,
oh
and
if
you
want
to
show
it
off
on
this
call,
I'm
really
happy
to
let
folks
get
on
here
and
discuss
the
work.
They've
done.
A
We
sort
of
did
this
with
the
dev
kitchens
that
we
did
during
the
pre
release
phase,
and
it
was
really
pretty
impressive
to
see
what
a
lot
of
folks
came
up
with
stuff.
You
know
that
I
would
never
have
thought
of
or
the
other
folks
would
never
thought
of,
and
some
really
cool
scenarios.
So
I
think
this
is
a
great
opportunity.
If
you
want
to
write
a
web
part
show
it
off
on
this
call.
A
We
can
do
that
as
early
as
next
week,
I'll
work
with
visa
to
coordinate
how
that's
going
to
happen
but
reach
out
to
us
on
Yammer
or
get
ur,
and
you
know,
make
sure
to
tag
either
myself
or
visa
make
sure
to
include
basa
at
least
for
next
week.
But
I
think
this
will
be
a
really
cool
way
to
get
to
show
off
your
work
and
highlight
kind
of
what
you've
been
doing
and
sort
of
give
everybody
else
in
the
community.
Some
ideas
so
obviously.
B
Patrick,
that's
pretty
much
what
we
do
in
a
monthly
community
calls
in
the
PMP
anyway,
as
showing
it
as
a
final
part
of
the
well
half
an
hour
at
least
there's
always
the
demo
part,
and
that's
actually.
That
would
be
a
great
way
for
other
people
to
learn
in
this
weekly
calls
to
actually
have
a
look
on
what
people
have
been
doing,
what
they've
been
facing
and
covering
the
individual
samples.
A
Absolutely,
and
definitely
it's
going
to
be
a
lot
of
folks
are
going
to
see
stuff
that
we
haven't
seen
we're
going
to
get
great
feedback
out
of
that,
but
also
the
whole
community
is
going
to
get
to
learn
from
the
different
tips
and
tricks
that
that
folks
are
going
to
develop.
As
you
know,
we
all
learn
the
new
framework
and
it
evolves
because
they
are
very
receptive
to
feedback
as
well.
So
if
you
have
real
problems,
you
can
report
those
of
course,
but
do
write
a
web
part
do
show
it
off
on
this
call.
A
I
want
to
kind
of
highlight
all
the
great
work
folks
in
this
community
or
doing
so
very
happy
again
to
sort
of
show
that
stuff
off
as
much
as
I
can
from
my
side
and
that
I
didn't
mention
it
earlier.
But
I've
mentioned
the
last
few
weeks.
That
goes
as
well,
if
you're
out
there
writing
blogs,
and
things
like
that.
A
Do
let
us
know
because
we
want
to
you,
know
again
kind
of
give
you
some
visibility
as
much
as
as
much
as
we
can
either
on
these
calls,
or
you
know,
I'm
happy
to
tweet
stuff
out,
for
you
know
the
folks
that
are
following
me
and
things
like
that,
but
let's
get
into
the
team
discussion.
So
let
me
get
so
if
you
haven't
been
yet
to
the
new
github
site.
A
If
you
go
to
github
com,
/
SharePoint,
that
is
now
us,
which
is
very
exciting,
that
is
the
official
repo
going
to
be
the
official.
What's
this
level
called
an
org
right,
so
this
is
gonna,
be
the
official
org
for
all
the
new
to
SharePoint,
open
source
stuff.
That's
coming
and
right
now,
there's
one
open
project,
so
you
can
go
into
the
dev
docs
and
this
will
walk
you
through
welcome
updates
how
to
provide
feedback
either
through
user
voice
or
stack
exchange.
A
You'll
also
see
folks
are
submitting
issues
directly
here
to
this
a
repo,
so
lots
of
ways
to
provide
feedback.
I
think
is
great,
but
the
really
exciting
stuff
is
out
here
in
the
wiki
and
in
this
wiki.
If
you
haven't
checked
this
out,
this
really
walks
you
through
getting
started
with
the
SharePoint
framework.
It
has
some
hands-on
labs.
There
are
six
hands-on
labs
right
now
from
from
sort
of
the
very
basic
getting
started
with
a
web
part
to
talking
to
SharePoint
to
serving
through
these
different
things.
A
Oh
and
I
forgot
to
mention,
if
you
do
write
a
web
part
and
want
to
show
down
on
this
call
bonus
points
if
you
actually
use
the
JavaScript
core
library
in
your
web
part
just
I
think
you
know
that
would
make
it
extra
cool.
If
you
know
you
want
it
to
be
extra
cool,
but
so
this
is
great
to
walk
through
this
wiki
and
see
these
things
and
I
just
want
to
very
briefly
to
show
you
guys
stepping
through
so
set
up
your
developer
tenant.
A
I'm
going
to
show
you
should
I
set
up
your
machine,
real,
quick,
just
to
show
you.
This
is
all
going
to
be
very
familiar
again,
hopefully
for
folks
that
have
been
with
us
since
the
beginning,
walking
you
through
the
all
the
same
sorts
of
things.
The
only
thing
that's
really
different
is
down
here
at
the
bottom.
This
is
the
new
public
yeoman
generator
for
SharePoint's
you'll
need
to
install
that
as
sort
of
a
first
step
to
getting
started
with
this
stuff.
A
So
if
you've
already
set
up
all
your
dev
tools,
you've
got
Visual
Studio
code
or
visual
studio
and
Commander,
and
all
these
things
installed
or
whatever
you
would
the
same
things
on
Mac.
This
is
kind
of
what
you
need
to
focus
on
is
running
this
npm
to
get
the
new
yeoman
generator.
So
I've
already
done
that.
That's
going
to
take
you
a
few
minutes
to
do
so.
I've
done
that
already
on
my
machine
to
kind
of
skip
the
time,
and
then
it
starts
off
with
the
hello
world
web
part.
A
And
again
these
are
very
step-by-step.
Tutorials
I
think
is,
can
be
very
easy,
but
I
wanted
to
walk
through
at
least
the
first
one
with
you
guys
you
folks,
so
everybody
can
kind
of
see
what
a
you
know,
what
to
expect
and
what
the
experience
is
going
to
be
like.
So
you've
got
here
a
little
message
at
the
top.
That
is
kind
of
reminding
you.
This
is
currently
in
preview,
and
things
could
change
so
you
know
just
be
aware
of
that,
but
generally
things
are
pretty
set.
A
So
what
I
want
to
do
is
I'm
going
to
go
to
this
folder
here,
and
this
is
my
demo
for
folder,
which
may
or
may
not
be
the
fourth
demo
in
a
series
of
demos,
but
so
this
will
walk
you
through
setting
up
your
dev
environment.
So
we've
already
done
that
create
a
project
director.
You've
already
done
that.
Our
next
step
here
is
to
create
a
new
web
part
project,
and
so
this
is
going
to
use
our
yeoman
generator
and
for
those
of
you
that
might
look
at
the
earlier
recordings.
A
This
is
going
to
be
very
similar.
What
you
saw
kind
of
in
the
very
early
preview
bits
I
was
showing
in
those
calls,
but
it's
a
different
name,
and
it's
also
a
little
bit
more
polished
experience
now.
So
this
is
going
to
start
up
our
little
yeoman
generator
I've
already
installed
the
generator
as
I
said
earlier.
So
don't
forget
that
step
so
we'll
get
this
get
this
started
up.
So
it's
going
to
come
in
here
and
again
it's
going
to
ask
us
these
questions
if
you've
used
yeoman
before
this
is
going
to
be
familiar.
A
So
that's
my
solution.
Name
I'm
great
with
using
the
current
folder
hello
world
is
great.
All
these
things
are
great,
except
one
thing
I
want
to
highlight.
If
you
remember
before
you
had
choices
of
no
framework
or
react,
they've
added
the
option
to
use
knockout,
which
I
think
is
really
great.
It
also
helps
show
the
flexibility
of
the
framework
for
you
to
use.
You
know
your
other
components.
Rather,
it's
react,
knockout,
angular,
etc.
Things
like
that,
but
reacted.
A
Knockout
are
kind
of
the
two
I
really
hesitated
to
say:
work
best
but
have
been
most
tested
within
the
framework,
so
you
can
use
any
framework
or
any
you
know,
sort
of
templating
engine
you
like
maybe
like
handlebars
and
let
those
will
all
work
but
reacted.
Knockout
have
really
sort
of
been
put
through
the
paces
a
little
bit
more.
A
So
that's
going
to
create
that's
going
to
take
a
little
while
so
I'm
going
to
go
to
a
little
folder.
I
have
called
demo
three,
which
is
already
a
project
I've
created,
and
the
first
thing
I
want
to
do
is
I'm
just
going
to
do
code
dot,
which
is
going
to
open
up
Visual
Studio
code
from
that
folder,
and
so
this
is
a
very
raw
project.
I
haven't
done
anything
in
here
that
isn't
generated
by
yeoman,
so
you
can
see
here
all
the
different
folders
that
get
created.
A
This
is
very
much
like
what
you
saw
before.
You've
got
your
vs
code
settings
and
tasks.
There's
the
dist
folder.
All
of
this
you've
likely
seen
before
the
one
thing
I
want
to
point
out
is
source.
So
source
is
again
where
the
source
files
are
located.
There's
localization
and
you've
got
your
web
part
component
files,
and
things
like
that
here,
so
you've
got
some
sass
modules,
some
some
CSS
of
sort
of
compiled
CSS.
So
this
is
also
how
the
office
fabric
was
done.
A
So
you
can
easily
incorporate
office
fabric
styles
into
these
sass
files.
Monty
hall
module,
sass
files
to
get
these
sorts
of
things
styled
up
to
look
like
the
office
fabrics.
You
can
incorporate
those
things
very
easily.
You've
got
your
manifest
again.
This
is
all
very
similar
to
what
you
would
have
seen
in
the
sort
of
pre
bits
I
previewed
before,
but
then,
if
you're
worried
about
what,
how
do
I
write
code,
how
do
I
start
doing
stuff?
That's
your
web
part
file.
So
you've
got
here
my
again
I'm
hello
world
web
part.
A
So
this
is
all
typescript
as
we're
all
familiar
with
so
again
based
client
web
part.
This
is
unchanged
from
the
preview
bits.
There's
still
a
single
render
method
and
again
we're
getting
hand
handed
a
Dom
element.
So
we're
being
told
this
is
your
Dom
element
to
render
into,
and
so
this
is
again
very
vanilla,
very
basic,
we're
just
setting
the
inner
HTML
using
a
string,
but
this
is
where,
if
you
were
using
reactor,
you
were
using
knockout
or
you
were
using
anything
else.
You
could
do
different
things
to
render
into
that
right.
A
So
you
could
render
be
a
react.
You
could
render
be
a
knockout
into
that
Dom
element
instead
of
just
setting
the
string,
so
we're
setting
things
creating
sort
of
a
just,
some
HTML,
that's
going
to
get
put
into
our
sort
of
parent
element,
and
then
we
have
some
property
pain
settings.
So
you've
got
one
here
called
description
and
you'll
see
up
here.
A
I
just
want
to
point
this
out
and
you'll
see
why,
in
a
second,
this
property's
dot
description
is
actually
tied
to
the
property
in
the
property
pain,
so
that's
kind
of
exciting
and
then
you've
got
sort
of
your
default
imports
and
your
default
styles
and
things
as
well
there.
So
let
me
pull
back
my
command
prompt
now,
I'm
gonna
run
gulp
serve,
so
this
command
is
unchanged
again
from
the
early
preview,
but
you
can
now
use
this
locally
and
I'm
going
to
run
this
and
what
I'm
going
to
get
is
that
development
dashboard?
A
A
A
And
so
you
can
see
the
1i
update
this.
You
get
a
live
update
in
the
web
part
and
so
that'll
work
with
other
properties.
You
can
bind
those
things
up
and
get
that
to
work
so
kind
of
very
cool
on
the
sort
of
dynamic
rendering
allows
you
to
really
see
how
your
web
part
is
going
to
behave
as
it's
being
edited
things
like
that.
So
again,
this
is
all
local
I.
Don't
have
access
from
right
here
to
SharePoint
data,
but
a
an
interesting
idea
that
somebody
could
explore
that
I
haven't
had
a
chance
to.
A
Since
we've
got
node
running.
You
could
do
something
around
getting
data
using
node
sort
of
a
local
web
service,
or
you
can
also
set
this
up
and
deploy
it
to
your
dev
tenant
and
get
your
data
via
the
dead
tenant.
So
once
it's
embedded
in
SharePoint,
you
would
get
data,
you
know
exactly
as
you
expect
from
sharepoint
one
of
the
things
I
want
to
show
you
so
you've
got
now
a
mobile
preview
here
right
on
this
workbench,
so
you
can
look
at
a
mobile
preview.
You
can
set
the
width
and
height.
A
You
can
rotate
the
screen
and
see
how
your
things
are
going
to
look
on
mobile.
This
is
an
iphone
5
and
you
can
also
do
the
same
for
tablet,
so
you
can
sort
of
see
how
your
sites
are
going
to
look
in
the
workbench,
and
this
gives
you
just
a
quick
way
to
go
through
and
look
at.
You
know,
how's.
My
web
part
laying
out
are
things
looking
the
way
I
want
things
like
that,
so
I've
got
a
question
any
way
to
test
data
SharePoint
from
the
local
workbench
right
now.
A
No,
the
push
is
going
to
be
for
you
to
mock
up
data
for
working
in
the
workbench,
but
there's
also,
if
you
step
through
those
tutorials
there's
ways
to
deploy
this
to
SharePoint
such
that
the
SharePoint,
the
manifest
and
sharepoint
is
going
to
point
back
to
your
local
host
machine
and
the
web
part
will
run
from
local
host
right,
so
you're
serving
the
files
from
local
host.
But
it's
it's.
The
java
script
is
executed
in
the
browser
in
SharePoint,
so
you'll
be
able
to
do
live
edits
edit.
A
So
there's
no
requirement
for
mocking
right
looking
for
folks
to
mock,
but
a
lot
of
folks
I
think
will
work
in
that
sort
of
web
part.
You
know
manifest
in
SharePoint,
pointing
to
localhost
pardon
me
as
I
think
how
a
lot
of
sort
of
the
development
cycle
is
gonna
end
up
being
so
again,
that's
a
very
basic
web
part.
A
It's
your
hello
world
web
part,
and
in
that
article
they
step
you
through
all
the
steps
running
the
gulp,
sir
of
all,
the
things
I've
shown
you
and
then
they
actually
go
through
here
at
the
bottom
and
really
explain
in
a
lot
more
detail.
These
different
methods
and
classes
and
what
the
different
property
pains
are.
There's
been
a
lot
of
work
on
improving
the
property,
pain
experience,
so
there's
different
types,
there's
text
fields,
drop
downs,
things
like
that
toggles
and
really
improving
the
overall
experience.
A
So
all
of
this
it's
going
to
explain
for
you
what
the
manifest
does
so
the
manifest
is
what
sort
of
defines
all
the
parts
of
your
solution
very
similar
to
web
pack.
In
fact,
this
probably
gets
old
into
web
pack
behind
the
scenes
and
then
looking
at
your
preview
code
in
SharePoint.
So
if
you're
actually
trying
to
look
at
this
in
SharePoint,
remember
you
need
to
load
unsafe
scripts
because
those
scripts
being
served
from
localhost.
Aren't
you
know
it's
a
course.
A
You
know
cross
resource
issue
so
load
those
unsafe
scripts
and
you'll
get
to
play
with
your
web
parts
right
there
in
your
SharePoint
site.
So
you
can
see.
That's
all
just
the
getting
started
first
tutorial
and
then
there's
a
whole
bunch
of
other
tutorials
if
I
go
back
up
to
the
top
so
talking
to
SharePoint
again,
that
is
not
going
to
use
the
J
s
core
library,
but
that's
a
great
way
to
add
the
j
s
core
library.
So,
if
you're
looking
to
do
that,
that's
really
easy
I'm,
just
going
to
hit
that.
A
A
So
we're
going
to
install
this
note,
I
use
the
save
devs
that'll,
leave
it
as
a
dev
dependency
for
my
little
demo,
three
project
here
and
I'll,
give
it
a
second
to
get
going,
and
I'm
going
to
look
back
over
here
there
any
questions
here:
okay,
yeah
bass,
is
answering
all
these
in
line.
This
is
great
making
my
job
nice
and
easy.
A
A
But
this
would
be
a
great
thing
to
highlight
for
folks
who
want
to
make
their
web
parts
and
show
them
off,
and
the
demo
would
love
to
see
how
folks
are
using
the
library
and
how
we
can
learn
from
and
improve
folks
using
the
library
in
these
sorts
of
SharePoint
framework
projects,
so
really
excited
to
see
what
everybody
can
come
up
with,
and
there
I
will
pause
and
just
sort
of
open
the
floor
to
questions
on
generally
anything
SharePoint
framework
in
particular,
or
anything
else.
That
is
on
folks
minds
around
what
we've
talked
about
today.
A
Any
example
of
hitting
rest
in
a
juror
and
handling
cores
or
authentication
so
for
we
do,
but
not
specifically
in
the
SharePoint
framework.
The
core
stuff
is
handled
on
the
server
side.
So
you
would
in
your
let's
say
it's
MVC
application.
You
would
set
a
couple
of
properties
in
there
that
allow
cores
we
do
have
a
tutorial
on
that.
A
I'd
have
to
dig
up
a
link
in
terms
of
the
authentication
that
is
really
dependent
on
how
you're
doing
off
so,
if
you're
doing
a
Windows
off
or
something
like
that
and
they're
already
logged
in
it
may
just
work.
Otherwise
it
depends.
But
but
all
these
examples
are
things
that
we
really
are
working
on
getting
together.
If
you
have
ideas,
certainly
welcome
community
contributed
samples
for
things
like
this,
so
it's
really
there's
a
lot
of
ground
to
cover
and
we're
just
in
the
pre-release.
A
So
that's
a
great
idea
and
we'll
do
what
we
can
to
get
those
kind
of
samples
out
there.
Let's
see
those
look
like
ETA
on
the
Yammer
web
part
I,
don't
know
if
one
of
those
is
under
development
currently,
but
that
would
be
a
great
community
contribution.
A
Yep,
it's
a
great
point
from
bill
and
I
can
mention
that
a
little
bit
louder.
We
are
encouraging
folks
to
go
to
SharePoint,
docked,
stack
exchange
com
for
support
and
questions,
one,
that's
sort
of
becoming
kind
of
the
de
facto
place
that
everybody
goes
for
answers
and
it
helps
folks
who
have
a
question
or
have
rather
the
same
question.
That's
already
been
asked
to
kind
of
find
that
answer
so
do
encourage
you
to
use
stack
exchange.
I
know
the
product
group
is
actively
tracking
that
and
helping
respond
to
folks.
A
B
Some
reason
so
right
now,
it's
it's
by
design
the
whole
idea
that
we
are
in
that
wiki
or
the
solution
is
kind
of
awkward.
It's
just
a
temporary
solution.
We
will
be
moving
the
documentation
to
Devdas
com
whenever
the
doctor's
office,
calm,
/
SharePoint
will
be
available,
but
there
was
a
timing
issue,
and
so
we
needed
to
get
the
documentation
somewhere
and
that's
why
the
week
it
won't
be
opened
up
or
anybody
else
to
contribute.
B
So
it's
only
for
people
who
are
actually
writing
the
tutorials
and
we'll
be
continuing
doing
that
when
it's
moves
the
depth
of
circle,
but
issues
for
requests,
suggestions
more
than
welcome
and
we'll
see
well
what
we're
going
to
do
in
the
future.
This
is
going
to
be.
These
tutorials
are
going
to
be
the
official
tutorials
in
the
official
documentation
whenever
we
get
our
final
location
in
place.
C
B
That's
going
to
be
in
a
key
top
and
it's
going
to
be
open
source
fully
yeah
we're
looking
into
getting
a
lot
of
the
actual
components
in
the
SharePoint
framework
as
source
open
and
some
elements
might
still
be
kind
of
a
in
quotes
hidden.
But
the
object
is
to
get
enough
maturity
of
the
stuff
fracture.
We
at
least
source
open,
if
not
open,
source.
B
It
yeah
we'll
see
we'll
see
how
it
actually
goes,
but
there
is
it
already
at
this
sign
which
has
been
decided,
but
I
cannot
share
that
so
and
there
will
be
a
opportunity
and
a
location
for
community
contributions,
samples,
documentation
and
all
of
that
as
well.
But
it's
a
timing
and
resourcing
thing
so
we
need
to
bulk,
like
I
wrote
in
the
iron
window
by
using
the
nkotb
method.
If
you
don't
know
what
Inco
OTP
means
you
didn't
have
a
look
on
the
Google,
but
it's
it's
in
symbol.
It
step
by
step.
B
C
But
I
thought
it
was
interesting.
Reading
the
the
Kathy,
the
part
of
the
a
the
was
actually
in
the
wiki,
whereas
about
the
philosophy
that
card
design,
philosophy
behind
it
and
it
was
staying
in
there
that
the
the
add-in
model
is
kind
of
it'll
still
be
around.
But
this
is
kind
of
hinting
that
this
is
the
new
way
for
and
I
think,
maybe
we're
moving
into
a
phase
where
it's
not
really
the
job
of
Microsoft
to
yeah
and
in
this
new
world
of
open
development.
C
So
it's
not
really
Microsoft's
job
to
tell
developers
out
they
need
to
build
things,
as
should
just
create
some
tools-
and
here
you
are
here-
are
some
tools
you
can
use
these
or
you
can
use
these
other
tools
or
whereas,
because
in
the
past
everything
was
proprietary
and
you
couldn't
get
it
it.
So
if
you
needed
Microsoft
to
tell
you
how
to
use
SharePoint
be
because
you
couldn't
see
what
was
what
it
was
doing
behind
the
scenes
exactly,
whereas
now
it's
a
different
world
were
living
in
turf.
B
No
doubt
and
like
you
mentioned,
adding
model
will
be
there.
It's
built
a
fully
supported,
there's
a
a
certain
scenarios
like
if
customers
are
looking
into
full
security
and
isolation
for
external
audience
and
external
customizations
and
adding
more
or
less
to
chosen.
One
sharepoint
framework
is
executed
within
the
context
of
browser
using
the
permissions
of
the
end
user.
So
if
that's
a
concern
and
then
adding
more
or
less
option,
but
it's
it's
always
debatable.
B
C
B
I
agree
and
personally
I
always
hate
it.
If
there's
any
session
in
any
conference
which
the
title
contains
words
best
practices,
that's
let's
see
how
I
put
it
in
there
here
in
a
polite
way
and
that's
not
accurate.
That's
not
that
you
cannot
be
fine
prospectus.
Experian
best
practices
depends
on
the
audience
and
there's
a
technical
skills
of
the
team
and
the
size
of
the
company
or
development
stuff
and
and
there's
Mulder
balance
but
and
the
situation.
Then
the
situation
told
them
you
try
to
solve
exactly
exactly.
B
A
B
Well,
yeah
so
bathrooms
and
practices.
I
think
that
at
least
the
new
hate
patterson
practices,
what
we've
been
doing
now
for
a
few
years
and
the
PMP
javascript
stick
is
a
good
example.
What
we
want
to
do
is
show
how
to
get
stuff
done
and
and
how
do
how
to
get
you
guys?
Unplugged,
that's
really
the
case.
It's
not
about
some
of
the
samples.
B
What
we're
providing
are
super
simple
and
they're
intentionally
simple,
so
that
they
are
easily
approachable,
so
you
don't
have
to
have
a
PhD
which
bill
probably
has,
if
I
remember
correctly,
have
to
be
able
to
understand
to
what
is
the
right
pattern
to
do
on
what
is
the
wrong
pattern
to
do?
That's
a
one
way
of
thinking:
let's
enable
the
community
to
do
their
stuff
and
make
money
and
be
successful
in
the
microsoft
products
and
then
and
I'm
sure,
it's
early.
B
C
A
A
Question
any
integration
with
SharePoint
mobile
app.
We
can
test
at
this
point
not
specifically,
but
if
you
put
the
web
parts
on
the
dev
tenant,
you
point
the
mobile
app
at
the
dev
tenant.
You
should
be
able
to
see
them,
as
you
would
other
things.
So
there
isn't
a
specific
API
or
integration
point
to
test
other
than
they
should
show
up,
and
you
should
be
able
to
see
them
and
interact
with
them
on
mobile
or
in
the
mobile
app
and.
B
On
that
one
over,
so
that
the
mobile
is
a
big
big
bet
for
us
in
the
future,
including
cross
the
cross,
the
channel,
not
just
windows,
phone
and
I
am
so
iPhones
and
Android.
So
there
will
be
guidance
round
one
of
those
considerations
when
you're
writing
a
ship
on
framework
solutions
target
across
devices.
But
basically,
if
you
follow
up
the,
if
you
build
stuff
using
the
framework
check
on
framework,
one
fundamental
benefit
out
of
it
is
that
it
will
automatically
scale
well.
A
A
big
part
of
that
is
using
that
office.
You
I
fabric
for
your
layout
truth,
because
that's
gonna,
that's
what
we
are
going
to
use
in
the
product,
sotalol
kind
of
as
it
collapses,
and
the
grids
do
all
their
grid
stuff,
it'll
all
kind
of
flow.
The
way
you
would
expect
so,
but
the
framework
is
very
mobile.
First
I
guess
is
a
good
buzz
word
to
throw
in
there,
but
definitely
should
work
on
mobile
as
well
as
phones
and
we're
definitely
not
just
targeting
Windows
Phone
we're
not
just
for
the
one
percent.
A
Few
people
typing
like
I,
said
next
week:
vaisseau
will
be
your
guest
host,
so
you'll
get
a
full
hour
of
getting
to
hear
they
saw
you
get
by
then
I.
Imagine
folks
will
have
some
really
good
detailed
questions
that
I
get
to
hand
off
to
him
for
next
week
so
but
do
get
out
there
and
so
got
a
question.
So
developers
can
use
anything.
So
we
can
end
up
with
mobile
pages.
Loading
react
to
different
versions
of
p.m.
pjs
and
three
different
versions
of
angular
all
trying
to
load
on
mobile.
A
So
the
answer
is
sure,
but
the
hope
is
that
an
organization
would
be
a
little
bit
more
coordinated
than
that
and
sort
of
not
allow
that
to
happen
right,
but
yeah,
that's
certainly
possible,
which
is
why
we're
sort
of
saying
react
as
a
great
choice.
Knockout
is
a
great
choice.
Hopefully
folks
will
keep
their
spp
and
pj
up
to
date
using
all
the
projects,
but
so
yeah.
That
would
be
a
bad
practice
exactly
what
happens
if
you
cannot
get
a
developer
tenant?
A
B
Act
should
be
so
as
long
as
you
go
and
request
the
tenants
yeah,
if
the.
If
the
chrome
is
having
issues
open
up,
aah
or
Firefox
and
in
an
anonymous
mode,
you
absolutely
should
be
able
to
replace
the
tenant.
So
the
only
thing
is
that
there's
a
small
nasty
limitation
within
them
within
the
dev
tenants.
You
cannot
use
the
same
email
address
which
you've
already
registered
in
a
past
when
you're
that
benefit
for
that
the
email
address
have
might
have
been
expired
and
it's
not
an
optimal
setup.
B
I
know,
but
at
least
in
my
case,
I
do
have
two
email
addresses
for
my
hotmail
account
and
I'm
using
my
hotmail
account
and
because
it's
it's
pretty
classic
already
and
so
I
do
have
an
outlook
address
for
my
hotmail
account
so
I
being
able
to
register
to
their
tenants
one
for
my
hotmail
and
one
from
my
outlook
and
I
just
as
well.
I
can
go
to
the
gmail
and
register
an
email
and
register
that
as
I
a
stoner
or
401
denim.
B
B
B
Great,
what
happens
after
the
first
year
of
the
free
turn
on
the
glove
size
becomes
paid?
Is
that's
going
to
happen
and
I'm
not
actually
sure?
What's
the
if
it's
an
msdn
benefits,
if
you
have
an
investor,
and
that's
free
I
haven't
thought
about
that
one
for
10
years,
because
I
got
I
have
msdn
and
I'm
I,
don't
think
we
have
a
price
for
the
distance
I,
don't
know
I
I
really
don't
I.
B
One
great
new
thing
within
the
distance:
you
can
actually
see
that
one
already
with
the
nude.
If
tenants,
if
your
request
the
one
today
they
no
longer
have
a
one
account
limitation,
you
can
actually
have
25,
so
you
can
actually
do
a
proper
testing
as
an
end
user
and
an
administrator
and
a
different
permissions,
and
that's
a
huge,
huge
improvement.
A
A
Great
so
thanks
everyone
for
attending
the
call,
and
thanks
for
bearing
with
us
with
a
little
bit
of
technical
difficulties
there
at
the
beginning.
Sorry
for
that
I
do
really
want
to
encourage
you
guys
get
into
the
new
SharePoint
framework.
Learn
it
give
us
feedback
and
by
us
I
mean
sack
exchange
or
the
github
site,
for
the
SharePoint
framework.
Welcome
to
bring
your
questions.
These
weekly
calls
do
write.
A
Some
web
parts
really
want
to
sort
of
start
showing
those
off
to
show
off
one
your
work
and
also
kind
of
give
the
community
a
great
source
of
learning
and
ideas
on
what
would
be
possible
once
you
kind
of
get
into
this.
Like
I,
said
the
dev
kitchens.
It
was
a
really
successful
project
to
see
all
the
different
things
that
others
produced
so
excited
to
see
what
all
of
you
will
come
up
with
and
I
guess.
A
Final
question
from
Nigel:
there
I
am
her
successor,
not
a
hundred
percent
certain,
what
we're
doing
yet
we're
still
working
on
figuring
that
out
so
we'll
let
everyone
know
for
sure
they're.
So
thanks,
everybody
have
a
great
rest
of
the
week
and
weekend,
like
I,
said
that
you'll
have
a
so
next
week
as
a
guest
host,
so
bring
him
all
your
hardest,
most
difficult
questions
and
then
really
get
into
that
SharePoint
framework.
Thanks
all.