►
From YouTube: Magento PWA Demo, 22 October 2018 (Sprint 27)
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
This
is,
this
is
Eric
and
they
have
folks
in
Austin.
How
is
everybody
doing
good.
A
E
D
A
G
H
A
A
A
So
it
looks
like
we've
got
a
full
house
from
barbarian
and
fight
which
is
fantastic
and
so
a
lot
of
recent
progress,
some
of
which
you've
probably
seen
in
slacks
but
for
those
who
have
not
I
kept
up
with
that
you'll
get
a
peek
at
some
of
the
work
on
the
product
options,
product
details
and
I.
Think
one
item
that
didn't
didn't
make
it
two
weeks
ago,
which
is
the
editable
cart
for
that
one.
A
So
it
looks
like
that
one's
up
and
running
on
their
servers
and
then
I
did
leave
some
time
for
Artem
on
on
on
the
product.
Slider
slider
I,
don't
know
if
that's
ready
to
show
but
I
put
that
in
there.
If
we
have
time
always
would
love
to
see
some
in
progress
work
on
that,
though,
so,
let's
the
line
up
for
line
up
for
today.
Yes,
any
questions
or
comments
before
we
get
going
nope
all
good,
all
right.
Let's
do
this
James,
let's
get
a
started
with
some
documentation.
All
sharing.
E
H
There's
some
sort
of
confusion
a
little
bit
about
what
our
classifier
component
does
and
knowing
that
with
with
Jimmy
stiletto
medical
weeds
that
we
got
somebody
addressing
our
CSS
architecture,
really
talking
about
in
detail
is
very,
very
heartwarming.
For
me,
you
have
a
great
relief.
Thank
you
very
much
very
good.
A
And
it's
also
a
good
story
for
the
question
that
we
often
get
again.
You
guys
are
often,
but
on
the
outside.
The
kind
of
assassin
left
question
right.
We
are
moving
forward
the
CSS
modules.
Yes,
this
is
a
big
part
of
that
and
this
gets
into
a
little
bit
more
detail
on
our
perspective
on
things
so
yeah.
Thank
you.
Thank
you
Martin
for
this
one
and
thank
you
for
James
Burke
for
taking
a
look
at
this
and
in
review
and.
J
J
J
A
This
was
great
stuff.
We've
had
this
pipeline
for
a
bit
and
a
lot
of
it
obviously
coming
by
way
of
some
of
the
some
of
the
recent
architectural
changes
from
James
and
the
outboard
work.
So
as
more
and
more
folks
join
us
both
internally
and
externally.
These
are
huge
right.
That's
why
we've
really
been
busy
in
this
area,
and
we
think
this
will
be
a
big
win
and,
but
you
know,
give
us
feedback
on
it.
Let
us
know
what
you
know:
some
PRS
we
keep
getting
in
them.
We
keep
taking
a
look
at
them.
A
H
Still
evolving
towards
youthfulness
in
a
way
like
I'll,
be
frank
about
that
right
now.
What
it
helps
us
to
do
is
listen,
fondly
really
simple:
HTML
box,
metadata,
cetera,
I,
look
I'm
interested
in,
for
instance,
having
a
build
time
step
that
creates
a
fake.
A
mock
date
of
a
graph
jill
has
mustaches
in
it
can
auto
generate
an
app
shell.
They
stop
nothing,
go
vendor
of
react
or
something
like
that
tear
my
fam
is
here
on
the
call
she's,
not
old.
He
has
an
idea
for
schema
stitching
as
an
upward
feature,
which
is
extraordinary.
H
I
really
I've
been
wanting
that
and
I
come
to
my
attention
that
our
edges
are
gigantic
and
that
there's
no
API
for
using
magentas
image
resolution
and
resizing.
So
maybe
upwards
should
do
something
like
that.
It's
hard
to
know
what
it
scope
is
sometimes,
but
it's
what's
got
you
know,
I
mean
it's
for
pou
a
PWA
is
neat
images.
Maybe
it
should
have
an
image
resolver
that
can
proxy
and
modify
images
that.
A
C
Right,
ok,
so,
after
looking
at
some
of
the
existing
models
out
there
and
reviewing
internally
with
zetlen
Eric
Andrew,
James
kind
of
the
approach
that
we're
proposing
for
this
is
to
sort
of
bifurcate
than
use
at
the
beginning.
Since
the
two,
the
first
two
options,
we're
planning
to
explore
is
PayPal
and
then
just
checkout.
So
if
they
were
to
click
PayPal,
then
it
would
go
outside.
C
It
would
do
the
PayPal,
validation
and
pop
them
back
into
this
sort
of
confirmation
screen
which
has
the
shipping
payment
and
then
some
standard
shipping
options
displayed,
and
then
they
would
be
able
to
confirm
the
order
and
go
through
with
checkout.
However,
if
they
chose
to
go
the
guest
checkout
way,
then
it
would
pop
them
into
sort
of
a
zero
state
of
the
same
draw
configuration
where
they
wouldn't
have.
C
If
this
was
the
first
time
or
since
this
is
guest
checkout,
they
would
have
to
add
shipping
and
billing
information
and
it
would
be
preloaded
with
the
standard
shipping
method
whatever
that
is
so
if
they
hit
add
shipping
information,
it
brings
up
the
shipping
information
screen
where
you
would
be
able
to
add
your
all.
The
pertinent
details,
and
then
you
hit
done
whoops,
don't
know
what
happened.
A
C
C
So
that's
kind
of
what
we
have
right
now
and
then,
if
you
noticed
on
the
screen,
where
information
has
already
been
filled
out,
the
initial
prompt
changes
to
kind
of
indicate
that
you
can
edit
those
entries.
We
have
dealt
with
the
prompt
to
either
save
a
shipping
address
or
save
a
credit
card.
Because
then,
if
we
get
into
sort
of
the
my
account
territory
and
we're
not
dealing
with
that
for
MVP
right
now,
it
would
just
be
PayPal
and
guest
checkout.
So
that's
what
we
have
so
far
any
questions.
A
Yeah
and
the
hope
is
that
it'll
be
some
reuse
with
this
and
that
it
some
of
the
recent
work
that
will
actually
see
her
from
Barger
and
just
a
bit
where
they'll
be
users
common
experience
inside
of
this
I
think
you
know,
I
get
a
lot
of
folks
will
ask
us
kind
of
why
payment,
but
it's
also
we're
you
know
it's
also
in
a
you
know.
In
response
to
you
know
some
of
those
some
of
the
feedback
we've
got
in
terms
of
our
viability
and
so
you'll
see
a
lot
of
the
work
here.
A
You
know
we
are
thinking
about
things
like
the
offline
experience
and
all
the
mechanics
around
that
what
it
means
to
make
a
commit.
If
suddenly,
you
lose
connection,
but
I
think
Tommy's
done
a
really
nice
job
setting
this
up
with
what
we
believe
is
certainly
very
viable,
but
also
fairly
straightforward.
Some
of
the
some
of
the
basic
integrations
that
are
available
within
agentive,
too,
and
so
we're
super
excited
about
it
and
again
this
will
be
part
of
kind
of
our
our
final
stretch
over
the
next
next
burn
or
two
to
what
to
pull
this
together.
C
A
A
little
bit
on
Friday,
but
we
didn't
have
a
chance
to
groom
them
on
Friday,
so
this
will
be
it
for
next
and
so
for
anyone
who's
following
carefully.
They
may
have
actually
seen
a
preview
of
themselves,
but
we're
just
testing
to
see
what
was
intentional
is
that
we
want
to
see
you
at
that
see
who's
paying
attention,
so
very
good,
cool,
great
Thank,
You
Samuel,
all
right.
So,
let's
I
flip
switch
gears.
A
Then
looking
at
the
lineup,
we've
got
the
pretty
pretty
hefty
updates
from
from
her
friends
and
fights
and
so
got
the
updates
that
include
again
some
of
the
work
around
prom
adoptions,
the
the
more
complex
product,
detailed
scenarios
and
then
pagination,
which
I
know
is
in
progress.
But
but
I
know
that
they're
excited
to
share
that
as
well
as
a
bit
of
a
carryover.
We
haven't
had
a
chance
to
demo,
which
again
is
that
many,
the
editable
shopping,
cart,
which
I
think
plays
well
and
what
we're
just
talking
around
with
our
peanuts.
Don't
worry!
G
Men's
tops
page
has
enough
products
here
that
starts
breaking
down
into
you
know
multiple
pages
here
so
right
now
my
paginate
er,
it's
the
arrows
will
navigate
the
little
page
marker
from
side
to
side
once
it
hits
one
of
the
edges.
These
arrows
go
dead
and
right
now
the
square
stays
centered
wherever
you
navigate.
G
Now,
whenever
a
new
page
is
hit,
it
has
a
full
page
load
because
category
is
a
root
component,
and
so
the
paginate
er
is
part
of
that.
I've
been
considering
trying
to
make
some
kind
of
implementation
where
the
pagination
component
persists.
So
there's
not
so
much
of
an
abrupt
reload,
but
once
these
are
a
hit,
these
are
all
cached,
so
it
happens
much
quicker
than
those
in
the
first
iterations
yeah.
This
is
more
or
less
the
meat
of
it
right
now.
G
C
G
C
C
Yeah
I
like
the
idea,
as
we
discussed
last
week
of
trying
to
persist
this
and
not
have
it
reload
with
the
page
mm-hmm
that
way,
we
could
also
use
it
to
kind
of
let
the
user
know
they
clicked
it.
Maybe
the
marker
moves
over
to
four
and
then
the
page
loads.
In
the
background
they
know
something's
about
to
happen.
It's
it's
a
good
opportunity
to
do
that.
If
those
two
up
we're
not
coupled
so
tightly
together,
but
I,
just
a
thought,
yeah.
A
G
L
L
Yet,
but
I've
got
moths
from
the
color
names
to
the
actual
hex
values
for
an
and
currently
the
disabled
options
don't
show
up,
because
I
wanted
to
open
that
up
to
more
of
a
community
discussion
on
how
we
want
to
implement
that
I'm,
not
sure,
there's
gonna
be
back
in
logic
for
actually
calculating
which
objects
are
disabled
or
not,
because
that
can
get
kind
of
complicated.
So
I've
left
that
a
little
separate
issue
from
now,
but
when
not
all
of
these
are
selected,
the
Add
to
Cart
button
is
disabled.
L
L
C
So
I
think
that
the
design
on
has
the
add
to
wish
list
right
under
the
the
big
image
at
the
top
and
the
Add
to
Cart
is
sticky
at
the
bottom,
similar
to
the
pagination
and
the
markups
are
all.
There
is
a
PD
page
markup,
which
I
can
separately
link
you
to
on
slack,
but
we
want
to
kind
of
keep
that
model
of
actions
being
sticky
in
the
foot
of
the
most
important
action
on
the
page.
C
A
Yeah
tell
me,
and
it's
okay
yeah,
just
a
couple
notes
on
this
one
so
I
would
say
for
MVP,
I
would
say
being
inventory
aware:
it's
probably
something
we'll
probably
defer
for
that.
So
Paul
I
think
it's
great.
You
call
that
out.
We
definitely
want
to
have
a
group
of
you
point
on
that.
One
because
you
know
I
think
we've
seen
17
available
on
a
lot
of
things.
I
mean
across
all
the
different
works
per
se,
but
I
think
look
for
a
cut
line
on
that,
one
which
I
think
it's
fine
right,
I
get.
A
If
you
look
at
something
that's
workable
and
then
Y
on
the
you
know
on
Sami
Anan,
the
add
to
wish
list
to
add
to
cart'
actually
see
what
you
did
there
regard
to
the
master
of
product
detailed
experience,
which
actually
has
it
fairly
similar
to
how
you've
done
it.
I
think
we
just
need
to
look
at
the
kind
of
a
master
template
master
change
across
that
they
would
bring
this
closer
to
what
we've
got.
A
But
again,
no,
you
know
I,
you
know
something
that's
more
Universal
based,
but
we
would
just
find
a
way
to
merge
between
what
you've
got
on
basically
options,
then,
to
kind
of
what
we
do
on
kind
of
a
more
simple
product
details
page
and
so
we'll
look
for
that
as
well.
But
we'll
set
up
some
we'll
set
up
some
follow-ups
on
that
one
which
would
then
just
give
that
a
universal
experience
and
so
I
I.
Definitely
do
we
add
it
on
that.
L
A
E
H
E
H
We're
going
to
talk
about,
and
the
thing
is
you
guys
have
built
it.
I'm
I
have
not
written
my
code
review
for
years,
but
I've
looked
at
it
and
you
guys
have
built
this
in
such
a
way
that
you
can
swap
your
implementation
out
and
we
the
presentational
component.
That
is
when
this
API
is
available.
So.
F
A
So
yeah
no
I
think
it's
good
feedback
and
it's
also
something
to
watch
out
to
for
again
not
with
this,
but
in
general,
as
we
start
to
dive
in
some
more
product
details
and
other
aspects
with
that
relate
to
sample
data.
So
James
and
I
had
a
good
chat
with
the
folks
who
own
that,
and
so,
as
we
debug,
and
that
new
functionality
look
at
coverage,
there
may
be
instances
where
we
would
just
tweak
the
sample
data
and
we're
looking
at
that
as
an
entity
and
a
resource
as
well
throughout
that
right.
A
Now,
that's
not
something.
We've
had
much
Liberty
to
play
around
with,
but
we
had
a
good
shot
with
them
to
figure
out
how
that
might
help.
And/Or
relate
to
things.
That's
the
more
of
a
side.
Cameras
are
more
of
a
deeper
conversation
on
the
side,
but
as
we
hit
the
items
where
we're
trying
to
look
at
coverage
in
for
sample
data
that
that
too,
is
that
there's
an
aspect
for
we
might
want
to
introduce
and
change.
Yeah
I
mean
bear
in
mind
that
the.
H
H
It,
but
you
know
if
we
should
provision
a
couple,
more
clouds
and
change
the
issue
that
we're
trying
to
get
out
ahead
of
it.
A
lot
of
people
need
to
change
their
sample.
Data
will
get
end-to-end
testing
together
there.
We
need
to
consolidate
all
the
data
that
people
made
into
satisfies
the
use
cases
and
then
read
the
sample
data,
push
it
as
a
dependency.
So
eventually
we
want
that
automated.
A
And
you
won't
know
what
it
is
and
then
just
a
really
rate
I
mean
it's
essentially.
The
approach
from
bar
green
is
identify
some
of
those
dependencies,
but
keep
them
keep
going
right,
mock
them
out,
keep
going
and
then
we'll
come
back
around
some.
So
that's
the
way
this
has
been
Donna's.
You
know
continues
to
be
a
really
good
example
for
us.
So
we
appreciate
that.
Okay,
it's.
H
C
Question
on
this
screen,
so
I
see
that
the
quantity
field
doesn't
seem
to
have
control.
That
indicates.
Oh,
it's
a
drop-down,
okay.
So
on
mobile,
it's
going
to
have
to
use
the
device
default
right
of
android
or
iOS
one.
Is
that
sort
of
roulette
type
thing
on
iOS
and
then
on
Android?
It's
sort
of
a
radio
button
selection
when
you
hit
quantity.
I
C
C
Yeah
and
the
label
style
is
different
than
the
other
two
for
color
in
size.
So
we
probably
want
to
look
at
that
and
I
discussed
that
with
Jimmy
and
it
would
be
whatever
the
device
default
is,
and
there
are
markups
for
that.
I
can
add
them
to
the
shared
community,
one
if
you
guys
are
going
to
tackle
that
at
all.
If
not,
let's
not
worry
about
it
and
we
can
deal
with
it
when
we're
ready
to,
but
just
a
note.
E
Yeah,
hey
guys,
this
is
me,
so
I
SI
got
question
about
color
schema.
So
in
case
just
imagine
case
we
got
white
color.
So
what
about
I
mean
seek
seek
color
so
do
we?
Do
we
get
the
same
white
or
it
will
changed
automatically
to
gray
or
like?
So?
What
is
single,
I
just
worried
about
mobile
a
desktop?
Is
it
supported
automatically
and
change
it
automatically?
All
we
need
to
add
some
kind
of
logic
to
that.
L
D
D
L
D
C
H
L
G
So
to
get
our
screens
is
just
a
mock
component,
that's
just
kind
of
static,
but
it
will
illustrate
that
in
the
edit
card
state,
the
little
X
up
here
does
keep
the
card
state
still
in
the
the
edit
screen,
whereas
that
cancels.
What
brings
you
back
to
the
mini
card
apart
from
that
add
to
favorites,
has
a
any
little.
You
know
fills
in
the
heart.
Of
course,
that's
just
another
marked
up
feature
can
change
how
that
gets.
G
A
Cooper
for
this
one,
we
actually
had
a
discussion
last
week
about
this,
and
so,
as
we
started
start
to
look
at
the
line
for
next
month,
which
could
wish
list
of
course,
would
be
fantastic,
but
I
think
that,
along
with
some
other
functionality,
we're
looking
at
around
sort
and
filter.
We'll
probably
look
at
that
for
the
next
reason,
if
we're
only
the
only
reason
why
that
the
the
API
coverage
just
won't
be
there
for
that
one.
A
K
A
K
J
K
A
H
G
H
Right,
that's
their
backlog
to
be
to
be
sure
of
it,
and
this
is
one
of
those
cases
where
the
technical
debt
to
pay
off.
If
we
did
it,
the
hacky
way
would
be
considerable.
Well,
I
haven't
telling
people
you
know,
incur
some
tech
debt
here
and
they're
like
get
things
done
in
this
case
like
you
would
have
to
do
such
a
weird
hack
in
order
to
get
sort
of
every
working
25,
and
that.
H
A
C
C
That's
one
the
other
one
is
I
had
talked
about
this
earlier
is
when
they
want
to
remove
an
item.
We
need
to
ask
them
to
confirm
that
and
not
just
remove
it.
We
need
some
kind
of
interim
like
are
you
sure
you
want
to
remove
this
item
from
your
cart,
because
we
wanted
to
prevent
them
from
doing
that
as
much
as.
G
C
Introducing
fiction
there
is
a
good
thing
and
also
sometimes
fat
fingers
and
you
you
tap
it
by
accident,
so
you
want
to
give
them
a
fail-safe
to
not
have
to
go
back
and
read
it,
and
so
we
definitely
need
some
kind
of
you
know
treatment,
and
we
can
talk
about
what
that
user
experience
needs
to
be.
I
haven't
worked
on
it
yet,
but
that's
that's.
Those
are
my
two
notes.
C
G
C
I
believe
so
that
was
the
update.
I
was
trying
to
distinguish
between
masking
something
versus
you
know
using
that
to
highlight
something
so
the
teal
usually
works
like
on
an
active
quality,
lower
notification,
but
really
here
you
just
telling
them
that
that
item
is
the
background,
is
kind
of
inactive
as
you're
performing
these
actions
in
the
foreground
and
the
way
we're
doing
that
in
every
other
context,
is
to
have
the
dark
sort
of
gray
mask
it's
a
little
bit
better
with
that
model.
C
Unless
somebody's,
which
case
we
can
definitely
discuss
it,
but
that
was
the
thought
make
sense
to
me.
Okay,
so
yeah
awesome
work
and
thank
you
I
can't.
Thank
you
guys
enough
for
being
constantly
engaged,
and
you
know
bringing
me
for
feedback.
It's
been
really
great
working
with
you
guys
on
all
of
these
pieces
yeah.
Likewise,.
A
Thank
you
guys,
so
I
think
we've
got
one
more
item
here.
I
just
want
to
reach
out
I
know:
we've
got
Artem
on
the
line,
who's
been
working,
fevers,
Artem
I
know
you
tried
to
get
a
demo
and
tried
to
share
some
things
about
two
weeks
ago
and
we
were
running
in
some
some
hosting
challenges.
Anything
you'd
like
to
share
for
this
week
or
would
you
prefer
to
hold
off
on
that
for
a
product
slider.
A
A
B
Yep
so,
according
to
product
slider,
actually
their
meeting
with
Jimmy
with
Sami
about
front
end,
which
would
look
like
and
especially
for
architectural
stuff.
Oh
yeah,
I
am
I,
am
currently
on
it
for
also
I
made
the
new
components,
a
mess
block
component
and
picture
controls,
and
if,
if
wait
second.
B
F
A
B
B
B
H
M
A
Perfect
yeah
and
once
I
done
so
on
the
merge
itself.
Well,
you
know
we'll
work
with
saamiya,
so
she
made
note
of
it
last
week
the
the
images
we
had
there
were
a
bit
placeholder
and
so
we're
gonna
take
something
from
the
proper
venue
catalog
it
shouldn't
be
completely
different,
but
we
want
to
make
sure
that
what
we
have
yeah
just
like
the
rest
of
the
product,
imagery
that
it's
got
the
right,
lovely
thing
in
section,
so
so
we'll
swap
those
out
during
the
merge.
That
should
be
pretty
pretty
easy.
So.
C
A
C
A
A
Perfect,
well,
that's
it!
You
know,
amazingly,
we
finished
up
finish
up
quite
early
that
we
covered
a
tremendous
amount
of
progress
during
the
some
of
which
we
did
internally
and
then
quite
a
bit
of
it
from
from
the
community,
and
so
any
other
comments
or
questions
that
we
wanted
to
cover
before
we
have.
We
break
for
this
demo.
I
think.
H
It's
worth
demoing
a
thing
that
that
we
were
able
to
merge
in
I
can't
demo
it
because
the
City
of
Austin
has
issued
an
oil.
My
computer
warning
boil
it
at
a
rolling
boil
of
three
minutes
before
whatever
is
infecting
it
is
fully
neutralized
but
I'll
deal
with
that
later.
But
if
anyone
has
yet
used
the
grass
UL
playground
that
we
added
say
something
now:
has
anyone
used
it
I.
H
L
H
H
H
So
tell
them
is
inside
it,
and
that
is
among
the
last
few
things
that
we're
going
to
be
adding
to
the
dev
tooling,
and
this
isn't
really
I
guess
demo
news,
but
you
know
my
my
job
from
here
on
out
is
to
act
as
bug
fixer
for
the
set
up
process
and
to
take
care
of
all
of
this
or
P
zeros
that
occur
in
that
respect.
I.
H
H
Go
to
slash
graphical
and
you
can
show
your
terminal
James
and
show
that
it
actually
lists
this
URL.
So
he
probably
has
a
share
versus
okay,
no
problem.
It
lists
the
URL,
so
you
should
be
able
to
see
it
and
and
click
on
it
from
your
terminal.
H
But
what
this
does
is
it
collects
all
of
the
graph
QL
files
that
it
can
see
in
your
project
and
there
may
be
a
future
enhancement
where
we
can
actually
plug
into
the
build
and
watch
the
inline
graph,
QL
tags
and
graph
QL
files
go
by
and
then
aggregate
them
all
so
that
we
can
put
them
in
these
tabs
for
testing.
But
this
is
like
graphical
something
that
each
time
was
requesting
bizarres
on
the
line
for
me
pom,
and
so
is
it
Sumitra?
H
So
if
you
can
see
this
Mentos
Vitaliy
and
so
yeah
so
great,
you
guys
now
have
the
ability
to
use
something
a
little
bit
more
sophisticated
than
postman.
So
you
don't
have
to
manually,
create
the
JSON
for
so
click
the
plus
you
can
click
the
plus
sign
there,
James
and
or
well
that
opens
a
new
tab.
I
said
plus
sign
I
meant
play
sign
so
over
and
get
product
detail
the
get
product
detail
tab
that
one
should
have
if
you
cook
sled
any
that's
not
going
to
work.
H
F
H
H
K
J
H
Got
at
them,
okay,
well,
I
mean
for
some
reason
it's
just
not
we're
not
loading
up,
and
this
is
something
I
think
you
kind
of
okay.
So
do
it
Isidore
skirts,
maybe
that'll
work,
we're
gonna
get
data,
yes,
okay,
so
every
tooth
pulled.
We
have
demoed
this
and
now,
obviously
you
can,
you
know,
adjust
the
query
tier
to
as
you
see
fit
and
if
you
haven't
used
graphical,
there's
actually
a
fair
bit
of
autocomplete
functionality
because
of
what
that's.
H
And
I
don't
know
why,
but
maybe
it's
cuz,
the
schema
is
not
popular
because
you
connected
to
a
production.
Isn't
that
that's
what
it
is
yeah.
So
if
you
have
a
local
instance
that
in
development
though,
then
it
should
populate
this
I
happen
to
you.
So
if
you've
got
it
connected,
then
this
is
going
to
be
like
basically
full
auto-generated
documentation
for
graph
duo
which
will
help
you
a
lot
separately
we're
working
on
the
production
in
the
Delta
mode.
So
this
issue
shouldn't
occur,
but.
J
H
A
A
Okay,
very
good,
well,
hey!
Thank
you!
So
much
everybody
have
a
great
rest
of
your
Monday
and
again,
thank
you
so
much
for
everyone
for
the
contributions.
These
demos
continue
to
be
bigger
and
bigger
and
better,
and
it
really
has
a
lot
to
do
with
the
people
on
the
call
here.
So
thanks
again
for
everything,
let
us
know
if
you
have
any
questions
and
we'll
talk.
Thank
you.
Thank
you.
Thank
you.
Everyone
thank.