►
From YouTube: SPFx JavaScript SIG 14th of September, 2017
Description
PnP community call on SPFx JavaScript SIG 14th of September, 2017
A
Hello
and
welcome
the
SharePoint
framework
and
JavaScript
special
interest
group
bi-weekly,
call
it
a
September,
14
2017,
just
realized
I
forgot
a
space
after
the
comma
there
and
the
date,
but
no
big
deal
I
think
we
can
get
past
that
we've
got
a
really
exciting
call
I.
Think
for
you
guys
today,
with
lots
of
demos.
We've
got
four
separate
demos,
so
lots
of
stuff
to
cover
I
think
is
gonna,
be
really
great,
but
first
for
folks
that
might
be
new
to
the
call
or
might
be
new
to
watching
these
recordings.
A
You
just
want
to
give
you
a
little
bit
of
an
overview
of
what
this
is
all
about,
so
we
live
under
the
larger
SharePoint
patterns
and
practices
program
and
awhile
ago.
It's
been
over
a
year
now
we
started
this
concept
of
special
interest
groups,
because
the
patterns
and
practices
had
grown
so
big
as
SharePoint
development
continues
to
grow
and
expand
and
focusing
a
lot
more
in
our
case
on
client
side
development.
A
We
also
have
ones
for
sort
of
the
PowerShell
and
the
managed
code,
reusable
libraries
that
I
think
most
folks
are
familiar
with
out
there
so
of
course
check
out
as
many
of
these
calls
or
as
few
as
you
like,
but
always
happy
to
have
folks
on
the
call
or
watching
the
recordings
so
down
there
at
the
bottom.
We
have
two
links.
The
first
one
is
the
SP
P
and
P
community.
That
will
take
you
to
the
Microsoft
tech
community.
That's
a
great
place
to
to
ask
general
development
questions.
A
You
know
you're
stuck
on
a
project
you're,
not
sure
how
to
proceed.
You're
working
on
design.
Those
are
all
great
topics
for
there
and
that
covers
not
just
SharePoint
development,
though
that
particular
link
will
take
you
to
the
SharePoint
I.
Don't
know
what
you
call
it
area
of
that
tech,
community
and
there's
plenty
of
other
areas.
So
if
you
have
you
know
a
focus
on
office
development,
so
office
add-in,
something
like
that.
There's
communities
for
that,
but
that's
really
the
great
place
and
that's
sort
of
been
the
replacement
for
the
Yammer
groups.
A
Don't
know
what
to
call
it
preview:
tech
preview,
dev
preview
releases,
are
documented
and
talked
about
there
as
well
with
samples
so
a
great
place
to
stay
up-to-date
on
what's
happening
in
SharePoint
development.
So
what
are
we
going
to
talk
about
on
today's
call?
We've
got
a
quick
update
on
the
JavaScript
core
component
as
well
as
we're
going
to
talk
about
august's
numbers
which
are
really
exciting.
We've
got
the
SharePoint
framework
latest
news,
which
will
include
a
short
demo
from
visa.
We've
got
demos,
then
from
myself.
A
I
want
to
give
you
guys
an
update
on
the
PNP
JavaScript
core
library,
refactoring
work
we'll
talk
about
that
in
a
little
more
detail
later
and
then
from
belem.
We've
got
communication
between
SPF
x
webparts
through
message,
broadcasting
utilizing
the
pub
sub
pattern
and
from
Chris
Kent
we've
got
item
order,
field,
customizer,
SharePoint
framework
extension,
so
not
for
the
short
titles
this
week,
but
I
think
going
to
be
two
very
interesting.
A
Demos
I'm
excited
to
see
those
in
action
later
in
the
call,
and
then
we
might
have
a
little
bit
of
time
for
open
discussion
at
the
end.
But
I
think
this
is
a
pretty
packed
call
so
not
sure
how
much
time
at
the
end,
we'll
have
but
of
course
feel
free
to
have
the
conversations
in
the
ion
window
as
we
go
through.
The
call
so
I
just
want
to
remind
folks
opportunities
to
participate
in
both
this
call,
as
well
as
the
larger
patterns
and
practices
program.
Demo.
A
We're
always
looking
for
demos
on
this
call,
so
you
saw
of
Ellen
and
Chris
will
be
demoing
some
stuff
later
they
got
to
do
those
by
simply
reaching
out
to
us
on
Twitter
and
signing
up.
So
if
you
have
something
cool,
you'd
love
to
demo,
whether
it's
a
SharePoint
framework
solution,
whether
it's
something
using
the
JavaScript
core
library
or
both
or
whether
it's
just
general
client-side
development
in
SharePoint
kind
of
a
demo,
always
excited
to
have
this
just
reach
out.
Let
us
know
we'd
love
to
have
you
on
the
calls
as
well.
A
You
can
contribute
on
github
and
we're
always
looking
for
feedback,
not
just
on
necessary
the
library,
the
JavaScript
core
library,
but
sort
of
the
the
overall
program
right,
the
patterns
and
practices
program.
So
how
are
these
calls
going?
How
are
the
videos
we
put
out
a
lot
of
different
videos?
So
how
is
that
stuff
going?
What
would
you
like
to
see
more
of
less
of
always
appreciate
that
feedback
from
folks,
especially
when
it's
framed
in
a
constructive
manner?
A
So
a
quick
update
on
the
JavaScript
core
component,
so
latest
updates
I
am
a
little
bit
behind
on
releasing
3.0
of
the
SPP
and
PJs
library,
and
that
is
due
to
some
of
the
refactoring
work
and
updates
I'm
going
to
discuss
in
the
demo
and
show
you
guys
where
we're
at
that's
actually
going
very
well.
But
it's
taken
I've
had
to
do
a
little
bit
more
work.
That
I
initially
thought
on
some
things,
but
that's
we're
getting
very
close
there.
So
we
will
get
a
release
of
3.
A
A
I'll
be
back
on
family
leave
at
that
point,
but
a
lot
of
great
PNP
stuff,
not
just
around
the
client-side
development,
but
all
the
things
PowerShell
etc
is
gonna,
be
at
ignite
as
well
as
a
great
chance
to
meet
a
lot
of
the
core
team
members.
Sadly,
not
me
because
I
always
enjoy
getting
to
meet
folks
and
I.
Think
ignite
is
a
really
fun
time.
So
one
thing
I'm
looking
at
with
SPP
and
PJs,
is
the
possibility
of
just
referencing
the
latest
stuff
from
this
at
P
and
P.
A
Work
will
talk
about
and
see
if
I
can
just
surface
that
up
in
the
SPP
and
PJs,
but
we'll
see
again
not
sure
how
that's
going
and
did
want
to
add
I've
kind
of
been
ignoring
the
issues
list
in
the
repo
on
purpose,
because
I've
been
super
busy
writing
code.
I
will
look
at
those
issues
before
the
release,
so
if
there's
stuff
in
it
needs
to
get
fixed,
I
will
take
a
look
through
there
and
respond
to
things
and
make
fixes,
but
just
a
note.
A
As
always,
if
you've
got
something
really
pressing,
we
of
course
always
invite
pull
requests.
So,
if
you're
sort
of
tapping
your
foot
and
waiting
for
me
to
get
to
something
and
you've
got
a
little
bit
of
time,
you
can
of
course
submit
a
pull
request.
We
absolutely
welcome
those
from
folks
out
there
in
the
community.
So
a
quick
update
on
this
at
PNP
refactoring.
A
We
have
taken
ownership
of
the
PNP
organization
in
github,
and
so
that's
github.com,
/p
and
P,
and
what
that
means
is
simply
a
container
for
us
to
put
our
code
in
it's
in
no
way
a
break
from
what
we've
been
doing
or
from
sharepoint
patterns
and
practices,
or
anything
like
that.
So
it's
not
a
dramatic
move.
What
it
is
is
a
container
move,
so
we'll
be
moving
the
code
there.
A
Eventually
this
is
gonna,
replace
SPP
and
PJs,
but
we'll
have
all
the
same
functionality
and
we're
gonna
talk
about
that
a
little
bit
when
I
do
a
quick
demo,
but
this
is
going
to
have
a
documented
transition
and
we're
gonna
have
helper
code
and
samples,
and
things
like
that.
So
we
understand
it'll
be
a
big
change,
but
we're
gonna
do
everything
we
can
to
smooth
that
transition
and
I
really
think
it
will
be
the
right
transition
for
the
library
and
the
way
we
want
to
grow
and
Patrick.
B
Quick
comment
also
from
my
side
on
this
one.
So,
like
patrick
said,
we
do
have
now
to
be
a
BMP
NPM
organization
and
really
do
the
reason
why
we
wanted
to
have
this.
One
is
that
in
the
future
we
want
to
have
additional
libraries
packages
and
all
of
that
grouped
under
the
scope
as
well,
so
the
SPP
and
BJ's
will
be
the
first
one
of
us
that
they're
looking
into
having
additional
packages,
there's
multiple
MVPs
who've
conducted
on
hey.
How
would
be
able
to
work
with
you
guys
to
get
us
our
like?
B
It
is
out
touring
the
using
the
PMPA
channels
and
all
of
that,
so
this
will
be
the
scope
for
that
and
we
didn't
wanna,
obviously
use
at
share
point
or
at
Microsoft,
because
that's
related
on
the
actual
Microsoft
company
BMP
itself,
and
especially
these
libraries.
These
are
open
source
and
they
are
community
driven
initiatives.
So
technically,
if
Microsoft
would
step
away
from
B&B,
we
would
hope
that
the
whole
thing
would
still
continue,
or
else
we're
not
looking
into
doing
that.
But
still
that's
that's
where
the
guide
here
anyway.
A
A
A
So
the
issues
list
for
the
JavaScript
core
library
is
not
a
open
help
forum.
So
the
it's
not
happening
a
lot,
but
it's
happening
a
little
bit
more,
so
just
want
to
mention
those
kind
of
questions
there.
Just
general
development
questions,
the
the
appropriate
place
for
those
are
the
better
place
for
those
would
be
the
Microsoft
tech
community
lots
of
folks.
There
would
be
very
happy
to
help
you
with
your
project
designs
or
your
general
SharePoint
development
questions.
A
We
do
want
to
keep
the
issues
list
kind
of
focused
on
the
core
libraries,
so
that
can
be
suggestions
for
functionality.
Bugs
you
find
things
like
that,
but
focused
around
the
library
and
then
of
course,
if
you
have
ideas,
please
submit
an
issue,
so
we
can
track
it
and
work
it
into
the
development
cycle.
I've
had
a
few
people
in
different
channels,
so
Twitter,
git
or
various
places
say.
Would
it
be
cool
if
the
library
did
X
and
sure
we
absolutely
can
talk
about
it,
but
I'm
I'm,
probably
not
going
to
remember
or
track
that.
A
A
So
I
just
wanted
to
say
thank
you
to
all
of
you
in
the
community
because
I
know
it's
you
guys
using
this
in
your
projects
and
your
work
that
drives
this
growth
and
I
just
have
to
say
it's
really
a
frankly
amazing.
For
me,
this
is
probably
the
most
rewarding
development
project.
I've
been
a
part
of
in
my
career.
So
it's
great
to
see
the
usage
and
great
to
see
people
being
able
to
pick
this
up
and
apply
it
into
their
work.
A
So
let's
keep
that
growth
going
and
part
of
that
is
keep
that
great
feedback
coming.
So
we
can
keep
making
it
better
and
helping
it
grow
out
there
in
the
community
and
then
the
bottom.
Maybe
a
table
not
a
chart,
shows
you
just
the
raw
numbers
from
that
bar
graph,
so
the
count
of
tenants
and
the
requests
you
can
see
our
tea
in
September,
so
I
grabbed
this
day
ago,
and
that's
probably
what
lagging
by
two
or
three
days
we're
already
up
to
me.
A
Almost
400
million
requests,
so
390
million
roughly
requests
in
September
so
really
exciting.
Really
phenomenal
and
again
that's
thank
you
to
all
of
you
out
there
taking
this
and
using
it
in
your
projects.
So
I
just
want
to
share
those
numbers
because
I
I'm
frankly
amazed
looking
at
them
for
August,
so
great
stuff
and
let's
keep
it
going
so
now,
I
think
vases
on
on
board
for
a
SharePoint
framework
update.
So.
B
A
few
updates
on
the
SharePoint
framework
sites,
obviously
ignite,
is
coming
relatively
soon.
We
will
have
much
more
announcements
on
the
ignite
and
we
can
show
a
lot
of
other
stuff
as
well,
but
a
few
things.
What
have
happened
during
the
past
week?
First,
if
you
are
in
ignite,
they
will
pee
for
at
least
four
or
five
SharePoint
developer
sessions
check
them
out.
B
How
we
end
up
in
that
situation?
Also,
if
you,
if
you
have
actually
time
and
you're
flying
over
to
the
Ignite
on
date
before
there
is
a
queue
pretty
nice
office,
def
pre
day
on
24th
of
September
on
Sunday
a
year
novel
Peter
I
will
be
there
from
MVP
crew.
The
PMP
MVP
crew
will
have
urban
ball
deck
and
Paulo
in
the
room
as
well.
Helping
on
the
development
questions.
There's
a
great
question
on
the
hoodies
again
this
year.
B
I
do
know
that
at
least
the
speakers
or
the
the
booth
people
will
get
at
the
classic
hoodie
at
the
SharePoint
every
day,
so
most
likely
we'll
have
some
of
those
to
give
away
in
ignite
as
well.
If
you
I'm
pretty
sure
that
if
you
join
the
pre
day,
you
will
get
a
hoodie.
If
that's
the
deal
breaker
for
somebody
now
on
the
actual
announcements
of
things.
So
you
last
Tuesday
was
a
Tuesday
so
day
before
yesterday
time
flies
when
you're
having
fun.
B
So
we
did
announce
the
feature
back
to
was
actually
our
released
for
SharePoint
2016
as
part
of
the
feature
back
to
the
SharePoint
framework
is
now
supported
in
on-premises
as
well.
For
the
development
side,
we
didn't
actually
release
a
new
version
of
the
SharePoint
framework,
yeoman
templates
or
anything
like
that
and
I'll
explain
that
in
a
second.
But
we
do
have
a
guidance
on
how
to
actually
start
your
development
on
top
of
SharePoint
2016
in
the
dev
tours
calm,
and
also
we
do
have
a
video
where
we
walk
through.
B
What
does
it
actually
mean
I'm,
creating
a
feature
by
a
bit
part
on
top
of
the
feature
pack
and
then
explaining
some
of
the
considerations
around
that
one
as
I
move
along
within
the
video
really
cool
stuff,
because
this
essentially
means
that
we
are
aligning
or
gradually
aligning
the
on-premises
development
capabilities
within
the
SharePoint
Online.
So
you
can
actually
choose
to
write
a
client-side
web
part
with
such
work
within
both
sides
and
I'll
come
back
on
that
one
in
a
second,
because
there
are
certain
implications
on
this
one.
Now.
B
What
this
means
is
that
let
me
try
to
explain
this
in
a
in
F,
understandable
way,
so,
first
of
all
feedback
to
does
support
client-side
web
parts.
We
do
not
support
extensions
in
SharePoint,
2016
feedback.
Why
well
extensions
are
not
yet
shipped
and
second
of
all,
she
when
framework
extensions,
are
for
the
modern
experiences.
The
shipment
for
ad
2016
feedback
is
still
classic
experience.
So
it's
it's
all
about
classic
pages.
There
is
no
modern
lists.
B
As
that
wait,
I
would
love
to
have
exactly
the
same
version
in
SharePoint
Online
and
in
on-premises,
and,
to
be
honest,
we
would
love
to
be
in
that
position
as
well
the
front
from
really
is
that
there's
always
the
service
line
dependency
on
the
packages,
what
they're
doing
and
the
API
is
what
we're
actually
hitting.
So
since
we
cannot
actually
update
your
SharePoint
2016
on-premises
server
whenever
we
are
pushing
an
update,
we
need
to
do
and
work
on
this
kind
of
a
smooth
version.
B
Multiple
versions
world
now
compare
con
that
one
in
the
following
slide
as
well
slightly
explaining
what
we're
going
to
do
in
the
future
right
now
we
release
the
feature
back
to
you.
We
did
not
release
a
new
version
of
the
packages
which
basically
makes
this
development
experience
lightly
awkward,
because
right
now,
if
you
want
to
do
development
on
the
on
premises,
you
will
actually
need
to
kind
of
fall
back
on
top
I'm
to
a
version
1.02
and
then
do
development
on
on-premises.
B
And
if
you
want
to
have
the
latest
and
greatest
API
on
SharePoint
framework,
you
can
use
the
one
point,
two
or
three
point
framework
and
SharePoint
Online.
But
that
way
part
doesn't
then
work
in
on-premise.
So
not
an
optimal
situation
will
work
on
that
one
as
likely
in
the
future.
So
we're
streamlining
that
one,
maybe
on
ownership
on
framework
2016
feature
two
things.
B
Don't
know
why
because
doesn't
make
any
sense,
but
it
is,
it
is
actually
a
clocked
file,
type
for
SharePoint,
2016
and
I
really.
Don't
know
why
that
Jason
would
be
a
block
file
type,
but
your
honor
you're.
Basically,
you
can
upload
a
chase
file
to
a
library,
but
you
cannot
upload
it
dot.
Json
file,
I
just
don't
get
it,
but
you
are
able
to
adjust
that
in
the
server
settings,
so
that's
absolutely
fine
or
or
in
the
forum
settings
now
what
we
gonna
do
in
the
future.
It's
kind
of
clarified
on
this
following
slide.
B
So
whenever
we
get
the
latest
version
of
the
Yeomen
templates
out,
which
is
gonna
happen
relatively
soon,
obviously,
within
the
Ignite
timeframe,
because
in
enoch
night
were
pushing
out
additional
things
as
well,
and
the
empiric
yeoman
template
will
ask:
are
you
looking
into
implementing
a
sharepoint
framework
webpart
only
to
watched
sharepoint
online,
or
do
you
want
to
support
also
on-premises?
So
there
will
be
a
question
within
the
flow
which
will
then
essentially
dedicate
on
the
direction
where
we're
heading,
and
it
actually
also
predicts,
then
the
future
version.
B
What
we're
going
to
use
to
scuffle
to
your
package
and
the
reason
for
this
one
once
again
is
the
server
side
dependences.
So
we
can't
use
the
latest
greatest
sharepoint
framework
in
on-premises,
because
we
can't
push
server
side
updates
to
your
server
without
your
permission
and
that's
really
the
challenge.
So
if
you
answer
the
only
online,
we
will
then
use
you,
you
will
be
asked
them.
Do
you
want
to
implement
a
with
part
or
an
extension?
B
If
you
will
be
answering
hey,
I
want
to
do
the
same
stuff
or
the
way
I
want
to
implement
my
customization
so
that
it
supports
both
on
premises
and
online.
Then
the
web
part
is
too
much
of
only
option
for
now,
and
then
that
is
predicting
the
actual
version
which
will
be
applied
and
used
for
the
solution.
Scaffolding-
and
that's
how
we
essentially
make
this
happen
pretty
soon
when
we
push
out
the
latest
version
of
the
of
the
human
template.
B
B
Okay,
yeah
I,
don't
I,
don't
know
who
made
decision
and
why
and
then
careers
on
the
SP
ethics
upgrade
path
for
feature
back
to
specifically
in
turn
feature
back
updates
or
do
we
have
to
wait
for
feature
back
tree
and
so
and
so
on
today,
clear
I'm,
not
asking
about
the
generator
I'm
asking
a
particular
tool,
is
supported
by
the
SharePoint
framework
that
will
be
installed
in
the
SharePoint
Online.
Now
you
will
always
have
the
latest
and
greatest
capabilities
in
SharePoint
Online.
So
it's
almost
always
the
same
story
as
with
anything
in
SharePoint.
B
The
latest
and
greatest
is
always
in
SharePoint
Online
for
on-premises.
We
will
keep
on
shipping
additional
capabilities
gradually.
As
far
as
the
sea
use
or
as
part
of
the
feature
backs
most
likely.
What
will
happen
from
a
clarity
perspective
is
that
will
ship
only
significant
updates
from
a
let's
say,
for
example,
for
extensions
and
additional
capability
perspective
as
part
of
the
feature
backs
which
are
not
as
common
as
komoti
updates,
which
happen
at
in
a
monthly
basis.
I
think
we
already
said
that
there
will
be
an
on-premises
again.
B
Obviously
there
will
be
future
on-premises
versions
of
SharePoint
and
those
are
all
players
they
completely
different
story.
So
for
the
SharePoint
2016,
we
will
keep
on
updating
support
for
on-premises
as
part
of
the
larger
feature,
packs
I'm,
not
sure
I'm,
not
aware
personally,
at
which
there
were
service
pack
2
coming
and
when
feedback
three
and
when
it's
actually
coming,
but
those
are
essentially
the
timelines
when
we
sleep
the
version
up
and
then
for
the
upcoming
SharePoint
on
premises.
B
Version
whenever
that's
coming
out
probably
will
have
some
public
information
on
that
in
ignite
that
will
have
them
and
that
the
additional
support
and
capabilities
on
top
of
the
SharePoint
framework,
hopefully
that
made
sense
for
ACS
question
good
dude
quickly.
Moving
forward
on
things,
that's
a
thumbs
up,
that's
always
good!
So
I'm
going
to
quickly
do
it
quickly
quickly,
quickly,
demo
Chester.
This
is
relatively
fast
and
simple
demo
to
show
you
what
we
actually
have
in
the
future
back
to
ya.
B
It
has
to
be
100
Tristan
super
clear
on:
what's
actually
there
I'm
actually
checking
and
showing
you
how
things
bird
so
okay,
okay,
that's
thumbs
up!
This
problem
is
that
you
can
see
what
I'm
sharing,
which
is
good,
confirm,
okay,
cool,
so
this
one
I
say
a
come
on
this
one
is
a
human
template
which
has
been
generated
using
the
right
version.
So
if,
if
I
have
a
look
on
quickly
my
npm
view
and
global
and
depth
equal
cipro,
we
can
say
that
in
this
particular
machine
which
I'm
now
running
I'm.
B
On
and
I
know,
I
using
the
wrong
commands
now,
I'm,
always
confusing
listing
view
for
some
reason.
I
can't
understand
why.
So
you
can
see
that
I'm
running
one
point:
zero,
two
as
a
human
to
narrator
in
this
particular
machine.
Technically,
obviously,
I
could
use
a
docker
I
could
use
NPM
version
or
in
their
managers
to
flip
between
the
NPM
versions
and
have
multiple
generators
on
the
same
machine
or
the
doctor
would
be
there
probably
the
best
solution
for
them.
But
what
I've
done
here
is
that
I've
created
this
relatively
simple
solution.
B
This
is
just
a
plain
web
part
to
show
you
how
things
can
be
actually
at
the
point
few
things
maybe
to
notice
here.
The
package.json
is
reference
into
1.000
a
version,
so
it's
not
referencing
the
1.2,
which
would
be
to
the
latest
version
of
SharePoint
framework.
So
if
this
will
be
a
support
at
Indo
on-premises
and
to
be
making
100%
sure
that
this
package
will
always
have
the
right
versions,
you
can
absolutely
run
the
antenna
shrink-wrap
and
that
will
then
make
sure
that
you
are
always
getting
that
specific
version
of
the
packages
to
the
solution.
B
What
you
are
using
now
in
my
case
I
did
this
I
didn't
want
to
steal
too
much
time
on
the
on
the
call
which
I
already
did,
but
if
that
is
that
is
actually
the
same
web
part
hosted
in
SharePoint
Online
in
SharePoint
Online,
if
I
open
up
the
same
web
part
or
add
it
in
the
feature
back
to
environment,
I've
already
deployed
that
in
the
catalog
I
will
add
a
page
and
because
this
is
on-premises
shape
on
2016
feedback.
Let's
call
this
stick
demo.
It
is
a
classic
page.
B
There
is
no
such
thing
as
modern
experience
in
SharePoint
2016.
It's
only
SharePoint
Online
for
time
being
so,
I
need
to
go
insert
web
part
and
underneath
by
default,
because
I
didn't
update
the
category.
It's
underneath
the
under
development.
There's
my
hello
there
web
part
adding
that
one
on
the
page.
You
can
see
that
it's
getting
rendered
properly
in
here
now
there
is
certain
things
and
obviously,
if
I
now
do
in
the
same
way
as
2.0
normal
online
classic
experiences,
I
can
do
customization
of
this
settings.
B
So
I
can
open
up
to
configure
and
I
can
do
something
hello
there,
sick
audience
and
that's
it.
That's
getting
updated
there
and
okay
and
work
it
so
modern
web
parts
in
the
classic
experience.
Now
there
are
certain
implications
of
this
one
as
well,
so,
as
you
can
see,
and
I
want
to
be
fully
transparent,
as
so
that
you
are
aware
of
this.
If
we
do
side
by
side
this
webpart,
that's
the
SharePoint
2016
feedback
too,
and
then
we
cannot
take
that
SharePoint.
B
When
a
SharePoint
Online,
you
can
say
that
the
same
webpart
it
is
actually
it's
the
same.
1.02
version,
SPF
ex-wife
part
it's
getting
rendered
slightly
differently
from
a
styling
perspective.
The
functionality
is
the
same,
but
do
you
the
dependency
is
one
the
office
UI
fabric
and
the
different
slightly
different
styling
in
SharePoint
2016
and
in
SharePoint
Online.
There
might
be
some
small
changes
in
the
in
the
rendering,
and
you
can
tackle
this
actually
by
overriding
this
rendered
rendering
settings
within
your
implementation.
I
didn't
do
that.
B
I
just
took
the
basic
output
of
my
work,
which
would
be
referencing
to
those
Styles
directly
within
the
page
and
that's
the
reason.
Why
are
able
to
say
that
there's
an
alignment
or
padding
difference
in
here
the
same
applies
if
I'm,
creating
a
classic
pates
and
sharepoint
online
and
I
can
actually
quickly
prove
that,
because
that
doesn't
take
too
long.
So
if
I
cut
the
site
pages
and
quickly
create
here
a
classic
page,
what
is
it
it's
Vicki
Bates,
then
highly
confusing
options.
I
think
yes,
wiki
page.
B
If
it's
confusing
for
me,
it
might
be
confusing
for
mind
users
as
well.
Let's
not
actually
concentrate
on
that
now
insert
web
part
under
development.
It's
the
hello
there
web
part.
If
I
add
that
one
on
the
side,
we
can
see
that
it's
in
SharePoint
Online,
it
is
actually
rendered
in
the
padding,
is
there,
but
that's
because
of
a
slightly
different
styling
settings
and
and
the
sharepoint
online
is,
will
evolving
faster.
Then
the
sharepoint
2016.
So
that's,
maybe
something
to
be
aware
with
in
implement
and
your
development.
B
So
there
might
be
some
adjustments
to
be
done
there
yeah,
but
like
that
you
can
actually
fix
this
by
overriding
the
styles
and
do
the
styling
properly
in
the
back
part
as
well
good
I'm
not
going
to
do
anything
more
than
this,
so
I'm
not
gonna,
actually
make
a
wow
effect
on
the
web
part.
My
point
was
more
or
less
pinpoint
what's
available
in
the
SharePoint
2016
feature
back
to
classic.
B
Beige
is
modern,
wit
points
and
no
extensions
is
the
current
status
and
you
can
absolutely
use
the
same
SharePoint
framework
with
or
in
poll
sites,
which
is
pretty
cool.
So
the
same
implementation
works
on
both
sides.
There's
small
styling
differences
when
that's
being
done,
we'll
look
in
all
of
this
in
the
future
as
well.
Good
flipping
back
on
the
slides
and
I
need
to
I
need
to
actually
let
other
people
to
move
on
on
their
demos,
where's
the
content
and
that's
today's
presentation.
B
B
On
the
following
slide,
I
probably
had
a
quick
status,
so
obviously
gone
from
support
is
now
being
shipped
we're
working
on
multiple
things
based
on
the
feedback.
Two
weeks
ago,
I
have
removed
all
Dorian's
balls
from
the
slide
over,
so
we
shipped
a
lot
of
stuff
already.
This
is
the
latest
stuff
which
is
in
the
queue
and
which
people
know
that
it's
in
our
roadmap.
So
that's
the
whole
point.
We'll
have
a
lot
of
additional
things
obviously
announced
in
the
Ignite
pretty
soon,
but
that's
it
Patrick
as
the
host.
Let's
flip,
actually
it's
your
demo.
A
And
folks,
let
me
know
when
it
shows
up
got
it
got
it.
Okay,
great,
so
just
wanted
to
give
everybody
an
update
of
what
we're
doing
with
the
refactor.
So
it's
not
a
surprise,
try
and
get
some
information
out
there
ahead
of
people.
I
talked
about
this
a
little
bit
on
the
last
call,
but
did
a
lot
of
hand
waving,
because
I
hadn't
actually
done
much
work
on
it
yet,
but
now
I've
done
a
lot
of
work
on
it,
so
I
actually
have
some
stuff
to
share.
A
So
this
is
actually
in
the
new
repo
we're
looking
at
here
some
of
these
files.
They
still
get
cleaned
up,
go
away,
but
all
of
the
source
code
has
now
moved
under
this
packages.
Folder,
so
I
did
model
this.
After
with
the
angular
folks
and
a
lot
of
other
folks
out
there
have
done
it
seemed
like
a
good
way
to
do
it,
but
all
the
packages
will
be
in
a
single
repo
which
makes
it
a
lot
to
manage
debug
tests,
all
those
sorts
of
things.
A
But,
looking
through
these,
you
can
kind
of
see
the
package
names
are
a
little
bit
self-explanatory.
For
example,
common
graph-
you
can
kind
of
guess
what
these
things
do,
but
we've
got
a
lot
of
the
same
functionality
is
now
moved
to
these
different
packages
with
the
idea
being
you
could
take
these
packages
and
use,
for
example,
I
broke
logging
out
into
its
own
package.
So
if
you
wanted
to
use
our
lightweight
logging
framework
in
your
own
application,
but
nothing
else
we
do.
A
You
can
now
do
that
very
easily,
so
also
I've
written
a
little
build
system
to
help
manage
all
this.
We
are
moving
to
supporting
smaller
modules,
so
less
files
will
be
in
each
NPM
package,
making
them
a
little
bit
lighter
so
you're
not
going
to
get
all
of
the
the
compiled
j/s
you're
gonna
get
the
bundles
as
well
as
then
all
the
Taipings
to
support
your
intellisense
work,
but
you'll
get
smaller
bundle
sizes
and
you
can
see
as
it
goes
through
we're
gonna
process.
A
All
these
eventually
there'll
be
a
command
line,
so
you
could
just
build
or
package
a
single
project
as
opposed
to
all
of
these
at
once,
but
right
now
it's
doing
all
of
these
at
once.
So
this
is
sort
of
the
idea
of
I'm
gonna.
Do
a
release
so
I'm
gonna
have
a
command
that
will
run
through
all
the
packages
and
package
them
for
a
release,
so
I've
packaged
everything,
and
then,
if
sorry
I
should
have
done
this
before
the
call.
A
So
you
can
actually
see
now,
there's
gonna
be
produced
a
dist
folder
that
has
in
it
each
of
the
packages.
Then
each
of
the
packages
folders.
This
is
what's
actually
gonna
get
pushed
to
NPM.
So
looking
through
this
you're
gonna
have
a
couple
of
different
kinds
of
modules.
So
you're
gonna
have
a
UMD
module
in
es5
you're
gonna
have
an
es5
module,
not
wrapped,
so
just
in
es5
or
in
2015
es
2015
module
in
es5
target.
Sorry
it
can
get
a
little
wacky
and
then
you're
actually
also
gonna
get
in
s.
A
A
Now
it's
a
little
bit
more
broadly
supported,
so
we're
gonna
do
our
best
to
try
and
support
that
as
well
and
then,
of
course,
you'll
get
all
your
Taipings
files
in
here
to
support
that
sort
of
stuff
you'll
notice,
all
the
package.json
are
gonna
be
version
the
same,
so
all
of
these
packages
will
be
released
in
lockstep
and
there'll,
be
all
peer
dependencies.
So
everything
will
have
a
period
of
pendency
on
everything
else
at
the
same
level,
we're
working
on
how
best
to
install
that,
because
I
don't
want
you
to
have
to
type
in
p.m.
A
install
for
six
different
packages.
So
we'll
be
looking
at
that,
but
this
will
hopefully
give
folks
a
lot
more
flexibility
in
their
development
and
then
finally,
I
just
wanted
to
sort
of
show
this
get
used.
So
these
haven't
been
published
yet,
but
you
can
actually
do
the
install
from
a
file
which
is
the
same
kind
of
thing.
So
I've
installed
the
logging
package
and
I'm
also
going
to
install
the
SP
package
just
as
an
example,
but
these
will
work
just
directly
out
of
and
you
can
see
I'm
getting
complaints
about
some
peer
dependencies.
A
So
like
this
and
logger
does
all
the
things
you'd
expect
with
the
intellisense
and
the
comments,
but
you'll
also
be
able
to
do
something
that
I
think
is
a
little
more
exciting
than
just
logging,
which
is
bring
in
just
the
SP
functionality
that
you're
familiar
with.
So
if
you're,
using
just
SharePoint
functionality,
you'll
be
able
to
bring
that
in
and
use
it
without
a
lot
of
the
other
baggage,
for
example
graph
and
node
support.
A
So
we've
broken
all
the
node
related
classes,
I'm
gonna
break
out
a
lot
of
the
add-in
related
stuff
to
a
separate
package.
So
again
the
goal
is
to
kind
of
shrink
these
packages
as
much
as
we
can
I
will
see
how
far
we
can
take
that.
But
to
give
you
a
little
bit
of
an
idea
if
we
look
at
the
minified
SP
package
size,
you
know.
A
So
if
you
take
one
of
these,
we're
actually
still
really
big
right
now,
because
we
have
some
additional
stuff,
that's
coming
out,
so
haven't
made
a
ton
of
progress,
but
we
will
get
there
on
minifying
this
stuff.
So
the
idea
here
is
you'll
be
able
to
bring
in
these
packages
as
you
need
and
then
use
them
and
we're
sort
of
trying
to
take
more.
It's
been
a
year
since
we
kind
of
did
it
came
up
with
everything
and
then
we
will,
you
know,
have
to
then
go
through
these
other.
A
You
know
pieces
and
get
it
all
out
there
for
everybody
so
happy
to
take
questions
and,
like
I
said
this
isn't
out
yet
this
will
be
out
by
ignite
as
a
beta,
so
check
that
out
and
I'll
make
an
announcement
when
it's
out,
but
I
want
to
stop
and
give
plenty
of
time
now
for
whoever
was
next.
So
if
I
can
get
back
to
the
manage
content,
sure
this
I
think
Velan
was
first
yeah.
A
C
C
You
see
my
screen
now:
I've
got
it
yep:
okay,
nice,
hello,
everyone!
My
name
is
linger
gif
and
I'm
SharePoint
developer
since
the
early
days
of
SharePoint.
Excuse
me
if
I
speak
too
fast,
but
I
have
to
give
some
time
to
Chris
as
well.
So
today
we're
going
to
have
a
quick
look
at
communication
between
the
web
part
through
message,
broadcasting
or
utilizing
the
pub/sub
pattern.
I
won't
go
to
the
audio
up,
that
is
in
the
readme
file.
I've
specified
in
URL
very
good
URL,
where
within
the
Wikipedia,
and
you
can
have
a
look.
C
C
One
is
using
the
event:
aggregator
Appy,
that's
out
of
the
box
with
the
SharePoint
framework,
but
still
in
alpha,
so
don't
use
it
in
production
and
another
implementation
done
by
me
as
a
temporary
solution
to
be
used.
One
of
these
girls
life.
Okay.
Now,
let's
see
the
first
demo
there's
my
first
sample
here.
It's
called
reactive
end
aggregator
and
I
already
started
the
node.js
server
within
the
solution.
We
have
two
web
parts.
The
first
web
part
is
called
broadcaster.
C
C
C
The
fun
part
is
here
where
we
figure
the
event
aggregator
Appy
and
we
code
event,
aggregator
rice
event,
that's
the
event
name,
that's
a
full
action.
This
is
how
and
microsoft
recommends,
to
specify
the
event
followed
by
an
action
here,
and
then
there
is
my
data,
so
my
date
is
just
one
single
number
that
increases
with
every
hit
of
the
button-
nothing,
nothing
really
interesting.
Then
we
have
a
source
ID
and
target
ID.
For
now.
These
are
all
strings
with
not
enough
documentation
from
Microsoft,
but
this
is
still
in
alpha.
C
So
we
expect
a
bit
more
for
now
as
a
string,
you
can
place
the
name
of
your
web
part
or
some
kind
of
a
unique
identifier
here,
because
it
will
be
useful
when
we
catch
the
web
event
within
the
next
web
part.
So,
as
you
can
see,
this
comes
from
the
properties.
I'm
in
a
component
react
component,
and
this
comes
from
the
properties,
but
with
where
we
actually
create
an
instance
of
the
event
aggregator.
C
C
What
we
have
there
just
collapsed,
those
on
the
receiver
web
part
again,
a
very
simple
web
part
with
just
one
way
that
shows
that
I've
received
the
information
here
and
then
in
the
constructor
of
the
react
component.
We
again
have
the
event
aggregator,
but
then
we
have
subscribed
by
event
name.
That
is
my
event
name,
and
here
we
have
a
handler
method.
C
This
is
how
we
can
subscribe
for
events
and
once
the
event
is
broadcasted,
we
can
change
another
component
or
another
web
part
behavior.
Based
on
that-
and
there
is
my
handler
down
below
nothing
interesting,
I'm,
just
appending
another
failure
within
an
array
and
I'm
changing
the
state
of
the
reactants.
So
we
can
display
that
change.
C
C
For
my
colleagues,
because
actually,
miguel
repatha
from
spanish
point
found
that
we
have
a
functionality
of
out
of
the
box
there
and
myself
and
host
in
breath.
Line
from
primary
could
just
refactor
the
solution
a
bit.
So
it's
more
testable
and
while
Miguel
was
working
on
that
I
was
absolutely
convinced
that
we
still
don't
have
such
a
functionality
within
the
SharePoint
framework
and
I
decided
to
go
with
my
own
datian
of
Agape
and
that's
the
next
sample.
C
C
We'll
see
it
very
same
behavior
again
we
have
a
broadcaster
and
a
receiver
webparts
and
within
the
broadcaster
we
have
again
just
a
button
that
triggers
the
very
same
event.
It's
a
it
loads.
I
want
to
quickly
show
you
how
it
looks.
It's
not
that
different,
but
ok,
almost
there,
but
here,
as
you
can
see,
instead
of
a
vet
irrigator
within
that
method,
I
have
something
that's
called
event
emitter
and
instead
of
rice
event,
I
have
another
method,
that's
called
emit,
and
then
we
have
the
event
name
and
the
data
pretty
much
the
same.
C
The
only
difference
is
that
the
we
are
only
up
here
and
the
app
is
over
here.
I'll
go
briefly
through
the
app
here
in
a
minute,
once
we
have
the
new
sample
that
we
see
broadcaster
receiver.
The
only
difference
is
the
title
to
show
the
difference,
but
as
you
can
see,
it
transmits
the
messages
and
if
we
have
another
receiver,
both
web
parts
receive
the
messages
again.
C
C
Again
in
the
constructor
who
have
that
event
and
either
own
replaces
subscribe
by
name
from
the
previous
sample,
but
again
we
listen
for
that
vent
name
and
with
trigger
that
method.
Down
below
that
changes
the
state
now.
The
main
difference
here
is
that
the
implementation
we
only
implementation
and
the
app
is
here
as
a
separate
library,
and
if
you
go
here,
you
will
see
that
I'm
using
reactive
X.
Your
active
X
is
a
kind
of
popular
library
heavily
used
within
angular
2
and
own.
C
It
utilizes
the
observer
pattern,
but
because
we
have
the
subject
object
there,
we
can
easily
create
our
own
event
bus
and
behave
like
the
same
way
away
like
the
event
aggregator,
it's
single
Tom.
So
all
the
webparts
communicate
through
a
single
tone
here
and
I
need-
is
just
emits
or
broadcast
events
using
some
functionality
from
the
react
effects.
Library
own
again.
This
is
like
a
subscribe
for
for
event.
C
That's
pretty
much
from
my
side.
A
typical
case
is
in
SharePoint.
We
have
is
the
search
page.
If
I
just
go
and
it
you
will
see
multiple
webparts
here
and
they
communicate
through
events
and
message
broadcasting.
The
same
way
were
a
lot
like
we
saw
from
the
sample.
As
you
can
see,
the
search
box
is
one
way:
parser
navigation,
another
search
results
at
third
and
then
we
have
refinements
on
the
left,
if
I
just
top
anything
and
just
that
web
part,
it
will
communicate
with
the
rest
in
a
similar
fashion.
C
A
A
D
D
Right,
good,
okay,
alright,
so
I
wouldnt
talk
about
a
field
customizer
this
time,
so
the
basic
idea
of
field
customizers
you're
gonna
customize
the
display
of
a
field
in
a
list
view.
So
you
could
take
things
like
that
kind
of
ugly
percent
field
right
there
and
wow.
So
pretty
now
right
you
can
convert
that
do
all
sorts
kind
of
custom
display,
but
you
can
also
go
a
little
further
with
that,
which
is
what
I'm
going
to
show
you
today,
all
right,
so
just
kind
of
set
the
scene
to
talk
about
out-of-the-box
list
item
ordering.
D
So
there
is
an
internal
order
field
on
your
list
and
she
was
natively
by
orderable
list.
So
if
you
have
an
orderable
list
like
a
links
list,
for
example,
you're
gonna
see
in
the
view
right
above
sort,
you're
gonna
get
this
allow
users
to
order
items
in
this
view-
and
you
know
on
the
classic:
UI
you're
gonna
get
a
reorder
page,
which
you
can
launch
by
clicking
that
change
item
order,
button
up
in
the
ribbon
all
right
and
you
get
this
kind
of
kludgy,
but
it
hey.
D
It
works,
change,
item
order,
dialog
right
and
that's
fine,
but
again
that's
classic
UI.
Only
and
up
until
recently
things
like
the
links
list,
announcements
list,
weren't,
even
a
part
of
the
modern
list.
They
are
now
so
you're
kind
of
missing
some
of
that
functionality.
Now
the
other
side
of
that
is,
if
you
don't
have
an
orderable
list,
because
the
order
field
is
hidden
right.
D
Even
though
it's
on
all
your
list,
you
really
can't
take
advantage
of
the
UI,
and
so,
regardless
of
whatever
value
you
think
this
user
interface
has
it's
not
even
available
to
you
outside
of
these
types
of
lists.
So
that's
where
this
sample
comes
in.
So
this
is
the
item
order,
field
customizer
and
what
its
gonna
do
is
going
to
enable
the
reordering
of
list
items
to
drag
and
drop
directly
in
the
modern
ListView.
So
it's
this
sample
illustrates
several
things
like
loading
p.m.
D
PJs,
core
jQuery,
jQuery
yuan
from
CD
ins,
which
you
should
always
do
bundle
is
if
your
package,
it's
gonna,
take
advantage
of
that
order.
Field
right,
we're
gonna,
use
the
J's
core
magic
batching
to
get
all
that
stuff
going
now
we're
also
going
to
apply
some
CSS
animations
in
s
CSS,
which
isn't
totally
straightforward.
So
you
can
take
a
look
at
that.
We're
not
gonna!
Look
at
that
today,
but
it's
all
in
there.
D
The
sample
link
is
down
there
and
then,
finally,
because
we
are
doing
a
little
more
than
just
showing
a
custom
field-
are
actually
gonna
be
editing
some
list
items,
we
do
check
the
permission
level
and
disable
ourselves
if
we
don't
have
it
all
right.
So.
Finally,
if
you
want
this
to
work
on
your
list,
you
have
to
have
your
list
be
orderable
right.
So
if
your
list
is
already
or
double
right,
so
hey
you're
good
to
go
no
problem
stuff,
the
links
list
or
something
like
that,
no
problem,
the
other
thing
is
right.
D
So
if
you
just
have
a
custom
list
or
some
other
list,
you
can
take
advantage
of
that
order
field
right.
So
you
can
go
old-school
if
you
need
to
open
up
SharePoint
designer
of
your
views,
camel
and
change
the
you
know
the
order
by
element
there
to
use
that
internal
order,
field
or
I've
included
a
PowerShell
script
which
uses
the
PNP
powershell
commandlets,
and
you
can
just
pass
it
a
view
and
it'll
recreate
it,
and
it
does
exactly
do
in
SharePoint
designer,
but
you
don't
have
to
get
your
hands
dirty
with
that
thing.
D
Okay
and
then
kind
of
the
last
thing
you
can
do
is
you
can
provide
your
own
custom
ordering
field,
and
this
is
done
through
the
client-side
component
properties
and
we'll
take
a
look
at
that.
It's
really
simple,
but
basically,
if
you
provide
a
number
field,
we'll
use
that
instead,
all
right
and
finally
because
this
is
a
little
bit
different-
we've
got
for
the
demo,
one
called
a
placeholder
field,
so
you
can
use
this
with
any
field,
but
we're
gonna
take
over
the
display
with
an
icon
that
kind
of
indicates
status.
D
D
Okay,
so
here
is
a
classic
links
list,
so
this
is
an
audible
les.
So
I
could
say
you
know
like
Paul's.
Blog
really
belongs
on
top
I
can
just
drag
that,
bring
it
on
up
and
just
see
all
those
update
and
I
said.
No
actually
I
belong
on
top,
whatever
you
need
right.
So
the
idea
here
is,
you
can
quickly
just
drag
and
drop
and
sort
those,
and
if
we
take
a
look
over
here,
here's
an
example
where
we've
taken
a
classic
view
right.
D
So
this
is
a
classic
view,
a
modern
view,
but
this
is
a
classic
list.
That's
not
a
links
list,
but
we've
applied
that
view,
and
so
again
we
get
the
exact
same
thing
right.
So
we
couldn't
move
our
Muppets
around.
However,
we
need
to
okay.
The
last
thing
here
is
we'll
show
you
that
I've
got
a
custom
order
field
on
my
records
list.
Right,
I,
don't
want
to
use
the
order,
one
for
whatever
reason
you
know
meet
it's
an
old.
It's
an
old
list.
I've
had
for
a
long
time.
D
People
have
been
using
that
for
a
long
time
you
can
just
specify
that
and
I'll
show
you
up
here
in
the
debug
string
at
the
very
end
here,
I'm
specifying
this
client-side
component
properties.
You
see
I've
just
touched
my
order
field
and
I've,
given
it
the
internal
name
of
custom
order
pretty
complicated,
but
then
I
could
say
that
you
know
bodyguard
really
belongs
above
the
list
right
and
all
that
just
kind
of
works.
So
let's
take
a
look
very
quickly
at
the
code
for
that.
D
Okay,
so
here's
how
the
code
flow
kind
of
works
right.
So
again
we
load
all
three
of
those
from
CD
ends.
Very
straightforward:
you'll
need
the
types
for
both
the
jQuery
in
the
jQuery
UI.
Meanwhile,
you'll
install
the
SVP
and
PJs
package
as
a
dev
dependency,
alright
and
then
the
code
for
any
field
customized.
You
really
get
three
kind
of
methods:
/
right,
so
the
honor
net
on
Ritter
cell
and
on
dispose
cell
they're
pretty
explanatory
what
they
do
there
right
so
on
a
nip
we're
gonna.
D
What
we're
doing
here
is
we're
going
to
set
the
field
to
use
based
on
the
properties.
That's
just
a
single
line:
we're
just
gonna
check
those
component
component
side
properties
and
see
we
want
to
use
there
and
then.
Finally,
every
time
you
use
p.m.
PJs
core
inside
SharePoint
framework
solution,
you're
gonna
want
to
do
a
special,
an
it
that
just
sets
that
SPF
X
context.
It's
really
easy.
It's
just
cut
in
pay,
so
take
a
look
at
that
grab
that
so
on
render
cell
we're
doing
a
couple
of
things
there.
D
So
we're
gonna
set
that
icon
right
based
on
whether
you
have
edit
less
item
per
mission
or
not,
if
you
don't,
we
actually
kind
of
gray
out
the
icon
and
we
don't
enable
that
reordering,
otherwise,
we're
gonna
store
the
ID
and
the
order
value
kind
of
for
later
reference.
So
we
know
the
current
order
and
have
those
map
to
list
items
and
then
we're
going
to
kind
of
do
this
backwoods
thing
here
we
got
processing
a
rolling
timeout.
D
The
reason
I'm
doing
that
is
for
my
own
event,
which
is
on
cells,
rendered
just
real,
quick
that
on
disposed
cells,
where
you
would
do
things
like
if
you're
using
react,
you
would
unmount
your
components
right.
You
would
stop
your
event,
listeners
whatever
you
do,
they're,
not
really
using
that
in
this
code
here,
but
in
the
on
cells
render,
which
is
again
my
way
of
getting
an
event
when
all
the
cells
have
rendered.
D
That's,
where
I'm
actually
applying.
What's
called
the
sortable
out
of
the
jquery
UI,
which
enables
that
fancy
drag-and-drop
stuff,
I
didn't
have
to
do
much
for
that,
and
then
we
saved
initial
roller
and
at
that
point
we're
good
to
go.
People
could
start
doing
their
reordering
and
so
the
way
we
handle
that
is
a
non
order.
Change
and
all
we
do
is
we
see.
Are
there
actual
changes?
D
If
there
are,
we
call
Save,
Changes
and
then
Save
Changes,
all
we're
gonna
do
is
we're
gonna
make
sure
we
show
that
animated
loading
icon'
so
we're
just
gonna
swap
out
that
icon
a
little
bit
and
apply
a
couple
of
classes,
pretty
straightforward,
then
we're
gonna
do
some
magic,
we're
gonna
swap
around
the
order
values.
You
can
take
a
look
at
the
logic
of
that.
It's
actually
not
as
complicated
as
maybe
even
that
sounds,
but
the
really
cool
thing
is
because
we
know
we're
always
going
to
be
updating
at
least
two
items
all
right.
D
If
you
grab
an
item
at
the
very
bottom,
the
list
drag
it
all
over.
The
top.
You
could
be
potentially
updating
all
of
the
items
so
we're
taking
advantage
of.
Is
that
p.m.
PJs
core
batching?
Now
it's
super
powerful.
It's
really
easy.
You
just
create
a
batch
and
then
just
go
for
it.
We'll
just
ignore
my
meeting
there,
all
right,
I,
that's
it
so
we'll
take
a
look
very
very
quickly
at
the
code.
Now
you
can
see
here
up
and
on
a
knit.
This
is
where
this
is
all
the
work.
D
We
have
to
do
to
get
our
property
right
and
we
either
set
it
to
that
or
we
set
it
to
our
internal
order
field.
This
is
that
PNP
initialization
I
told
you
about
very
straightforward
down
here
in
our
render
cell
now.
This
is
that
rolling
timeout
right
here,
we're
kind
of
cancel
at
a
time
out
or
starting
a
timeout
again,
better
or
worse
right,
it's
working,
so
we
kind
of
track
things.
We're
gonna
set
those
icons.
This
is
pretty
straightforward.
Take
a
look
at
the
code.
Take
a
look
at
the
sample.
D
The
real
magic
happens
down
here
right.
This
is
where
we
set
that
sortable,
it's
a
single
call
and
we
just
provide
an
event
we
want
to
handle
when
things
move
around,
which
we
don't
do
down
here-
and
this
is
just
a
quick
comparison
to
see-
do
we
actually
change
anything
of
value
and
then
to
save
it?
This
is
the
real
power
of
jstor
comes
in.
We
don't
care
how
many
dirty
rows
there
are
right.
There
could
be
two.
There
could
be
30.
D
It
does
not
matter
to
us,
because
all
we're
gonna
do
is
we're
gonna
create
this
batch
right
here,
where
we
got
this
item
batch
very
straightforward,
just
go,
create
batch,
and
then
we
go
P
and
P
dot,
SP
that
we
have
that
list
and
we're
gonna
go
around
here
and
before
you
know,
we
update
this
guy.
We
just
call
in
batch
and
that's
all
you
need
to
do
to
get
all
that
kind
of
matched
up.
D
D
A
Great
stuff,
thanks
Chris,
thanks
Evelyn
for
two
fantastic
demos.
Today,
thanks
to
all
of
you
for
coming
Bama,
jump
briefly
back
to
the
slide.
So
we
have
the
next
meeting
date
in
the
recording
great
demos,
great
stuff,
today,
really
great
to
see
the
community
get
involved
and,
as
always,
if
you
guys
other
folks
out,
there
would
like
to
do
a
demo.
Please
just
get
in
touch
very
happy
to
facilitate
that.
Our
next
meeting
will
be
September
28th
look
forward
to
seeing
all
of
you
then,
on
the
call
thanks
very
much
have
a
good
day.