►
From YouTube: Octant Community Meeting - April 8, 2020
Description
April 8, 2020
Agenda
Upcoming Release - 0.12
Navigation Update! #812
Huge thanks to Milan, Sam, and Ross!
Persistent volume panic #814
Grid actions component #801
Event/Action namespacing #820
Potentially breaking if your plugin uses any internal actions or events. To date, we do not know of any plugins that do this.
Create objects #803
This was enabled for plugins as well.
Demo!
Open Q&A - add your questions here
A
Hi
everyone
and
welcome
to
this
week's
episode
of
the
octan
community
meeting
today
is
April,
8th,
2020
and
per
usual.
We
get
a
bunch
of
things
regarding
the
upcoming
and
release,
then
we
want
to
talk
about
and
then
we
have
an
open
Q&A.
So
if
you
want
to
add
in
something
to
the
open
Q&A,
please
do
so
in
the
hand
can
be
that
I
linked
in
the
chat
there
and
with
that
I'm
gonna
share
my
screen
and
then
I'm
gonna
hand
it
over
to
wait.
B
Thanks
yeah
so
exciting,
we
have
a
another
release
coming
up
here.
This
was
kind
of
so
we
made
the
decision
to
so
I'll
give
some
back
story
on
this.
We
have
been
working
on
the
navigation,
the
new
navigation
which
has
landed
in
master
and,
as
we
were
working
on
this
over
the
past
few
weeks
and
and
releases
there's
been
some
outstanding
issues
with
some
persistent
volume
stuff
and
and
we
fixed
just
a
handful
of
bugs
that
were
kind
of
blocking
people.
B
So
today,
I
just
kinda
want
to
highlight
some
of
those
new
things
and
then
I
I'm,
not
maybe
at
the
end
we'll
do
a
demo
of
the
new
nav
I
think
but
I'll
have
to
I.
Don't
know
what
the
state
of
my
octant
and
I
don't
know.
If
anyone
else
has
it
up
and
running
right,
so
it's
what
my
octant
is
doing
is
always
if
he,
but
it's
wool
I
can
do
that
at
the
end.
I
have
it's
finding
its
next
call.
I
can
make
so
yeah
the
update
of
navigation
yeah.
That
was
all
done.
B
B
It
has
created
the
it
has
removed
some
of
the
issues
with
the
the
vertical
spacing
of
the
of
the
navigation
and
issues
with
it.
Stacking
really
really
high,
especially
when
you
get
into
lots
of
custom
resources,
and
it's
just
it's
all
around.
It's
just
a
much
better
experience
for
everyone
using
it.
So
super
excited
to
have
that
in
and
I
just
I
want
to
give
a
huge
thanks
to
Milan
and
Sam
and
Ross
for
all
of
their
hard
work.
B
On
that
it's
been
it's
been
going
on
for
a
while,
and
it's
been
a
lot
of
you
know:
I
hesitate
to
use
the
word
bike
shedding
because
they
were
important
points,
but
it's
been
just
a
lot
of
back
and
forth,
and
so
it's
all
it's
really
great
work.
So
I
really
really
appreciate
that
and
then
I
wanted
to
call
out
this
one.
B
In
current
master,
which
will
be
out
at
12,
so
I
want
to
say
a
huge
thanks
to
Sam
on
that
it
was
it
was
he
attacked
those
really
quick
and
got
him
done
so
the
other
two,
the
the
next
three
are
all
kind
of
learned:
they're
not
tied
together
specifically,
but
they
do
all
impact
plugins
in
a
way,
so
I
wanted
to
highlight
them.
Brian
added
the
ability
to
create
grid
actions
which
are
actions
so
for
those
who
don't
know
octant
has
this
this
concept
of
actions.
B
An
action
is
really
just
the
ability
to
tell
octant
that
you
have
a
custom
handler
that
you
are
going
to
set
up
so
that
when
somebody
does
something
on
the
front
end
clicks
a
button,
usually
in
that
case
clicks
a
button
that
your
handler
will
be
mapped
to
that
button.
That
is
clicked
and
the
payload
data
that
you've
mapped
out
for
your
action
will
give
sent
into
that
handler.
So
before
the
way
to
do
that,
was
you
always
created
a
button
group.
You
inserted
a
button.
B
The
button
had
an
action,
and
then
the
action
name
was
mapped
to
your
actions.
Callback
handler
now
and
in
grids
that
didn't
look
very
good.
You
always
had
this.
You
had
this
grid
and
then
you
would
create
a
null
you'd
create
an
empty
header
for
the
table
column
and
then
you
would
insert
buttons
into
it
and
and
if
you
had
multiple
actions,
you
end
up
with
multiple
buttons
and
it
just
never
worked
or
looked
right.
It
functioned,
but
it
just
it
the
essence
of
what
people
wanted
to
do.
B
Wasn't
there
so
Brian
went
and
added
the
grid
actions
which
are
stackable
so
when
you
add
them
into
a
grid,
you
get
this
menu
on
the
left-hand
side.
That
has
the
the
three
dots
and
when
you
click
that
you
will
see
all
of
the
actions
that
have
been
inserted
into
you,
the
the
grid
act
to
row
the
grid,
actions
for
that
row,
and
so
it's
a
much
cleaner
way
to
get
in
actions
and
multiple
actions
into
per
feel
like
per
row
in
a
whole
set
of
data
in
a
table.
B
So
that's
really
convenient
and
it's
something
that
we'll
be
taking
advantage
of
throughout
the
application.
As
we
start
to
do
more
kind
of
enhancements
and
modifications
to
our
interface,
but
it's
also
something
that
plugin
authors
can
now
take
advantage
of
as
well
and
then
in
a
related
note,
the
we
went
through
and
we
namespaced
all
of
our
internal
events
and
actions
in
issue
820
and
what
that
means
is
before
they
were
just
kind
of
the
the
name
actually
Jonas.
If
you
could
pull
up
a
twenty
that
would
that
would
be.
B
Yeah
and
just
go
the
files
changed.
So
if,
if
you
look
at
what
was
there
before,
we
just
had
these
really
generic
strings
like
event
type
add
filter,
clear
filters,
remove
filters
right,
so
this
is
a.
This
is
the
event
type
up
top
is
an
example
of
in
a
test
that
was
an
event,
and
then
you
can
see
there
like
on
the
screen.
Now
we
have
all
of
these
internal
event,
types
that
are
named
spaced
with
event
octet.
B
The
idea
here
is
that
in
the
future,
when
people
are
writing
plugins
and
they're
creating
actions-
and
there
have
their
own
events
that
they're
going
to
trigger
in
their
own
actions
as
a
result,
we
want
to
make
sure
that
there's
not
conflicts,
but
we
also
want
to
be
able
to
document
and
give
people
an
easy
way
to
potentially
handle
internal.
Like
add
special
cases
to
handle
internal
octant
events
if
they
were,
if
we
ever
make
that
possible
right
now,
there's
no
way
to
really
route
those
events
through
to
plugins.
B
But
we
are
looking
at
ways
to
do
that,
specifically
around
things
like
when
the
namespace
changes
right
now,
there's
no
plugins
don't
really
get
informed
when
a
namespace
has
changed,
so
the
ability
to
have
a
plug-in
register
itself
with
a
handler
to
listen
specifically
for
event.
Octants
octave
/I
think
it's
namespace
right
that
that
allows
us
to
create
simple
documentation.
B
That's
clear
that
is
easy
for
developers
to
kind
of
understand
what
their
event
is
watching
for
when
they
come
back
and
look
at
it
later,
and
it
also
prevents
us
from
conflicting
with
existing
authors
and
plug-in
things,
because
it's
very
likely
that
you
might
want
to
write
something
and
call
it.
You
know
namespace.
So
then,
in
your
case
it
would
be.
You
know
my
plugin
dot.
You
know
whatever
v1
forward,
slash,
namespace
or
something
so
the
the
it's.
It's
a
small
little
internal
change.
I!
Don't
think
Sam
pointed
out
that
this
potentially
breaks
plugins.
B
If
there
is
anyone
who
is
attempting
to
use
our
internal
actions
but
I,
no,
how
many
plugins
that
are
doing
that
currently
and
I
haven't
seen
anyone
talk
about
it
and
the
I
think
there
would
be
a
lot
of
Hoops
to
jump
through
currently
to
kind
of
do
it
anyway.
So
it's
not
a
like
there.
It
has
to
go
dig
through
the
code,
find
the
thing
in
anyway,
so
I
don't
think
anyone's
doing
it,
but
their
namespace
now,
which
will
make
things
much
easier
and
then
finally,
we
Brian
when
he
created
the
grid
actions
component.
B
He
also
wanted
the
ability
to
create
objects
which
we've
had
an
outstanding
issue
for
a
long
time.
It
was
I
can't
remember,
but
the
it
has
come
up
and
been
part
of
the
plug-in
API
for
an
extended
period.
It's
just
no
one
had
taken
the
time
to
do
it,
Brian
needed
it
for
something
he
was
working
on,
and
so
he
did
it.
So
now
we
have
the
ability
to
create
objects
via
via
plugins,
as
well
as
internally
in
our
store,
but
also
the
plugins.
B
C
Hope
you
can
see
my
screen,
so
this
is
the
yeah.
So
this
is
the
new
bring
in
navigation.
As
we
mentioned,
we
put
a
lot
of
effort
into
this
and
then
back
and
forth
few
times
and
as
you
can
see,
navigation
is
totally
on
the
left
now
and
it's
completely
minimized
compared
they
used
to
be
both
both
horizontally
and
vertically.
C
Basically,
when
you
collapse
it
all,
your
navigation
is
put
all
the
way
to
the
left
and
saving
the
space
for
things
that
are
important,
like
you
know,
deployments
you
and
things
like
that.
So
the
whole
idea
is
just
to
almost
put
navigation
out
of
the
way
and
we
were
not
sure
which
you
should
be
default
and
I
think
on
Monday.
We
decided
that
collapsed.
You
should
be
default
that
weekend
shot
for
now
and
maybe
see
how
it
works
and
get
some
feedback
on
it.
C
So
if
you
guys
have
any
any
feedback,
this
is
geared
little
towards
more
experienced
user,
because
you
can't
seal
the
items.
Do
you
can
still
see
them
if
you
mouse
over
all
the
clips,
but
it's
it's
a
little
harder
to
access
it
and
it's
a
little
harder
to
to
find
what
it
is
the
other
difference
in
behavior.
If
it's,
if
navigation
is
collapsed,
you
can
run
out
of
the
items.
C
I,
don't
know
how
I'm
gonna
do
this,
but
if
I
make
this
window
smaller
kind
of
simulating
adding
more
items,
you
will
see
that
there's
no
scrollbar.
Obviously
this
is
so
tiny,
so
the
items
just
expand
and
we
may
improve
this
in
future,
a
little
more
and
add
ability
to
access
the
items
that
get
hidden,
but
for
now
they're
just
disappearing
and
I
mean
even
I.
C
Think
even
this
is
okay
for
now,
because
if
you
see
that
icons
are
gone,
you
can
always
go
to
expand
its
State
and
scroll
down
to
access
some
of
the
stuff
here,
you're
missing
in
that
sphere,
so
that
is,
in
short,
the
new
navigation.
The
other
big
changes,
the
names
pieces
drop-down,
is
now
moved
to
the
right
close
to
the
context
selector
and
they
kind
of
look
almost
the
same.
C
So
the
thing
this
is
a
good
way
to
position
the
filtering
it
so
so,
with
this
change,
everything
that's
related
to
filtering
filtering
by
labels
by
namespaces
and
by
context
is
kind
of
close
together
in
the
top
of
the
view-
and
we
may
add
some
more
stuff
here
in
the
future,
and
this
filtering
will
change.
I.
Think
Ross
started
working
on
that
too.
That
may
change
in
the
future,
so
the
one
peculiar
thing
without
namespace
is
being
visible.
C
C
So
that's
how
it
works
right
now
and
also
you
can
see
that
there's
breadcrumbs
they'll
give
you
a
better
ability
to
move
back
and
forth
to
so
so
the
whole
idea
of
it
with
this
change
and
some
changes
coming
in
the
future
is
that
to
as
much
as
we
can
we'll
put
put
the
links
inside
move
that
navigation
to
the
side
and
get
filtering
at
the
top.
So
that's
pretty
much
it
any
questions.
A
A
D
I,
don't
know
if
it's
the
right
word
for
it
in
this
case,
because
all
namespaces
and
might
imply
one
day
wherever
you
want
to
see
objects
and
all
namespaces
and
maybe
non
namespace
doesn't
sound
quite
right
either.
But
there
should
be
something
in
there
to
say
it's
like
cluster
overview
level
and
not
necessarily
all
the
namespaces
great.
C
B
Yeah
this
is
this
is
great
I,
one
of
the
things
that
I
have
it's
a
really
simple
thing:
that
one
of
the
things
that
I
really
like
is
when
you're
in
the
cluster
overview,
and
you
select
something
that
then
takes
you
to
a
name,
spaced
link,
it
updates
the
namespace
EURion
and
as
well
as,
what's
it
in
the
menu,
that's
like
it
was
always
even
before
I
think
I
think
it
worked
before.
But
as
always,
it
wasn't
very
clear
that
that
was
happening,
and
now
it's
very
clear
that
that's
what
happens.