►
From YouTube: JupyterLab Team Meeting - 19 July 2023
Description
A meeting to share and discuss features, ideas, issues, and pull requests in JupyterLab and other Jupyter frontends. This meeting is open to anyone and everyone.
Join future calls via the Jupyter community calendar: https://docs.jupyter.org/en/latest/community/content-community.html#jupyter-community-meetings
Notes for upcoming meetings can be found on the agenda: https://hackmd.io/Y7fBMQPSQ1C08SDGI-fwtg
Past notes can be found on the JupyterLab team compass: https://github.com/jupyterlab/team-compass/issues/205
A
To
the
clouds,
okay
recording
started:
welcome
everyone
to
the
July
19
2023
to
prolect
the
call
I'm,
Andrea,
bocchenko
and
I'm
hosting
the
call
today.
I
will
post
the
link
to
the
cake
MD
again
to
the
chat
so
link
link
to
hacking.
This
in
the
chat
I
can
see
people
already
signing
in,
but
there
is
nothing
on
the
agenda.
A
A
It's
been
a
project
wrong
in
the
works,
so
good
job.
Everyone
in
the
world.
A
B
C
Thanks
I
was
hoping
somebody
would
speak
before
me.
I,
don't
think
my
colleague
Gabriella
is
on
the
call.
C
I
just
wanted
to
give
a
brief
update
and
we
will
be
creating
issues
around
this
so
that
people
can
actually
look
a
goal
that
I
hope
we
can
achieve
either
before
4.1
or
n4.1,
depending
on
what
the
address
look
like
is
to
allow
for
virtual
scrolling
and
large
notebooks
to
be
turned
on
by
default,
because
if
it's
not
on
a
lot
of
people,
might
never
Discover
it
and
might
not
there's
a
way
to
mitigate
performance
issues
with
large
notebooks.
C
But
right
now
we
have
put
it
behind
a
preference,
because
we
had
some
pushback
on
the
nature
of
virtual
scroll
right.
So,
if
you
imagine
you're
inside
Instagram
and
there's
an
infinite
scroll,
you
scroll
to
the
bottom
of
the
page,
some
stuff
gets
added
and
your
scroll
bar
jumps
up,
because
some
stuff
was
added
and
that
doesn't
bother
you
because
that's
an
infinite
scroll.
You
don't
expect
that
to
end,
and
you
can
imagine
in
another
circumstance,
you're
saying
Google
collab
and
you
have
a
notebook
and
you
see.
That's!
C
That's
not
a
native
scroll
bar,
it's
a
custom
one,
but
you
scroll
from
top
to
bottom,
and
you
have
a
fairly
coherent
experience.
Not
really
aware
that
what's
happening
under
the
covers
is
that
only
what
you're
seeing
is
being
rendered.
But
the
dimensions
of
the
notebook
are
known.
We
don't
have
the
full
dimensions
of
the
notebook.
That's
why
our
scroll
bar
jumps,
because,
even
though
we
know
how
many
cells
there
are,
we
don't
have
a
way
of
knowing
how
tall
each
cell
is
and
a
cell
can
be
arbitrarily
large.
C
You
can
imagine
a
notebook
with
2
000
cells
in
it,
and
one
of
them
occupies
95
of
the
real
estate,
because
it's
a
giant
cell
and
every
other
sells
time,
for
example,
or
a
markdown
cell,
that's
arbitrarily
large
HTML
or
a
widget.
That
does
some
crazy
thing
to
your
screen
or
lots
of
different
outcomes
can
manipulate
the
height
of
the
notebook
right,
and
so
what
Gabriella
and
I
talked
about
yesterday
and
when
I
think
we
can
bring
forward,
are
some
wireframes
to
test
people's
intuitions
here.
C
So
you
need
a
scroll
bar
partly
to
see
the
dimensions.
B
C
Document
right,
so
if
we
have
a
control
that
shows
you
every
individual
cell,
imagine
if
you
have
used
a
slideshow
app
like
Google,
slides
for
example
or
or
if
you've
used
Apple
preview,
where
you
open
up
10
documents
and
there's
a
sidebar
that
shows
you
thumbnails
of
each
now.
We
cannot
produce
thumbnails
at
least
not
currently,
but
we
do
know.
C
I
mean
cells,
have
a
thing
that
signifies
them,
whether
it's
the
execution
count,
whether
it's
cell
ID,
whether
we
provide
a
custom
renderer
for
a
cell,
to
give
you
something
better
and
some
future
date.
C
The
point
is,
we
can
create
a
sidebar
that
shows
you
exactly
how
many
cells
a
notebook,
has
and
gives
you
a
native
scroll
bar
for
that
control,
but
hides
the
native
scroll
bar
for
the
actual
no
book
itself
and
allows
you
to
scroll
with
all
the
modalities
you
have
with
your
trackpad
with
your
mouse
wheel,
with
your
keyboard
up
and
down
arrows.
The
only
one
that
you
cannot
do
is
click
on
your
literal,
scroll
bar
itself.
D
C
Instead,
what
you
can
do
is
use
the
control
that
shows
you
all
the
cells
right
and
scroll
down.
You
want
to
jump
to
the
bottom
cool
scroll
down
and
jump
to
the
bottom
side.
That
kind
of
thing
so
I
think
this
removes
the
counter-intuitive
behavior
of
the
scroll
bar
and
replaces
it
with
something
that
gives
you
all
those
behaviors
that
we
want,
but
we
need
to
play
some.
We
need
to
validate
it
so
hopefully,
by
the
next
time.
We're
on
this
call.
C
I
can
share
some
wireframes
or
something
to
get
people's
opinions,
because
it
would
be
really
nice
if
we
can
make
virtual
scrolling
the
default
and
get
the
benefit
of
this
really
big
enhancement.
That
thread
build
minus
the
the
jerkiness
of
the
scroll
bar
that
harms
the
user
experience
for
some
people,
I.
D
D
I
am
not
knocking
the
work
that
has
been
done.
The
virtual
scrolling
is
not
always
an
improvement
or
an
enhancement
where
it
stands
right.
Now
we
make
a
sacrifice
on
the
small
notebook
experience
for
the
big
notebook
experience,
and
since
you
mentioned
this
yesterday,
I've
been
thinking
about
it
and
I'm
wondering
if
we're
obfuscating
the
two
things
as
the
same
problem,
so
I
agree
that
in
the
large
notebook
experience
we
need
something
better,
but
there
is
a
shortcoming
in
the
current
experience
that
has
kind
of
arisen
with
this.
D
So
I
just
raised
a
little
bit
of
caution
and
going
too
hard
in
the
virtual
scrolling
like
I,
think
it's
a
good
feature
like
I
have
a
notebook.
Now
that
has
I
keep
an
index.I,
Pi
MB
and
sometimes
it
gets
up
to
like
200
250
cells.
I
delete
a
bunch
along
the
way,
like
I
kind
of
go
and
refactor,
that
I
wouldn't
be
able
to
have
that
file
without
the
virtual
rendering
right.
D
But
what
I
do
is
like
I
kind
of
keep
a
running
log
there
I
this
might
not
be
a
common
work
style,
but
I
keep
a
running
log
when
I
get
something
good,
I
move
it
over
to
a
smaller
notebook
right.
So
the
two
experiences
that
I'm
expecting
from
like
a
long
notebook
and
a
short
notebook,
are
different
and
I
kind
of
caution
at
combining
those
two
experiences
together.
C
Well,
so
the
impetus
for
this
work
isn't
to
lean
into
virtual
scrolling,
it's
to
fix
the
behavior
of
virtual
scrolling
so
that
it
stops
bothering
people
but
virtual
scrolling.
It
still
won't
be
a
thing
that
every
single
notebook
benefits
from
if
a
notebook
only
has
20
cells
in
it,
it
might
not
benefit
from
virtual
schooling,
I
mean
then
again.
We
never
know
because,
like
I
said,
if
that
20th
cell
is
like
150
000,
pixels
High,
you
might
actually
still
want
that,
but
we
actually
can't
currently
accommodate
that.
Well,
anyway,.
D
C
But
I
think
people
didn't
have
those
long
ones
well,
I
know
for
sure,
but
here
I
mean
look.
The
actual
like
elegant,
easy
to
reason
about
and
maintainable
solution
to,
this
is
to
say
every
cell
gets
rendered
at
the
same
height
like
the
slide
shows
do
right.
They
know
how
tall
each
slide
is,
so
they
don't
even
need
a
scroll
bar,
but
I
think
people
expect
a
long
form
document
and
not
like
a
bunch
of
collapsed
areas
and
Fred
has
thought
about
this
a
lot.
So,
let's
see
what
he
thinks.
E
Now
I
understand
the
concern
of
Tony,
but
from
a
code
point
of
view
with
we
are
already
finished,
maintaining
the
code
and
having
a
single
way
of
doing
things,
I
mean
we
still
have
the
setting.
We
have
the
settings
to
change
the
behavior,
but
we
should
aim
for
a
common
for
not
changing
the
behavior
if
it's
a
short
or
the
long
document,
because
not
two
people
will
have
the
same
definition
of
that
thing.
C
Yeah,
but
we're
not
committed
to
rendering
a
tensile
notebook
virtually
we
can
render
that
concrete,
reified
great
and
great.
We
could
even
like
we
already
have
the
capacity.
Let's
suppose
we
turn
on
Virtual
for
everything
we
already
have
a
capacity
within
deployments
to
override
default
settings
anyway,
because
you
know
your
users
are
basically
like
nah.
Actually,
it's
not
relevant
here,
we're
we're
teaching,
you
know
sixth
graders,
and
they
don't
make
giant
notebooks
or
something
right.
C
D
Love
it
I
love.
It
I
think
that
what
you
do
is
you
lean
more
on
the
vert.
You
call
the
like
virtualized
notebook,
a
feature
right
like
in
virtualized
Notebook
space
right
like
it's
like
bullet
time,
almost
like.
How
do
you
go
and
think
about
navigating
this?
Almost
as
like
a
different
video
game
effect,
so
yeah
I
could
see
this
as
being
more
of
a
special
kind
of
like
power
up
mode,
whereas
there's
a
simpler
basic
mode,
I.
C
I
see
what
you're
saying
but
I
think
the
optimal
experiences
where
you're
not
even
aware
that
it
just
feels
like
a
document
like
the
optimal
experiences.
Only
the
pixels
on
your
screen
get
rendered
and
they're
always
the
correct
pixels
right.
We
just
can't
do
that,
but
if
we
could
give
you
a
window
into
that
document
and
that
document
whizzes
past
you
in
real
Fidelity
with
the
entire
thing
rendered
and
uses
no
overhead
to
do
that.
That's
like
the
experience
we
want.
We
just
can't
get
there
yet
so
we
render
some
above
we
render
some
below.
F
Can
you
describe
again
with
virtual
scrolling
enabled
it's
you
said
that
it's
giving
you
a
Cell
by
cell
representation
in
the
scroll
bar.
C
So
the
proposal
is
that
the
native
scroll
bar
disappears
and
another
control
replaces
it
that
control
is
just
a
list
of
cells
like
little
squares
right
and
that
has
a
native
scroll
bar.
So
you
can
natively
scroll
that
and
just
click
on
any
cell.
You
want
now
there's
multiple
ways
to
implement
it.
We
could
Implement
that
so
that
that
scroll
pegs
to
the
motion
of
the
notebook,
but
it
would
be
weird
right
because
if
one
sells
way
taller
than
the
other,
the
scrolling
won't
ex
it'll
be
jumps,
not
Scrolls.
So
maybe
we
won't.
C
We
don't
do
that.
Maybe
we
just
let
you
click
on
each
individual
cell
unclear
and
we
leave
the
notebook
itself
working
exactly,
as
is
the
only
thing
that's
different
is
CSS
is
hiding
the
scroll
bar,
but
you're
still
scrolling.
It's
still
rendering
what
you
see.
It's
still
actually
changing
the
height
of
the
container.
C
You
just
don't
notice
it
because
you
don't
see
the
scroll
bar
doing
that
and
that
way
you
have
both
an
idea
of
how
big
this
document
is,
which
is
what
a
real
scroll
bar
gives
you
and
an
ability
to
jump
to
a
specific
place,
which
is
what
a
real
scoreboard
gives
you.
But
you
do
not
have
the
confusion
about
how
tall
is
this
document
and
why
can't
I
jump
to
the
bottom
I
scrolled
to
the
bottom,
and
then
my
scroll
bar
janked
up,
you
know
and
I.
Don't
I,
don't
like
that
experience.
C
C
D
D
It's
just
that
when
I
think
of
the
reality
of
documents
and
like
the
the
scroll
bar
moving
is
like
a
transitory
phase
of
work
in
some
way
right,
like
you,
know,
reading
mode
and
form
submission
mode
or
like
two
kind
of
different
things,
at
least
in
accessibility
land
right.
So
you
know
when
I'm
editing,
I'm
not
moving
around
as
much
so.
My
concerns
are
a
little
bit
different,
so
it's
good
that
we
have
designers
in
this
right
because
they're
going
to
help
us
figure
out.
D
What's
what
in
this
so
I
think
this
is
a
really
worthwhile
feature
to
consider.
The
virtual
scrolling
has
gotten
a
lot
better
from
my
experience
like
with
these
big
notebooks
and
finding
a
way
to
figure
out.
Some
of
these
problems
will
be
definitely
good.
I
just
think
they're,
two
different
ways
of
working
like
I
think
we're
like
the
document
like
comparing
the
document
editing
to
the
moving
around
they're,
probably
two
different
modes
of
working.
C
But
if
you're
writing
the
document
as
the
author,
hopefully
all
of
this
is
actually
transparent
to
you,
because
the
piece
you
care
about
has
been
reified
already
and
it
acts
natively
because
it
is
native
and
your
emotions,
whether
they're
just
micro,
adjustments
of
your
scroll
position
or
whatever
all
that
stuff
happens,
because
it's
native,
we
don't
Implement
that
it
just
works.
The
way
you
think
so.
D
It's
just
yeah,
it's
just
you
know,
I
want
to
see
the
rough
edges
go
away
and
I,
just
that's
the
stuff
that
makes
me
uncomfortable,
like
the
authoring
experience,
has
some
keyboard
problems
right
now
that
feel
super
unfamiliar.
D
D
It's
honestly
like
imperceptible
little
things
that
I
don't
notice
right
like
they're
things
that
in
the
product
like
in
between
when
I'm
moving
around
that
make
me
feel
uncomfortable,
so
they're
sort
of
hard
to
put
on
to
to
to
nail
down
and
one
of
the
ones
that
you're
talking
about.
Is
this
right?
Yeah.
C
So
yeah
no
I
I
mean
that
that
is
and-
and
this
you
know,
is
actually
holding
back.
C
There
is
a
class
of
notebook,
6.x
user
who
has
not
wanted
to
migrate
to
lab,
because
they've
been
concerned
that
the
UI
feels
slower
and
until
we
can
out
of
the
box,
give
them
a
performance,
responsive,
UI,
they're,
not
gonna
migrate,
and
now
that
we've
released
notebook
7,
we
we
might
hear
from
that
class
of
user.
Although
notebook
7
benefits
from
being
a
single
document,
UI
and
probably
won't
bug
them
performance
wise,
you
know
and
also
code
mirror.
C
6
has
held
tier
two,
so
we
do
have
like
we're
not
stuck
in
a
situation
where
users
are
gonna
be
unhappy.
Whichever
way
they
go,
but
it
would
be
nice
if
we
could
persuade
people
that
they're
not
using
something
slow
out
of
the
box,
because
right
now
there's
a
certain
class
of
users
that
feel
that
way.
F
Quick
question:
if
let's
say
you
have
a
bunch
of
cells
and
the
very
last
one
is
very,
very
extremely
tall,
I
guess
what
you
would
be
doing,
then
is
you'd
be
clicking
on
the
last
cell
in
the
scroll
bar
and
then
it
would
take
you
to
the
top
of
the
cell.
Is
that
right,
yeah.
C
F
E
It's
something
we
should
if
we
want
to
do.
That
is
something
we
need
to
implement,
because
for
now
we
don't
have
a
the
only.
The
only
thing
we
can
Target
like
in
the
middle
of
a
cell
is
like
if
it's
a
marked
on
rendered
thing,
it's
a
it's
a
title.
This
is
the
only
thing,
but
as
we
don't
have
any
fragments
specification
within
a
notebook,
then
we
are
a
bit
yeah.
We
are
a
bit
drained
when
scrolling
is.
F
Is
the
sparse
whatever
what
is
it
called
virtual,
rendering
or
sparse
rendering
that
always
that
doesn't
split
a
single
cell
right,
you're
always
doing
individual
single
cells?
F
Yes,
I
think
I,
think
I
think
maybe
Darian
mentioned
that
you
wouldn't
be
able
to
click
in
the
scroll
bar
I.
Guess
I
would
just
I
guess
point
out
that,
typically,
when
you
click
in
this
in
the
scroll
bar
not
on
the
scroll
handle
but
inside
the
scroll
bar,
not
on
the
handle?
Typically,
it's
like
a
page
up
or
a
page
down.
C
So
there's
a
few
things
we
could
do.
There
will
be
a
native
scroll
bar
next
to
this
control.
That
shows
you
all
your
cells
that
should
behave
the
way
all
Native
scroll
bars
do
or
you'll
get
confused.
So
when
you
click
on
that,
it
should
just
page
down
on
the
list
of
cells,
not
change
the
document.
Perhaps
unless
we
decide
we're
pegging
the
document
to
this
list
of
sounds
which
we
could
do
and
that
might
be
a
setting,
some
people
might
like
it.
C
Some
might
not
I'm
not
sure
this
is
one
of
those
things
where
it's
not
an
incorrect
UI.
It's
just
a
confusing
one,
because
if
you
think
about
this
notebook
where
all
the
cells
are
tiny
except
the
final
one
scrolling
through
them
is
a
weird,
not
the
same
speed
experience
right,
it's
a
piecewise
experience.
So
maybe
we
don't
want
that,
because
people
won't
believe
that
that's
what's
about
to
happen
and
then
they'll
be
annoyed
because
something
counter-intuitive
occurred,
but
We
could
decide.
C
No,
we
actually
kind
of
want
this
cell
list
not
just
to
be
a
list
of
buttons
to
jump,
but
also
be
a
control
that
works
roughly.
Like
you
described
I'm,
not
sure
that
is
actually
where
I
think
Gabriella's,
mock-ups
and
wireframes
and
prototypes
will
help
us
gather
some
input
here
and
it.
You
know
the
thing
that
I
don't
want
to
happen
is
probably
what
will
happen,
which
is.
C
C
But
like
that
actually
sometimes
well,
the
defaults
matter
right
to
try
not
to
confuse
users,
oh
man,
so
like
yeah,
the
stuff
that's
going
on
in
the
chat.
A
Okay,
I
I
can
say
that
some
links
from
the
chats
to
the
you
know
the
device
or
any
other
discussion
participants
would
like
to
highlight
any.
You
know
a
keyboard
key
points
from
the
discussion
in
the
notes.
Please
feel
free
to
yeah.
A
I
can
see
that
Tony
just
added
to
another
topic,
so
if
there
are
no
comments
on
the
virtual
scrolling,
let's
proceed
to
20..
This
is
next
topic.
D
Hi
guys
seriously
I
love
you
all
I
love
what
you're
doing
and
making
thank
you
I
have
to
preface
these
things
because
I'm
hard
on
the
product
and
I'm
sorry
about
that.
It's
really
amazing
that
notebooks
haven't
got
out
there.
Congratulations
to
everybody
who
brought
that
over
the
finish
line
and
thanks
to
Jeremy
for
getting
that
started
like
that's
so
crazy
that
that
little
retro
project
turned
into
a
flagship
product.
It's
amazing!
D
It's
not
usable
for
a
screen
reader.
At
this
point,
it
upsets
me
a
little
bit.
I,
really
hope
that
we
can
get
the
tabtrap
pr
merged
in
yeah
right
Mike,
you,
you
commented
on
it
about
two
weeks
ago.
It's
the
one
over
in
Jupiter
lab
that
is
working
on
the
tab.
Traps
really
need
that
in
if
a
disabled
person
comes
to
the
notebook
and
they
can't
tab
around
to
the
second
cell,
it's
a
big
problem.
D
B
So,
just
to
clarify
this
pull
request,
I
requested
changes
on
it
and
that's
because
there
is
a
critical
bug.
If
there
is
a
text
area
in
the
output
of
a
cell,
I
was
trying
to
be
very
gentle
in
my
review,
so
it
doesn't
stand
out.
But
if
there
is
a
text
area
in
a
cell
and
user
tries
to
type,
there
will
be
commands
executed,
which
might
result
in
errors
deleting
code
cells
or
leading
to
other
issues.
So
my
request
to
change
to
the
interest
changes
to
the
selectors
is
not
about
styling.
D
Okay,
that's
that's
great.
I
did
not
know
that
that
was
a
late
Comer
to
the
game
and
that
sucks
that
that's
a
thing
but
like
we
gotta
over,
we
gotta
overcome
this
one.
This
PR
has
been
open
for
months
and
it's
like
the
one
thing.
We
need
to
do
to
open
the
door
to
accessibility
like
everything
we
a
lot
of
the
stuff
that
we
do
around
accessibility
doesn't
get
noticed
when
these
tab
traps
are
the
biggest
thing
that
show
up.
D
So
I
really
hope
that-
and
this
is
affecting
this
affects
this
single
user
experience
and
the
non-disabled
experience
being
able
to
tab
around
the
application.
So
yeah
I
hope
that
we
can
see
this
one
landed
thanks
for
that
extra
information,
Mike.
A
Okay,
I
have
added
the
link
to
regard
to
the
meeting
nodes
after
your
good
points,
starting
if
anyone
else
might
probably
anyone
else
wants
to
add
other
comments.
Please
do
in
the
meeting
notes
yeah,
if
other
than
that
any
other
points
on
this
topic,
any
other
comments,
no
okay.
This
is
good
or
it
is
what
it
is.
So
we
don't
have
anything
else
on
the
agenda,
so
I
want
to
go.
If
there
is
anything
else
you
would
like
to
discuss
now,
because
I
will
end
the
meeting
recording,
if
not
available,.
A
Of
the
recording,
if
there
is
anything
to
discuss
I'll
I'll,
wait
a
minute.
I
I
see
two
hands
up
Frederick
and
me:
Frederick
shows
up
first.
So
please
go
oh.
E
Thanks
sorry,
Nick.
E
I,
don't
know
so:
just
I
I
opened
a
PR
for
for
the
membership
and
the
different
level
of
Team
on
the
team
Compass
to
draft
something.
So
don't
hesitate
to
read
that
and
and
comment
on
it
is
yeah.
E
We
definitely
need
some
some
some
some
cleanup
there,
because
also
I
was
looking
at
the,
for
example,
at
the
GitHub
organization
we
have
24
people
that
are
owner
of
the
organization.
It's
too
many
too
many
for
security
reasons,
so
we
definitely
do
need
to
decide.
Oh,
we
handle
those
membership
and
to
clean
that
up.
Yeah
thanks
a
lot
and
Nick.
You
can
go
ahead.
A
G
Yeah
so
Fred's
been
been
nagging
me
to
get
that
mermaid
PR
into
fighting
shape.
If
anybody
has
any
inputs
on
14102
reasons,
why
we
absolutely
shouldn't
do
it
because
we're
flying
in
the
face
of
the
SSC
and
the
Jets
never
going
to
get
merged
or
I,
don't
know
whatever
I'm
just
exhausted.
On
this
thing.
At
this
point
and.
E
G
Not
going
to
specify
it
then
don't
specify
it.
That's
fine!
The
valid
concerns
out
there
are
the
the
size
right
because
it
brings
an
elk
inside
Escape,
which
is
good
because
that's
big,
tent,
but
they're
heavy.
You
know
so
I
think
whatever
whatever
lab
labs
like
8.9
megabyte
wheel
now,
so
this
will
absolutely
add
another
megabyte
and
some
to
that,
so
we
can
probably
engineer
around
that
and
remove
those
features.
G
If
you
don't
want
mind
maps
and
you
don't
want
fjs
layout,
so
that's
that's
the
thing
we
could
do,
but
we
did.
Since
we
last
talked
about
this,
we
added
a
mime
type
renderer
for
it,
so
you
can
make
dot
mermaid
files
and
you
can
collaborate
on
those
which
feels
great
I.
Did
that
a
little
bit
with
one
of
my,
my
colleagues
not
too
long
ago,
so
just
a
lot
of
a
lot
of
stuff
to
see
there
but
yeah.
If
there's
someone
that's
like
no,
we
can't
do
that.
E
A
You
know
any
description
of
this
to
fmd.
Maybe
links
if
you
would
like
more
publicity.
A
B
I
I
have
a
question
regarding
veeam
modes,
so
so
there
is
a
discussion
about
Jupiter
lab
theme,
extension
and
quite
a
few
people
suggested
adding
that
into
the
core.
The
thing
is
that
the
theme
accession
we
discussed
came
up
from
him.
Previously,
it's
not
only
adding
they
came
up.
It
is
actually
a
standalone
called
Mirror
Workstation.
B
C
C
B
So
my
recognition
from
looking
at
integrating
other
keymobs
is
that
it
would
be
probably
not
very
good
user
experience
and
it's
not
a
very
good
user
experience
right.
D
B
When
users
are
taught
that
they
can
change
a
team
up,
but
they
came
up
in
the
code,
editor
does
not
correspond
to
what
happens
around
it,
so
the
the
traditional
sense
of
a
key
map.
It
also
influences
things
like
the
debugger
and
switching
tabs,
so
the
presets
for
for
the
keymobs
extend
beyond
the
editor,
which
is
especially
visible
in
the
notebook
because
in
in
the
theme
modes,
you
use
Escape
key
to
switch
between
modes.
B
B
So
I
I
will
probably
work
on
reporting
to
develop
theme
to
work
with
Jupiter
lab
for
a
series,
but
going
forward.
It
might
be
actually
easier
and
less
frustrating
for
users.
If
we
consider
adding,
can
bespoke,
came
up
concept
to
Jupiter
lab
and
have
other
one,
and
only
alternative
implementation
have
Jupiter
that
theme
in
core.
C
C
B
So
that
the
maintainer
it's
it's
actually
a
couple.
People
who
are
essentially
maintaining
kids
comment
that
he
would
be
happy
to
okay,.
C
Cool
yeah,
so
then
we
can
just
have
to
team
Compass
vote
and
take
it
up
from
there.
B
I
mean
more
than
that,
because
when
I
I
looked
into
like
using
the
extension,
customizable
extension
called
Mirror,
that's
not
enough,
because
the
veeam
code
mirror
extension
does
way
more
and
you
want
to
customize
these
things
and
by
bearing
that
this
is
just
as
it
came
up
it's
it's
probably
not
enough.
B
So
sorry,
let
me
step
back
and
think
about
an
example
why
it
doesn't
fit
into
like
a
list
of
options
for
a
key
map.
So
you
have
a
code,
mirror
came
up
and
vs
code
came
up,
which
is
a
thing.
B
We
can
have
a
vs
code
team
up
in
in
Jupiter
lab
now
using
Code
mirror
6.,
and
you
want
to
have
theme
as
a
something
separate
and
you
could
have
so
it
veeam
is
not
exclusive,
because
in
the
insert
mode
you
would
still
be
able
to
choose
between
code
mirror
and
vs
code
came
up.
E
B
And
that
would
be
ideal,
so
so
it
would
be
probably
a
setting
code
mirror
extension
level,
which
is
synchronized
with
a
due
to
lab
right
yeah.
It
needs
more
design,
I
I'm,
just
asking
to
get
a
feeling
on
what
you
all
think
and
we
can
iterate
on
that
in
an
issue.
You
know
separate
discussion
later
on.
E
G
Yeah
the
extension
play
feels
really
good
with
that,
because
it
can
already
ship
and
overrides
json.d
that
would
that
would
change
those
defaults,
but
the
defaults
have
to
exist.
It
can't
just
be
you
know
the
Fiat
behavior
and
still
give
because
then
people
eat
Max
people.
They
want
control
of
everything
from
their
keyboard
right.
So
I
definitely
see
that.
It's
not
just
about
the
text
editor
component
inside
of
a
cell.
They
want
to.
You
know
they
want
to
go
in
and
write
some
lists
for
whatever
the
hell
them
speaks
and
automate
everything.
G
G
So
you
know,
Tony
brings
up
the
the
game
controller
frequently,
which
is
great.
You
know,
because
the
game
controllers
have
keyboards
on
them
now,
because,
whatever
in
Bluetooth
and
seat
warmers
and
all
that
stuff,
but
you
know
what
would
a
on-screen
cursor?
That's
not
your
mouse
cursor,
look
like
that.
Just
worked
out
of
the
box
from
from
a
controller
or
from
a
motion
based
thing
or
from
a
tongue
switch
or
you
know
whatever.
That
thing
is
so
that
kind
of
has
this.
Oh
nice
game,
accessibility
guidelines.
That's
great!
G
You
know
what
is
the
overarching
model?
Would
you
have
a
lot
of
things
like
can
I
get
to
this
with
a
keyboard?
Can
I
get
to
this
with
something
like
that
yeah
sure,
and
we
got
that
to
an
extent
but
like
we
don't
have
like
a
lot
of
times
that
in
a
in
a
proper
gaming
system,
you'll
get
an
on-screen
cursor
that
corresponds
to
your
mouse,
but
that
would
conflict
with
a
lot
of
behaviors
that
we
have.
So
if
you've
got
a
cursor,
but
then
you
go
into
a
text
area.
Do
you
keep?
G
B
Mr
clarify:
are
you
advocating
for
helping
for
keeping
Jupiter
lymphium
as
a
separate
extension
or.
G
I
think
I
am
as
a
gateway
drug
to
them.
Jupiter
lab
would
be
awful
because
of
how
many
opinions
it
has,
so
they
need
to
already
be
hooked
on
them
and
then
desire
it.
We
shipped
it
before
because
it
was
built
in
the
code
mirror
it's
key
maps
and
emax's
keymax
were
like.
G
A
Good
discussion
yeah,
if
I,
can
see
that
there
are
already
some
additional
details
and
comments
are
being
typed
in
the
tech
MD.
If
you
would
like
to
add
some
additional
details
from
the
discussion
or
links,
for
example,
someone
who
to
I
I'll,
probably
focus
on
that
Tony
posted
angle
at
it
just
because
I
think
it's
relevant
so
yeah
you
suppose
there
are
any
other
comments
or
points
for
the
discussion.
A
Okay,
interesting
by
the
silence,
there
are
no
other
plans
on
that
topic.
So
then
I'd
like
to
mention
that
if
you
would
like
accurate
assistance,
they
can
be
already,
but
also
would
like
to
voice
it
here.
So
if
you
like,
the
post
next
scripture
lab
call
or
just
if
you
would
like
to
host
a
YouTube
channel
up,
call
please
sign
up
by
the
link
to
the
full
student's
chat.
It's
also
on
hmd.
It's
a
issue
created
by
Darian.
There
is
a
table
with
for
July.
A
Was
the
book
called
like
the
fullest
goals
in
July,
but
you
can
also,
you
know,
sign
up
for
it.
The
later
months,
there
is
a
guide
available,
basically
in
that
spread
for
hosting
actual
update
this
guide,
based
on
the
callings
from
this
call,
but
yeah,
please
feel
free
to
sign
up.
B
A
You
for
watching
Andrew,
oh
my
pleasure
thanks
Isabella,
so
I
shall
wait
a
minute
and
I
will
stop
recording.