►
From YouTube: Octant Community Meeting - October 21th, 2020
Description
Octant community meeting is held weekly. We discuss and talk about the current state and future of Octant, demo upcoming features and releases, and preview new ideas we are considering for Octant.
Meeting agenda: https://hackmd.io/CzaPxtmXT_SW8nEpdwvGzw?view
A
Cool
all
right,
hello,
everyone.
This
is
the
octan
community
meeting
on
october
21st
2020
and
today
we
are
going
to
go
through
a
couple
of
updates,
mainly
around
what
the
game
is
currently
focusing
on,
and
some
of
the
new
navigation
changes
that
we've
just
mentioned
to
master.
A
A
Whoa,
that
is
a
little
bit
of
a
lag
on
chrome,
but
hopefully
it'll
fix
itself
in
a
second
here.
Awesome
cool.
A
So
the
first
thing
we're
going
to
talk
about
is
updates
to
the
electron
work
that
we're
doing
for
octants.
So
as
y'all
know,
we
are
currently
trying
to
push
octant
as
using
electron
as
its
run
type,
and
this
is
currently
in
progress.
We've
talked
about
this
way
way
back
in
like
march
and
even
earlier,
it's
just
something
we
wanted
to
do,
but
at
the
time
there
were
a
bunch
of
issues
that
were
blocking,
and
this
is
actually
something
I
kind
of
want
to
call
out.
A
If
you
go
back
to
this
march
25th
date,
we
said
we
needed
something
like
a
new
navigation
breadcrumbs.
We
needed
a
octane
to
have
like
a
loading
start
without
a
cube
config,
and
so
it's
just
kind
of
cool
to
see
that
we've
called
our
shots
way
back
in
march
and
now
we've
actually
hit
the
entire
list
of
those
requirements
and
now
we're
actually
doing
the
the
electron
piece
of
it
and
there's
already
some
code
that
brian
wrote
that
does
give
us
a
sample
electron
app.
A
But
to
give
an
update
on
what
I've
been
working
on
the
past
week,
we're
I'm
considering
using
electron
builder
in
favor
of
fast
electrons.
So
as
the
electron
is
essentially
this
wrapper
that
allows
us
to
abstract
away
talking
with
electron
directly
through
ipc
and
what
I've
found
is
that
we're
going
to
be
tied
to
the
features
in
s
electron
and
in
this
case,
if
you
look
at
their
features
in
road
map,
they're
noticeably
they're,
missing
stuff,
like
notifications
and
auto
update,
which
isn't
even
listed
on
here.
A
So
if
we
really
wanted
to
keep
using
this,
we're
either
going
to
be
suggesting
that
we're
going
to
fork
this
or
contribute
to
this
or
the
other
way,
is
just
a
side
step
to
see
something
like
electron
builder,
which
already
has
all
of
this
implemented.
But
it
just
means
we
will
have
to
bundle
our
electron
application
in
a
slightly
different
way.
A
So
I'm
looking
to
get
a
proof
of
concept
with
electron
builder,
up
hopefully
sometime
within
this
week,
but
that's
kind
of
the
update
with
electrons.
So
far,
next
up
is
the
community
survey.
A
And
so
this
survey
will
give
us
the
data
and
information
that
we
need
to
make
sure
that
we're
prioritizing
the
right
things
and
making
sure
that
we're
building
what
the
community
actually
wants.
Did
I
miss
anything
about
the
community
that
anyone
wants
to
add.
C
No,
I
think
sam
gave
a
great
summary,
we're
just
trying
to
learn
overall
how
you're,
using
octet
and
there's
an
opportunity
for
you
to
give
some
feedback
as
well.
I
think
we
can
just
even
link
it
in
the
chat,
I'll
link
it
in
the
chat
here
in
case
you
don't
have
access
to
hack
and
d.
A
A
D
I
hope
so
I'm
sorry,
I
just
had
some
issues
with
my
machine
and
I
just
rebooted.
I
actually
my
laptop,
never
ever
crashed
and
it
happened
five
minutes
ago.
So
hopefully
it's
gonna
work.
Let
me
try
to
share
the
screen.
A
Oh,
I
can
stop
sharing
and
if
you
want,
I
can
also
share.
I
have
today
I
have
a
master
builder
locked
in
right
now
that
I
could
share
and
can
just
tell
me
to
click
stuff
as
well.
If
you
want,
it
seems.
D
It
all
right
so
hope
you
can
see
my
screen
so
yeah
I
this
as
sam
said
this
is
now
merged
in
it's
part
of
the
daily
build.
So
if
for
everybody
out
there,
that's
testing
the
daily
builds,
they
should
be
in.
D
We
are
still
collecting
the
feedback,
so
please,
if
there
are
any
issues,
let
us
know,
but
basically
the
navigation
has
been
redesigned
and
we
have.
I
talked
about
that
last
few
meetings.
We
have
a
two
vertical
bars
and
also
there's
quite
a
bit
of
customization
that
we
added,
so
you
can
compress
collapses,
expanded
and
stuff
like
that.
One
thing
that
I
forgot
to
mention
previously
is
for
each
one
of
the
modules.
D
Now
we
have
this
little
box
that
displays
a
little
description,
so
that
should
be
used
also
by
plug-in
orders
if
they
want
to
display
some
more
information
there,
for
example,
description
of
a
plugin
or
something
like
that.
Currently
that's
only
a
text
field,
but
in
the
future
that
will
probably
be
content.
So
so
maybe
some
some
links
or
even
actions
could
be
should
be
able
to
be
performed
from
there
and
also
something
that's
still
not
available.
That
I
wanted
to
show
today
is
via
the
preferences.
D
D
To
the
web,
app
as
well
they're
still
not,
this
is
my
local
build,
so
this
is
not
merged
and
yet
but
I'll
do
a
blue
request
soon.
I
don't
think
I'll
show
this
here,
but
it's
still
working
progress,
but
basically
this
will
allow
much
better
customization
of
octant.
D
So
you
can
do
things
like
you
know,
for
tanks
that
we
used
to
be
able
to
do
only
through
shortcuts
or
or
things
that
were
using
the
valuable
real
estate
space
they
moved
away
here
now,
so
you
can,
you
know,
go
and
quickly
check
the
change.
The
theme
do
things
like
that,
so
the
this.
D
This
is
just
the
first
step
for
preferences
and
I
I
can
see,
there's
gonna
be
a
lot
of
items
that
we
can
put
here
in
the
future,
not
sure
yet
how
we're
going
to
expose
that
for
the
plug-in
orders.
So
it's
something
we
should
probably
figure
out
in
the
future,
but
that's
it
for
now.
Please,
if
you
try
daily
build.
Let
us
know
what
you
think.
D
The
reason
we
did
this
at
this
point
of
time
is
so
we
have
enough
time
for
the
next
release
to
gather
the
feedback.
So
yeah,
that's
that's
everything.
Any
comments,
questions.
E
Will
the
preferences
be
persisted
with
on
the
local
machine
with
next
runs
of
octant,
or
will
it
be
just
for
the
current
running
of
the
web
application.
D
So
so
preference
will
be
preserved
on
our
back-end
side.
That
means
everybody.
I
mean
if
you
have
two
instances,
for
example,
of
octant
running
in
the
same
time,
they'll
share
those
preferences.
D
That's
the
idea,
some
of
those
strictly
client
side
preferences,
like
you,
know,
team
and
stuff
like
that-
that
we
could
store
that
on
a
client,
but
I
I
still
think
we
should
store
preferences
completely
on
the
backhand
side.
A
Yeah
and
adding
a
little
more
color
to
that,
I
think
there's
a
I
don't
have
the
issue
right
in
my
hand,
but
there
is
talk
of
having
an
octet
config
somewhere,
and
this
could
just
live
similar
in
like
dot
config
octane,
and
we
can
just
read
from
that
to
populate
preferences
by
default.
So
there
will
be
some
idea,
persistence
and
this
kind
of
follows
well
into
the
electron
model
as
well,
but
we'll
definitely
work
for
the
binary,
at
least
for
at
least
starting
out.
B
B
You
know
stored
as
a
as
a
local
storage
like
on
the
client,
and
then
some
will
be
the
similar
like
filters
where
we
store
them
in
the
server,
but
then
the
next
time
you
restart
it
goes
away.
It
really
just
depends
on
like
the
nature
of
that
thing,
whether
it's
ephemeral
or
not
so
color
theme
navigation,
we'll
keep
those
around
and
persist
those
as
long
as
there's
you.
C
B
You
know
as
long
as
you're,
not
on
a
new
machine
where
we
don't
know
what
they
are,
but
other
things
will
push
to
the
the
server
and
they'll
be.
You
know
at
run
time
with
a
potentially
like
a
config
file,
or
even
I'm
trying
to
think
of
an
example,
but
I
don't
really
have
a
good
one.
I
think
I
think
it's
safe
to
say
most
of
these
preferences
will
end
up
in
like
a
local
storage
where
their
their
toggle
and
theirs
persisted
between
all
instances
that
you're
running.
E
D
Exactly
that's
going
to
happen
for
sure,
so
how
about
that
plug-in
orders
should
should
they
be
able
to
store
tanks
and
prep
so
actually
provide
interfaces.
B
For
that
yeah
we
have
an
open
issue
to
allow
plugins
to
persist.
You
know
some
type
of
of
metadata.
You
know
for
startup
procedures
and
stuff
like
that,
so
yeah
we'll
eventually
support
that
cool
yeah.
That's
good
to
know.
A
A
Cool,
thank
you,
milan.
That
is
an
awesome
update
on
the
navigation
and
great
work.
I'm
digging
the
new,
the
new
look
and
it'll
be
super
nice.
Once
we
get
that
error
tab
on
the
bottom
too,
and
so
we
can
pretty
much
have
users
not
have
to
go
to
the
terminal
every
time
something
weird
happens
in
octane
and
it'll
definitely
help
reporting
issues
as
well.
A
A
lot
of
these
were
driven
by
the
k-native
plug-in,
and
some
of
these
are
also
from
other
projects
as
well,
and
since
we
were
saying
that
dot
17
was
going
to
be
our
target
electron
release.
We
figured
that
it
would
take
way
too
long
to
push
some
of
those
plug-in
fixes
and
have
make
people
wait,
2.17
to
get
those
changes,
so
we're
gonna
do
a
16.2
just
to
unblock
some
of
the
smaller
issues
that
we've
seen
come
up
with
plugins
and
yeah,
and
this
should
come
on
692..
A
A
lot
of
these
are
just
minor
fixes,
so
it
shouldn't
really
yeah,
so
this
shouldn't
really
be
too
far
out.
But
if
there's
something
that
you'd
like
to
see
prioritized,
definitely
ping
someone
on
the
octan
channel,
so
we
can
make
sure
that
it
gets.
B
Included
and
and
we'll
be
doing,
no
there'll
be
no
breaking
changes.
Obviously,
but
I
just
want
to
state
that
clearly
there
may
be
some
api
editions
that
will
come
out
in
n16
too
we'll
be
sure
to
document
those
and
publish
it
all.
All
this
stuff
will
be
landing
in
master
and
then
we'll
cherry
pick
it
back
into
the
the
miner.
B
A
Yep
that
definitely
sounds
great
cool
all
right,
so
anyone
have
any
questions
about
plug-in
updates
or
things
they'd
like
to
see
to
go
into
16.2,
going
once
twice
all
right
and
we're
going
to
open
q.
A
so
does
anyone
have
any
questions
that
they'd
like
to
ask,
but
we're
all
here.
A
Cool,
it
doesn't
look
like
we
have
any
q
a
today
so
and
as
always,
if
there
are
any
questions,
just
feel
free
to
ask
and
slack,
and
one
of
us
will
pick
it
up,
so
no
pressure
to
ask
in
a
community
format
and
that's
pretty
much
it.
So.
Thank
you,
everyone
for
coming
to
the
community
meeting
and
we'll
see
y'all
next
time.