►
From YouTube: IPython/Jupyter Lab Meeting, April 29, 2016
Description
Meeting of the IPython/Jupyter Lab development team.
B
C
Sure,
okay,
so
boss
for
Jess
updates,
phosphor
quarters
out
published
its
on
NPM
in
for
a
while
to
their
versions
from
that
you
can
now
install
sort
using
that
from
phosphor
UI
plus
VI
is
not
yet
published.
I've
got
a
few
more
widgets
to
be
done.
Most
of
them
are
in
I
finished
menu
couple
days
ago,
working
on
menu
bar
now.
C
That
might
not
be
done
today,
but
close
to
being
done,
and
that
leaves
command
palette
and
doc
panel
to
bring
over,
and
then
that
should
be
done
and
publishable
to
the
point
where
we
can
use
it:
boss,
fine
and
get
phosphide
running
on
all
the
new
stuff.
Once
we
have
that
done,
then
deprecated
all
the
old
reposts
kind
of
push
them
sweep
them
under
the
rug
debating
whether
or
not
I
want
to
keep
the
github
repos
around.
C
We
could
deprecated
the
NPM
packages
and
they'll
still
work
so
that
won't
break
anybody's
builds
on
I'm
debating
whether
or
not
we
want
to
keep
the
repos
around
and
the
github
or
just
because
there's
so
much
visual
clutter.
When
you
visit
the
foster
Jan
sword
with
them,
there
I
think
it
might
actually
be
better.
You
got
to
remove
them
or
take
the
code,
that's
condemned
and
put
them
in,
like
some
other
deprecated,
think
it
out
just
so
that
the
code
is
there.
C
D
E
C
D
See
a
couple
of
comments
from
Jason
on
it
so
be
tidying
them
up
and
and
that's
basically
it
for
the
message
except
the
most
kind
of
had
to
work
for
that
it's
going
to
be
integrating
render
might
with
it,
so
that
you
can
do
all
this
nice
sort
of
recursively
nested
as
a
widget
area
stuff,
but
at
the
moment,
is
just
just
kind
of
hard
coding
text.
I,
look
pretty
ready
for
whenever
and
a
bunch
such
that
I
said.
E
Chef,
okay,
so
this
week
I
got
the
console
behavior
for
history
working
and
it
seems
it
seems
pretty
much
done
actually
in
terms
of
that
feature,
so
people
playing
around
with
it
and
testing.
It
would
be
great
because
I'm
sure
this
stuff
I've
missed,
but
everything
obvious
seems
to
be
taken
care
of
ste.
Talking
like
that
and
some
of
the
stuff
involved
in
that
is
actually
being
used
elsewhere,
like
this
cursor
position,
stuff
and
lost
even
walk
up.
E
The
other
thing
is
I
just
to
spend
a
virus
today,
working
on
getting
the
ipad
widgets
review
comments.
Fixed
step
is
an
outstanding
PR
with
each
of
the
things
that
I
thought
should
be
addressed.
Addressed
and
I
wrote
a
really
long
comment
to
explain
my
thinking
behind
it,
so
you
might
want
to
take
a
look
at
that
as
well,
and
that's
it
I
guess.
I
want
to
the
next
thing
I
want
to
do
with
console
is
tooltips.
E
F
Okay
spent
a
lot
of
time
this
past
week,
making
working
on
unit
tests
for
things
like
accepting
and
rejecting
dialogues
was
pretty
difficult
to
get
set
up.
But
now
that
that's
there
I
can
test
the
more
interactive
parts
of
phosphor
you.
I
do
/
jsui
and
do
produce
notebook
created,
mock
implementations
of
colonel
session
and
contents
manager
that
we
don't
have
to
spin
up
a
whole
server
to
test
basic
functionality
that
use
those
things
to
include
adding
a
test
for
execution
and
notebook
module
to
that.
F
The
cursor
is
so
that
the
reason
I
needed
was
for
coats
for
cell
splitting
that
behavior,
so
that
shortcut
and
behavior
now
exists
and
darian
gets
to
use
it
when
tooltip
next,
which
will
be
the
tool
typically
applicable
to
both
notebook
and
the
the
console,
and
also
looking
more
and
talking
more
about
notebook
execution
models
and
plugins
to
that
then
use
the
notebook
execution
and
the
widget
on
how
those
would
be
instantiated
and
registered
that
probably
follow
on
discussion.
F
This
afternoon
about
how
we
want
to
handle
that-
and
this
morning,
I
did
some
auditing
of
how
focus
is
handled
and
marked
down
cell
rendering,
as
you
move
in
and
out
of
command
and
edit
mode
and
compared
it
to
the
existing
notebook
in
nature
of
the
behaviors
match
stone.
So
that
is
a
lot
cleaner,
a
lot
less
fiddling
with
flip,
focusing
blur
events
and
it's
more
taking
the
appropriate
action
based
on
user
intent
and
actual
focusing
and
I'm.
F
Sorry,
click
in
double
click,
events
and
changes
to
the
model
don't
get
into
these
groups
cycles
and
that's
about
it
just
been
open
during
with
the
various
aspects
of
the
console
is
one.
B
A
A
B
I
think
the
thing
I
get
her
was
the
releases,
the
type
I
widget
stuff.
There
was
some
fat
finger,
type
of
things
that
happened
and
and
then
so
so
that
I
pay
widgets
releases
were
broken,
Dan
needed
to
be
fixed
right
away
and
stuff
yepper.
We
had
discussions
about
how
to
better
release
things
so
that
more
of
the
process
is
automated
sure.
B
A
I'd,
like
so,
you
know,
consistency
across
the
project
and
how
we
do
things
I
release,
I
realized,
like
parts
of
the
project
have
different.
You
know
really
cycles
and
some
stuffs
going
to
iterate
faster,
but
I'd
like
some
consistency
across
the
board.
Just
so
have
a
bit
of
a
formula
formula
and
everybody
kind
of
expects.
The
same
sort
of
cycles
of.
B
B
B
We
did
a
lot
of
review
of
the
widgets,
particularly
the
widget
six
point:
X
branch
emerging
into
master-
so
that's
so
the
widgets
are
officially
on
6x
now
and
5x
is
a
is
a
is
a
branch
and
then
and
then
we
gave
there
and
a
lot
of
little
things
here
and
there
and
I
saw
your
poster
and
we're
going
to
get
back
to
you
about
that.