►
From YouTube: WebIDE past design explorations
Description
Mike and Michael discuss past ideas around removing the tabs on the side in the WebIDE and different areas that were explored to start a commit process.
A
Cool
so
hi
everyone
today
we're
going
to
talk
mike
and
mike,
are
going
to
talk
about
web
id
stuff.
Some
past
exploration
from
a
design
perspective
on
the
exploration
around
moving
away
from
tabs
to
lists,
and
some
explorations
around
the
commit
area
and
like
where
to
put
that
so
mike
yeah,
take
it
away.
And
if
you
have
any
questions
that
you
need
me
to
like.
If
you
want
more
clarifications-
and
I
can
answer
some
stuff.
B
B
People
would
were
constantly
searching
for
like
how
do
I,
how
do
I
get
to
the
edit
mode
from
here?
They
were
lost
they
they
had
no
real
idea
of
how
to
like
transition
into
edit
mode.
So
clearly
the
tabs
weren't
resonating
with
folks
and
then
speaking
with
marcel,
you
know
their
the
original
design
way
back.
B
I
think,
even
back
in
the
dimitri
days,
perceiving
marcel
even
was
kind
of
a
stepped
flow
that
you
would
kind
of
edit
review
commit,
and
I
think
the
only
people
that
understood
that
flow
or
interpreted
that
flow
to
be
that
flow
were
dimitri,
marcel
and
now
us
too,
because
unless
you
knew
the
that
was
the
intent
of
the
design,
it
never
resonated
with
with
people
that
that
was
designed.
So
you
know
that
was
the
the
genesis
of
that
kind
of
tab
flow
system.
B
A
B
To
remember,
if
we
did,
I
don't
think
we
did.
This
was
right
at
the
end
of
my
my
web
ide
career.
This
was
this
was
right
right
before
the
reorganization
kind
of
got
switched,
so
we
were
kind
of
just
exploring
some
designs
thrown
this
out
there
and
then
that's
when
that
whole
reshuffle
happened
so
yeah
this
was
never.
B
I
don't
think
it
was
ever
scheduled
to
be
built
or
implemented.
It
was
more.
I
think
it
was
in
the
phase
of
putting
it
in
front
of
the
engineers
and
getting
their
feedback
from
both.
You
know,
as
consumers
of
of
gitlab
and
and
editors
of
code
editing.
How
did
you
feel
about
them,
but
also,
more
importantly,
like
what
of
this
would
be
challenging?
B
B
A
B
B
A
A
A
B
B
B
B
So
it's
always
kind
of
remained
on
the
bottom,
which
I
do
think
is
a
valid
flow.
But,
looking
at
you
know
some
of
the
other
editors
out
there,
it's
an
interesting
one
because
they
don't
necessarily
like
the
most
engineers
are
coming
in
line.
First,
so
they're,
usually
when
they're
pushing
things
they're
they're
using
the
command
line
for
that.
But
if
you
look
at
vs
code
and
where
the
save
button
or
the
commit
button
or
that
kind
of
flow,
is
it
was
kind
of
up
towards
the
top
area
up
there.
B
So
I
played
around
with
that
a
bit.
I'm
sorry!
So
there's
also
like
explorations
of
like
these
buttons
as
well.
I'm
trying
to
trying
to
remember
what
all
these
things
were.
I
played
around
with
this
a
lot,
but
it
was
this
idea
of
kind
of
moving
it
up
towards
the
top
grouping
it
up
in
this
area
here.
So
you
have
basically
an
action
section
and
then
files
below
that.
What
I
kind
of
liked
about
that
was
that
then
this
can
scroll
and
it's
just
at
the
loss
of
files.
B
This
also
coincided
with,
I
think,
you're
familiar
with
some
of
the
editor
light
stuff
and
some
of
the
in
context,
editing
and
playing
with
that
idea
that
dennis
was
was
had
built
up
kind
of
that
proof
of
concept
and
that
really
started
to
feel
kind
of
like
a
direction
that
maybe
we
can
go
in.
So
the
thought
was
maybe,
if
we
had
built
out
this
kind
of
modal
commit
flow
for
this,
that
it
could
be
reused
wherever
we're
doing
that
in
context,
editing
to
try
and
kind
of
componentize.
B
B
But
if
we
can
get
that
into
a
modal,
then
it's
that
same
flow
every
time
that,
unfortunately,
did
not
get
user
tested.
So
that
is
a
wild
theory
that
I
would
highly
recommend
throwing
some
user
testing
at
before
proceeding
down
that
that
modal
flow.
But
that
was
kind
of
the
thought
of
this.
One
of
let's
group
everything
all
your
actions
in
one
place
and
then
go
to
a
more
modal
style,
commit
flow.
A
That's
not
too
far
off
because
we
started
exploring
some
of
that
in
the
static
set
editor
and
the
timing,
and
the
way
you're
talking
about
things
is
aligned
to
like
what
nadia
and
I
are
kind
of
thinking
about,
of
having
a
consistent
commit
flow
across
the
different
editors
she's,
focusing
more
on
pipeline
pipeline
editors,
which
is
based
on
top
of
editor
light.
So
it's
kind
of
on
the
same
world.
It's
like
different,
looks
and
feels,
but,
like
you
know,
the
commit
flow
in
in
general.
B
Yeah,
it
seems
like
a
if
we
could
prove
it
out
to
be
a
viable
user
flow.
It
just
seems
like
it's
going
to
save
so
much
time
and
just
be
able
to
build
that
once
and
maybe
even
do
testing
around
that
and
get
that
flow
really
knocked
out
because
yeah,
whether
it's
static
site
or
or
ide,
or
even
in
the
source
code,
you
know
side
of
things
or
the
pipeline
editor.
B
Really.
The
commit
flow
is
fairly
similar.
I
think
the
static
site
maybe
had
a
little
variance
of
like
assigning
a
approver
or
something
during
that
flow,
but
yeah.
It
seems
like
the
kind
of
flow
that
I
I'm
just
not
seeing
why
it
would
vary
differently
right,
like
I'm
a
fan
of
defaulting
to
consistency
unless
there's
a
reason
to
not
so
it
seems
like
that
flow
would
would
be
a
good
candidate
for
that.
B
B
The
split
drop
down
we
kind
of
got
into
a
split
drop
down
phase
that
we
were
doing
some
tests
on.
So
it
was
kind
of
pushing
that
idea
here
and
the
answer
to
the
question
that
you're,
probably
thinking
is
well.
What
is
in
that
drop
down,
it
would
be
discard.
All
changes
would
be
the
only
option
in
here.
So
it's
a
little
interesting
that
do
we
really
need
a
drop
down
for
that,
but
it
was
kind
of
just
cleaning
some
things
up.
B
If
you
really
wanted
to
like
move
all
these
buttons
out
of
this
header
and
put
them
in
there.
I
think
this
one
is
the
cleanest
visually,
but
probably
not
the
best
experience,
but
if
you
do
like
grouping
buttons
together,
here's
an
opt-in
for
that
and
then
I
think
I
think
this
was
just
the
bait
yeah.
This
was
the
standard
one
and
then
components.
B
B
B
B
A
B
B
A
A
B
Yeah,
no,
I
remember
yeah.
It
was
about
the
time
when,
when
I
started
looking
at
that
modal
flow
and
marcel
was
was
encouraging
me
to
look
at
the
static
site,
editor
stuff,
that's
how
I
knew
about
the
reviewer
flow
and
all
that
stuff,
because
yeah
that
was,
I
was
looking
very
much
at
the
modal
that
you
were
working
on
the
modal
fold
that
you're
working
on
for
that.
A
B
In
context,
editing
issue
again
with
daniel
ipm,
just
seeing
the
progress
of
editor
light
and
now,
knowing
that
it's
going
to
be
the
base
for
the
web
ide
and
just
the
power
of
that
and
then
also
knowing
kind
of
the
history
of
the
single
the
single
file
commit
flow
not
being
optimal
and
then
also
seeing
those
kind
of
we
have
now.
I
have
like
four
editors
right
and
and
the
web
id
and
the
single
file
editor
have
always
been
a
difficult.