►
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
Hello
and
welcome
the
SharePoint
framework
and
JavaScript
special
interest
group
bi-weekly
meeting
is
February,
2nd
2017
were
already
into
February
of
this
new
year.
Vasa
thinks
it's
5:00
p.m.
he
is
so
confused
about
time.
He's
never
understood
it,
but
so
we
are
here
this
week.
We've
got
two
exciting
demos
coming
up
and
so
to
just
kind
of
get
going
for
those
folks
that
might
be
new
to
the
call
or
new
to
the
special
interest
group
or
patterns
and
practices
in
general.
So
just
to
talk
a
little
bit
about
what
we
do.
A
The
special
interest
group
was
formed
underneath
the
larger
SharePoint
patterns
and
practices
umbrella,
and
what
we
do
is
one
host.
These
bi-weekly
calls
to
talk
about
all
things:
client-side
development
and
SharePoint
framework,
as
well
as
to
provide
a
forum
for
demonstrations
and
folks
in
the
community
to
kind
of
learn
from
each
other
as
well
as
learn
from
us,
which
I
think
is
very
valuable
to
get
that
community
involvement
and
interaction.
A
And
then,
looking
at
each
week,
we
have
an
open
discussion
around
the
SharePoint
framework,
new
things
that
are
coming
out,
updates
on
release
timelines
and
things
like
that.
And
then
we
also
talk
about
the
JavaScript
core
component,
which
a
lot
of
folks
on
the
call
have
contributed
to
or
are
using,
which
is
fantastic
to
see.
So
we
like
to
do
an
update
about
that
on
this
call
as
well.
A
So
two
links
down
there
at
the
bottom,
aka
MSSP,
P
and
P
community
gets
you
to
the
Microsoft
tech
community,
which
is
sort
of
the
replacement
for
Yammer
and
then
dev
dot
office.
Comm,
slash
SharePoint.
Is
your
one-stop
shop
for
all
things,
SharePoint
development,
so
that's,
including
the
new
SharePoint
framework.
You've
got
a
ton
of
how-to
documentation.
How
to
get
started.
Make
your
first
SharePoint
framework
web
part
there,
but
as
well
the
add
in
development
and
classic
server-side
development
resources
can
be
found
there
as
well.
A
So
that's
really
the
one-stop
shop
for
all
SharePoint
development
Tim's
got
a
question.
Is
there
an
update
calendar
invite
for
2017?
Yes,
there
is,
and
I
can
get
you
that
link
I,
don't
have
it
right
in
front
of
me.
Maybe
it
up
there,
you
go
bases
got
it.
So
that's
the
updated
invite
for
anybody.
You
can
also
get
that
off
the
links
page
on
the
Wiki
for
the
JavaScript
core
library.
The
invite
link
is
there
as
well
so
moving
into
our
agenda
for
today,
we'll
get
from
vase
of
the
latest
updates
on
the
SharePoint
framework.
A
I'll
give
you
a
quick
rundown
on
some
updates
around
the
Jas
core,
but
most
exciting
this
week.
We've
got
two
great
demos,
one
from
Sergey
using
view
j/s
or
view
Jas
in
SharePoint
framework,
which
is
gonna,
be
really
cool
to
see
so
view
for
folks.
That
don't
know
is
another
sort
of
Dom
manipulation
framework
very
similar
to
react
in
a
lot
of
ways,
but
different
as
well,
so
very
cool.
So
it's
always
neat
to
see
different
approaches
as
things
that
come
out
and
then
Russell
has
got
a
react.
A
Video
library
web
part,
which
is
also
really
cool,
I'm,
excited
to
see
that
in
action,
I've
actually
written
myself,
a
video
library
management,
SharePoint
add-in,
which
was
available
in
the
SharePoint
store
for
a
while
and
was
the
least
sold
add-in
in
history
and
then
an
open
discussion.
Hopefully
at
the
end
for
folks
to
have
questions
and
ask
us
any
questions
they
might
have
so
I'll
turn
it
over
to
VAE.
So
for
updates
on
the
SharePoint
framework.
B
So
first
of
all,
Rolfe
actually
ask
a
quick
question
on
the
ion
window
related
on:
hey
is
the
shipment
framework
and
Elend
on
SharePoint
2013,
as
well
just
to
clarify
again
on
that
one
ship
and
framework
is
gonna,
be
first
released
pretty
soon
actually
to
SharePoint
Online,
so
we're
now
right
now
in
the
release
candidate
mode
for
SharePoint
Online
and
then
we're
looking
into
getting
that
shipped
on
a
SharePoint
2016
during
this
calendar
year.
So
it
will
be
part
of
this
feature
packs
at
some
point.
B
We
do
not
have
an
exit
timing
on
that
yet
because,
where
everybody
is
working
on
getting
the
SharePoint
Online
release
currently
available
a
few
notes
on
the
on
the
shipment
framework.
It's
a
progress
perspective.
If
you
go
to
the
after
of
the
consular
SharePoint,
which
is
the
new
SharePoint
development
landing
page,
which
will
replace
also
MSDN,
because
we
will
actually
create
a
shutdown
MSDN
during
this
calendar
year.
We're
related
on
on
SharePoint.
Well,
it's
a
longer
story.
B
We
are
moving
to
go
strut,
my
stuff,
that
comes
the
SharePoint,
so
there
will
be
some
URL
changes
in
the
future,
but
ended
after
that
comes
a
SharePoint.
A
few
go
sharpen
framework
web
fonts
and
guidance.
There
are
four
new
articles.
Three
of
them
actually
went
live
five
minutes
ago
or
actually
ten
minutes
ago,
so
there's
a
a
guidance
related
on
localization
of
a
client-side
web
part.
So
how
do
you
do
localization
with
the
release
candidate
version
sharing
data
cross
client-side
web
parts?
B
Super
super
important,
actually
guidance,
and
this
relates
on
the
let's
say,
classic
challenge
with
add-ins
or
JavaScript
customizations
in
SharePoint
in
general,
which
is
that
hey
I
have
multiple
widgets
or
functionalities.
In
my
welcome
page
in
my
poor
old
front
page,
all
of
them
require,
for
example,
accessing
user
profile
data
or
taxonomy
data.
How
do
I
make
sure
that
only
what
I'm
loading
that
data
once
across
all
of
my
papers
or
widgets
or
JavaScript,
and
that
guidance
is
addressing
that
particular
topic?
B
There's
multiple
different
options
to
choose
from,
and
it's
explaining
how
to
implement
that
with
client-side
web
parts.
So
if
you
do
have,
as
an
example,
I
think
the
scenario
for
that
one
which
we
are
using
in
the
guidance
is
that
you
are
loading
recent
documents
from
the
from
the
office
graph
and
you
don't
actually
want
to
load
that
multiple
times.
B
If
you
have
two
different
webparts
with
a
slightly
different
presentation
on
the
same
page,
you
only
want
to
load
that
the
information
once
for
both
webparts
and
that
particular
thing
is
very
founder,
sharepoint
framework
enterprise
guidance
again
out
as
well.
So
that's
a
relatively
long
article
explaining
what
does
it
mean
from
a
enterprise
architecture
and
development
perspective
and
then
another
article
related
on
SharePoint
team
development.
So
explaining?
What
does
it
mean?
B
What
is
the
Constitution's
from
a
conceptual
perspective,
both
the
enterprise
guidance
and
the
team
guidance
are
more,
let's
say,
formats
explaining
things
from
a
conceptual
perspective:
they're
not
really
hands-on,
explaining
how
to
visual
studio
or,
let's
say
TFS,
which
integrate
with
SPF
X.
That's
still
on
the
cure,
in
our
long-lasting
view
of
articles
and
guidance
which
are
coming
out.
B
Huge
so
few
I
a
few
items,
we
have
actually
updated
our
existing
shape,
one
framework
reference
documentation,
so
the
reference
API
documentation
is
available
in
the
dev
tourists
come
slash,
SharePoint
as
well.
Easiest
URL
to
remember
is
they
came
as
SPFs
reference,
and
this
is
where
we
have
all
of
the
guidance
related
on
code
objects,
classes
and
everything
else.
B
This
is
generated
directly
from
code
and
we're
looking
into
actually
even
including
code
samples
and
all
of
that
in
here,
as
well
few
things
kind
of
a
summary
slide
on
what
has
happened
recently
related
on
SharePoint
framework.
So
the
release
candidate
came
out
early
January,
the
written,
video
and
tutorials
have
been
updated
to
release
candidate
level,
and
you
can
find
YouTube
recordings
of
the
written
format
tutorials,
which
are
available
in
the
deaf.
B
B
Sample
updates
are
ongoing,
so
we
are
working
into
updating
existing
samples
to
the
release
candidate
level
first
and
then
do
the
cheer
level
relatively
soon
as
well.
Getting
started
with
SharePoint
framework
training
package
is
getting
closer
and
that
was
actually
exactly
the
same
status
two
weeks
ago.
Now
it's
pretty
much
ready.
B
It's
just
waiting
for
me
to
have
some
time
to
push
it
out
in
the
github
in
the
training,
github
repo,
so
I
need
to
do
some
modifications
and
done
on
that
one
where
we
will
release
labs
presentations
and
initial
structures
for
this
training
package
and
I
will
show
you
what's
included
in
that
one
in
following
slide
and
then
the
video
recordings
of
that
one
will
be
released
after
GA.
The
GA
will
happen
in
flag
mentioned
through
relatively
soon,
but
I
can
cannot
give
you
that
date.
B
You
can
play
an
accident,
because
I
would
compromise
my
career,
huge,
more
samples
under
the
shipment
github
organization,
and
there
are
fewer
requests
already
pending
on
existing
samples
which
the
the
persons
who
have
contributed.
The
samples
have
upgraded
that
those
to
release
candidate
levels
I
do
apologize
on
a
small
delay
on
this
one.
It's
just
a
matter
of
getting
the
probe
request
processed
and
we
can
actually
get
adopt
its
included
now
I
mentioned
to
getting
started
with
chip
and
framework.
B
This
is
actually
super
super
interesting
and
super
super
powerful
package,
because
this
is
really
hundreds
of
slides
and
tens
of
laps
related
on
SharePoint
framework,
and
this
is
something
what
we
will
keep
on
evolving
after
the
initial
release
as
well.
So
right
now
the
labs
have
been
tested
and
upgraded
to
release
candidate
level,
and
this
is
the
time
when
we
will
push
them
out.
We
will
also
work
on
updating
them
to
the
cheer
level.
B
When
the
GA
is
available,
we
have
eight
vicar
modules,
which
are
split
splits
to
a
more
smaller
sections
and
really
the
idea
of
this
one
is
that
we
have
kind
of
eight
specific
areas
and
there.
Those
are
then
split
to
a
smaller
sections
which
are
individual
presentations
and
individual
videos.
This
way,
one
module
is
not
one
and
a
half
hours
and
some
parish
recording
that
video.
It
will
be
rather
ten
to
fifteen
minutes
and
you
can
more
easily
find
what's
relevant
for
you.
B
B
B
B
This
is
getting
started
with
SharePoint
frameworks,
so,
if
you're
deep
into
the
SharePoint
framework
already,
this
might
not
actually
get
you
a
humongous
amount
of
new
stuff,
but
we
need
to
start
obviously
with
getting
started
and
then,
when
the
killing
started
is
out,
there
will
be
an
additional
deep
dive,
training
packages
or
material
for
people
to
use
as
much
as
they
want
later
on.
Unlike
mentioned
you,
don't
not,
you
do
not
need
to
ask
any
permissions.
This
is
shared
for
the
purpose
of
anybody
to
consume
slides.
B
And
yes,
the
training
package
is
not
yet
available,
just
making
sure
that
everybody
actually
gets
this.
So
this
is
spending
the
go
live
in
matter
of
days.
It
is
spending
to
go,
live
for
the
safe.
That
I
need
to
have
some
time
to
write
some
MD
files
and
get
the
presentation
book
published
in
a
github
and
after
that,
we're
good
to
go
some
presentations
and
that's
response.
B
It's
actually
a
good
point,
a
fair
comment
from
Nigel.
It
says
that
it
should
be
out
in
January
2017
and
is
it
is
actually
2nd
of
February,
so
it
is
gonna.
Go
live
in
a
matter
of
days
anyway,
so
I
can
update
the
slide
if
that's
needed.
Well,
let
me
do
this.
Let's
actually
make
sure
that
somebody
is
watching
this
afterwards.
Let's
fix
that
one
live
with
my
mouse,
which
is
pretty
hard.
20
70
never
get
fixed.
B
Well,
this
is
exactly
the
same
stuff.
So
if
you
go
to
the
the
what
you're
getting
from
here
is
a
search
tool
which
is
giving
you
what
are
the
samples
available
from
a
key
table.
So
this
is
just
the
easier
way
to
filter
what
are
the
samples
available
in
the
key
table
rather
than
going
to
the
kitchen
after
you
to
choose
the
model,
you
can
absolutely
go
that
the
key
top
and
pull
them
down,
and
that's
it.
B
Yes,
exactly
exactly
the
point
huge
moving
on
on
things
is
probably
time
to
have
the
same
question.
What
we
had
last
time,
no
we're
closing
into
the
TA
and
yes,
we're
working
on
updating
a
sample
for
working
updating
documents.
We
have
the
the
reference
API
documentation.
We
actually
even
got
some
of
the
old
tourist
documentation
from
MSD
and
included
injectors.
B
That
comes
last
lash
upon
the
full-fledged
REST
API
reference,
that's
actually
in
the
works
as
well,
because
obviously
the
the
REST
API
is
relatively
important
for
SharePoint
framework,
so
we're
working
on
getting
that
as
a
high
priority
thing
verifying.
There
are
some
unfortunate
delays
on
that
one.
Do
numerius
in
general
Microsoft
challenges
which
I'm
not
going
to
go
into.
B
B
Anything
else
what
we
need,
there's
a
question
related
on
SPF
X:
can
videos
power-ups
or
flow
as
a
developer
Bo,
not
precisely?
No,
they
don't
quite
integrate.
Well,
there's
certain
scenarios
where
you
might
actually
theoretically
integrate
them,
but
that's
not
really
the
mission
of
the
things
easy
commanding
plans
for
streak,
shrink-wrap
the
NPM
packages
from
MSFT
dev
tools,
which
is
a
fair
comment.
B
This
relates
on
the
on
the
challenge
of
the
versions
versioning,
and
how
do
we
make
sure
that
whenever
we
are
pushing
updates
on
the
NPM
packages,
the
existing
customizations,
then
client,
lightweight
ones
which
you
have
developed
will
still
work
properly
and
that's
absolutely
absolutely
on
our
site
to
get
still
clarified
for
TGA
and
the
load
debates
wasn't
that
successful
for
our
site?
Yes,
it
was
super
connor.
Well,
technically,
it
wasn't
back
on
our
side,
it
back
on
typescript,
which
was
pretty
horrible.
B
This
almost
seems
like
at
the
classic
story,
and
I
have
to
do
this.
Teacher
old-school,
SharePoint
people
do
remember
that
everybody
was
always
complaining
that
she
appointed
super
stewardship
when
the
super
stroke
actually
quite
often,
and
the
problem
was
that
it
was
sequel
server,
but
Stephen
had
sufficient
amount
of
iOS.
B
But
that's
OH
debate
essentially
cute,
but
let's,
let's
say
that
we
can
okay,
the
version
you
think.
No
doubt
we
need
to
get
it
clarified.
We
need
to
understand
how
do
we
make
sure
that
your
stuff
doesn't
break
whenever
we
are
submitting
new
stuff
in
a
SharePoint
Online
on
new
versions
of
the
packages?
What
else
need
it
GA
tomorrow?
If
that
would
be
true,
it's
not
true,
but
what
would
they
need
it
after
that?
B
C
I
I'm,
taking
that
from
what
she
said
earlier
that
there's
not
going
to
be
another
release
candidate
before
we
go
GA,
it
sounds
like
J's
are
closer
than
that.
So
my
questions
about,
like
once
we
hit
GA
I,
know
that
there's
a
support
stance
that
Microsoft
has
to
abide
by
price
that
doesn't
really
apply
to
things
that
are
pre
GA
with
RC
and
their
previews.
So
can
you
comment
on
the
frequency
that
you
guys
are
gonna
have
with
refreshes
post
GA?
C
The
reason
I'm
asking
is
just
because
it
seems
like,
from
my
experience,
supportive
see
from
other
people's
that
there
been.
There
were
a
bunch
of
regressions
that
hit
due
to
the
did
a
bunch
of
refactorings
with
our
c0,
and
so
I
was
I
person
was
expecting
another
release
candidate
and
just
want
to
know
where
what
your
stance
is
going
forward.
Past
GA.
B
And
that's:
why
that's
why
we
have
this
course
so,
right
now
we
don't
have
an
official
statements
on
on
that
one.
So,
but
but
it
seems
to
be
that
we
will
go
live
without
a
second
release
candidate,
so
we
are
getting
pretty
close
on
the
GA
and
I
can't
give
you
an
official
statement
related
on
how
do
we
avoid
all
of
these
things
in
the
future,
and
I
wouldn't
want
to
speculate
on
that
particular
thing,
because
it's
super
super
important
thing
to
solve
as
well.
B
B
Nigel
is
asked
commenting,
so
we
could
have
another
load
death
situation.
Well
now,
let's
be
clear
around
the
load,
this
is
say
a
issue
which
is
reported
I,
can't
it's
like
346
or
whatever
issue
in
the
dev
Docs
repo,
pretty
close,
probably
if
I
remember
the
number
correctly,
but
the
load
s
issue
was
related
on
somebody
missing
up
things
in
the
pipe
script
and
that's
a
problematic
thing,
obviously,
because
we're
building
stuff
on
top
of
the
typescript
technically
it
would
be
the
same
thing
as
within
the
old
c-sharp
development.
B
Somebody
would
be
doing
a
breaking
chains
in
a
dotnet,
4.0
or
4
points
whatever.
And
yes,
it's
super
unfortunate
situation
and
we
need
to
get
all
of
that
in
a
better
reader
level,
as
Microsoft
and
I
can't
actually
I
work
for
Microsoft,
so
I
shouldn't
be
saying:
yeah,
it's
not
my
fault,
it's
the
other
things
fault.
No,
it's
my
first
fault.
We
do
get
that,
but
it
is
a
challenging
thing
to
fix
as
well
and
yes,
the
shrink-wrap
absolutely
will
fix
that,
because
shrink-wrapping
means
that
you
are
essentially
setting
up
your
solution.
B
And
well,
there's
there's
a
discussion
going
on
on
SharePoint
final
16.
Yes,
it
will
come
on
ship
on
channel
16
later
on
this
year.
We
do
not
have
an
exact
timing
on
getting
the
ship
on
framework
on
ship
on
2016.
Now
the
web
pack
is
completely
different
thing.
Web
book
is
essentially
tooling
to
do
modern
web
stack
development.
You
can
actually
use
webpack
in
SharePoint,
2001
technically
or
you
can
build
your
chava
script
using
a
backpack
or
use
the
web
pack
in
the
JavaScript
development
and
use
those
in
SharePoint
2001.
B
Is
there
a
roadmap
of
being
able
to
create
for-profit
web
parts
pages
that
includes
license
checking
and
trial
subscription
et
Cie?
So
essentially,
question
is:
do
we
have
a
store
plan
for
client-side
web
parts
and
SharePoint
favorite
reports?
We
do
have
a
plan
and
we
are
actually
working
on
the
on
the
full
store
story
for
SharePoint
framework
client-side
webparts,
another
SharePoint
framework
customizations
as
well,
because
client-side
web
parts
is
just
the
first
component
in
SharePoint
framework.
We
will
release
additional
customization
endpoints
as
well.
C
A
Really
appreciate
everybody's
questions.
It's
it's
fantastic
feedback.
It
really
helps
us
grow
and
become
better,
but
do
want
to
make
sure
we've
got
time
for
the
demos
and
then
likely
we'll
have
a
little
bit
more
time
at
the
end.
To
continue
this
great
conversation,
so
I'm
just
gonna
move
forward
a
little
bit
with
the
slides
so.
A
A
quick
update
on
the
Jas
core
stuff
before
we
get
into
the
demos.
Thank
you,
of
course
everybody.
That's
contributed,
really
appreciate.
It
got
some
great
feedback,
as
always,
since
the
2.0
release
so
really
great
to
see.
Thank
you,
everybody.
So
quick
updates
for
2.0
that
is
out
as
of
Monday,
so
we're
seeing
a
rapid
uptake
in
the
metrics
thanks
to
everybody,
who's
been
engaged
with
that
and
they
started
using
that
in
their
projects.
We're
now
in
339
tenants
and
we're
servicing
5.9
million
requests
in
January.
A
That's
a
doubling
of
the
number
in
December
and
then
we've
also
got
some
updated
wiki
articles.
So
you
can
check
out
there's
now
a
developer
guide
link,
so
we're
working
very
hard
to
add
articles
on
how
to
do
all
the
specific
actions
with
the
core
library.
That's
been
an
asked
for
a
long
time
as
a
little
bit
clearer
guidance.
So
we've
tried
to
listen
to
that
and
are
working
on
improving
those
articles
almost
every
day.
A
So
my
ask
of
you
is
try
out
2.0
and
let
us
know
your
feedback,
we've
gotten
some
great
feedback
and
always
appreciate
more
one
thing.
I
did
want
to
mention
is
we're
gonna,
try
and
move
to
monthly
releases
in
line
with
the
other
patterns
and
practices
library
releases,
so
the
see
psalm
library
that'll
be
smaller,
updates,
typically,
but
more
frequent
releases,
so
monthly
cadence,
but
we
do
not
at
this
time
anticipate
any
more
breaking
changes
so
obviously
going
from
one
dot
whatever
to
two
dot.
O
was
a
breaking
change,
but
we
shouldn't
have
any
big.
A
You
know
big
changes.
You
know
moving
forward,
so
opportunities
to
participate.
Demo,
a
SharePoint
framework
web
part
demo,
the
core
library
contribute
on
github
or
provide
feedback
through
any
of
those
avenues
are
always
requested.
So
do
encourage
that
and
then
great
so
we've
gotten
to
the
demos.
Okay,.
D
Thank
you
at
the
beginning
may
be
a
few
words
about
you
because,
like
patrick
said,
may
be
a
lot
of
everybody
knows
what
is
you
and
what
I'm
going
to
talk
about
the
future?
The
communication
says
that
use
the
progressive
framework
for
building
user
interfaces
and,
in
that
sense,
it's
similar
to
other
frameworks
or
libraries
like
knock
out
etcetera,
and
you
would
say
why
you
and
from
what
I
see
and
from
from
what
I
learned
in
a
few
weeks.
I
can
say
that
view
is
fast.
It's
much
much
easy
to
learn.
D
It
has
very
clear
and
straightforward
documentation.
You
can
start
using
also
it
can
be
easily
integrated
with
any
third
party
companions
or
framework.
Like
is
perfect,
for
example,
and
we
will
see
that
within
minutes,
don't
you
have
exact
answer
on
this
question?
Why
do
I
think
you
need
to
try
it
yourself
and
compare
it
with
other
libraries?
You
are
using.
It
have
your
own
opinion,
whose
aesthetic.
D
D
D
D
D
First
of
all,
I
want
to
say
that
I'm
using
here
something
it
is
called
individual
mineralogy.
It's
called
as
Negro
file
components.
What
is
single
file
company?
It's
a
file.
It
is
not
view
extension
and
this.
This
file
contains
everything
you
need
in
order
to
run
small
piece
of
the
web
component.
You
see
that
there
is
a
HTML
template.
Also,
there
is
a
script
tag,
contains
your
logic
for
your
component
and
also
styling.
D
D
D
You
see
I'm
using
a
sum
to
the
characters
which
are
officially
supported
by
the
this
companion
secretly,
this
property
to
character.
There
are
two
methods.
Yet
to
do
and
complete
it
completed
is
actually
it
went
erased
when
you
click
on
check
box
and
you
are
effectively
marking
to
do
is
completed.
Also,
you
see
that
I
am
importing
this
interest
in
Lion
important.
My
to-do
item,
good
new
file
and
this
lion
registers
to-do
item
as
gel
companion
for
my
route
to
do
component.
We
can
also
take
a
look
at
to-do
item.
D
Well,
when
you
click
on
check
box,
there
is
around
just
completed
around
which
is
picked
up
by
our
parent
to
do
the
tears
component
and
right
after
that
he
ought
to
write
them.
Consider
it
as
completed
that's
our
two
components
and
if
you
take
a
look
at
the
to
do
a
part,
you
see
that
in
order
to
drop
our
web
part,
we
need
to
import
view
and
we
need
to
import
our
route
to
do
component
and
inside
our
method.
We
need
this
little
wire.
D
D
D
For
example,
I
don't
want
the
client
to
copy
the
model,
dot
CSS
files
this.
Why
I
found
this
this
little
trick
in
order
to
not
to
copy
these
files,
because
actually
all
styles
you'll
be
will
be
compiled
by
a
view
loader.
He
sees
it
as
this
configurable
Park
task.
He
suggested
to
build
this
additional
configuration,
and
this
additional
configuration
adds
special
reload,
which
is
responsible
for
lodging
hours
and
go
file,
components
and
parsing.
These
templates,
these
scripts
and
these
Styles
in
four
separate
modern
modules.
D
I'm
also
one
little
notification
here
we
need
to.
We
need
to
quote
the
harm
good
view
and
dot.
C
has
assessed
files
into
the
out
the
folder
into
the
loop
by
default
copy
static
assets
task
dozen
corpuses
files.
This
way,
even
it
also
makes
this
little
adjustment
in
order
to
go
beyond
these
extensions
into
the
output.
D
A
D
My
sample
is
available
and
the
samples
as
basic
samples,
repository
and
I
think
they
are
responding.
Yeah
right
and
the
question
about
separate
HTML
CSS
right.
It
is
possible
to
split
between
separate
HTML
and
CSS
files,
but
in
that
way
you
need
to
to
do
a
little
bit
different
syntax.
For
example,
you
need
to
specify
template
and
then
you
can
use
string
key
or
you
can
use,
require
yours
to
my
file
etc
for
benefits.
I
can
recommend
you
to
read.
D
A
E
The
current
web
parts
that
are
available
off
out
of
the
box
only
allow
you
to
present
one
video
at
a
time
and
we
wanted
to
kind
of
have
a
library
of
videos
that
users
can
view
so
I've
created
it
on
office,
365
channel
here
and
I've
uploaded
some
sample
videos
to
it
and
I've
created
a
demo
site
to
show
this
there's
actually
three
different
webparts
that
I
messed
around
with
or
three
different
libraries
react.
3D
carousel
reacts
lick
and
react
Cover
Flow.
Those
are
different.
E
Carousel
components
that
you
can
use
with
react
I
had
to
try
them
all
to
try
and
figure
out
which
works
best.
But
the
idea
is
that
I
call
into
the
office
365
video
service
to
get
a
list
of
all
the
videos
in
the
channel.
I
display
an
image,
the
thumbnail
image
for
the
video
and
then
when
the
user
clicks
on
it,
I
will
go
ahead
and
switch
it
to
an
iframe
to
show
the
video.
So
the
first
component
is
the
react:
3d
carousel.
E
It's
going
to
take
them
into
load
here,
so
this
is
a
3d
carousel.
It's
displaying
the
thumbnail
images
of
all
the
videos
that
were
in
our
library
in
the
office,
365
video
Channel
and
this
one
worked
well,
but
there's
no
way
that
I
can
switch
it
to
an
iframe,
because
the
component
doesn't
allow
me
to
switch
from
the
static
image
to
an
iframe.
So
I
gave
up
on
that.
One
I
moved
over
to
the
react
slick,
carousel
library
with
these
are
all
all
NPM
packages,
so
the
react
slick
library
worked
well.
E
I
can
toggle
around
between
the
different
videos
and
when
I
click
on
one
of
the
videos
it'll
actually
begin
to
play.
The
the
image
tag
was
replaced
with
an
iframe
and
the
video
started.
Well,
it
should
have
started
I'm,
not
sure
what
happened
there.
I
had
some
issues
with
the
CSS
on
this
one
and
I
didn't
like
the
layout,
so
I
moved
to
the
final
one,
which
was
the
react:
Cover
Flow,
carousel
library.
E
And
this
one
it's
kind
of
a
nice
library
it
supports
scrolling
with
the
mouse
wheel.
So
if
I
just
scroll
my
mouse
wheel,
I
can
go
to
the
different
videos
and
again,
if
I
click
on
any
one
of
the
videos,
the
image
tag
is
replaced
with
an
iframe
and
the
video
begins
to
play
so
I've
added
a
lot
of
controls
to
this
one.
If
I
go
out
at
this
page,
I've
made
this
one
highly
configurable,
the
other
ones
all
have
hard-coded
values.
E
But
if
I
come
in
to
edit
the
web
part
I
can
change
the
of
the
controls,
the
various
components
in
it
and
generally
make
a
mess
of
things
if
I
want
to.
But
that's
a
demo.
Let
me
switch
over
to
the
code
here.
So
there's
three
different
webparts
in
the
library,
but
the
first
created
utility
class
just
to
talk
to
the
office
365
video
service.
E
E
Then
I've
got
another
message
to
call
get
all
the
channels
for
the
tenant
and
a
final
method
to
get
all
the
videos
within
a
channel.
So
this
library
is
used
by
all
the
different
webpart
components,
so
I'm
going
to
switch
to
one
of
the
components
that
I
have
here.
I'll
just
go
they're
all
pretty
much
the
same,
so
I'm
just
going
to
go
over
the
Cover
Flow
one
and
if
I
open
that
web
part
you
see
in
the
constructor
I
go
create
one
of
those
office.
E
365
video
components,
I
just
create
a
new
object
on
that
which
will
connect
to
office
365
video
and
get
all
the
metadata
associated
with
the
tenants
video
channel
and
then
in
the
render
method.
I
just
pass
that
down
somewhere
in
here,
yeah
I
pass
that
down
to
the
component.
That's
going
to
go
ahead
and
display
the
videos-
and
in
this
case
that
component
is
the
video
library,
coverflow.
E
E
E
And
then,
if
I
move
over
here,
you'll
notice
that
I've
captured
the
video
number
on
a
data
tag
and
when
the
user
clicks
on
the
video,
it's
going
to
call
the
play
video
method,
and
so
up
here
in
play.
Video
we're
going
to
set
the
selected
video
to
the
video
number
that
he
clicked
on
set
the
state
so
that
the
state
will
represent
the
new
selected
video
and
then
back
in
the
render
method.
C
A
A
All
right,
let's
switch
back
to
the
slides
here,
so
Thank
You,
CJ,
Thank,
You
Russell.
Both
you
guys
awesome
demos
really
appreciate
it.
A
reminder
for
anybody
who
would
like
to
do
a
demo
like
this
on
the
call,
please
let
myself
or
vaisseau,
know
and
we'll
make
sure
to
get
you
on
the
schedule.
We're
always
really
excited
to
see
what
the
community
comes
up
with
I.
Think
it's
really
great
to
see
the
different
approaches.
Different
libraries,
for
example,
view
J
s
is
something
I
personally
haven't
gotten
to
use.
A
Much,
that's
really
cool
to
see
it
and
I
know
I'm
gonna
go
learn
a
little
bit
more
about
it
after
this
call,
and
then
thanks
to
everybody
for
the
interest
there,
so
we
do
have
a
little
bit
more
time,
so
we
can
reopen
the
the
open
discussion.
So
are
there
other
other
questions
we
didn't
get
to
previously
or
that
folks
have
come
up
with
sense?
The
other
discussion
either
around
the
demos
or
around
the
SharePoint
framework.
A
A
I
haven't
heard
anything
about
that:
okay.
Well,
in
that
case,
we'll
move
to
close
out.
So
our
next
meeting
is
gonna,
be
February
16th,
look
forward
to
seeing
everybody
there
again
if
you'd
like
to
you
know,
do
a
demo
or
something
on
these
calls.
Please
do.
Let
us
know,
would
love
to
have
you
on
the
agenda
and
get
you
involved.
I
think
it's
really
valuable
for
for
all
of
us
to
see
what
the
community
is
doing
and
learning
from
each
other.
So
thank
you.
Everybody
appreciate
everybody
joining
the
call.
A
B
B
Good
question?
Actually
right
now
the
modern
web
parts
are
only
available
in
the
in
the
modern
pages
because
they're
using
well,
they
don't
have
a
dependence,
then
kind
of
us,
but
still
I'm,
not
sure
I
can
actually
double
check
from
the
guys
who
are
responsible
as
web
parts,
but
good
question.
Actually
I
haven't
even
thought
about
that.
One
cool.