►
From YouTube: July 6, 2023 - Ortelius Architecture Meeting
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
B
Let
me
drop
the
link
in
welcome
everybody
to
the
artillius
architecture
meeting
for
Thursday
July
6th.
Let
me
drop
the
link
in
the
chat.
Please
sign
in.
C
B
So
just
we
kind
of
had
a
little
bit
of
this
discussion
on
the
Outreach
meeting,
but
a
little
better
to
do
it
here.
B
B
It
was
like
a
side
project.
Something
was
working
on,
so
we
I
took
another
look
and
based
on
Joseph's
recommendation.
B
I
took
another
look
at
svelte
and
that
one
has
the
most
like
plugins
that
are
available.
So
we
have
the
spell
kit
and
the
material
UI.
So
the
links
are
here
and
also
I
didn't
put
the
links
in
for
the
tutorials,
but
they
have
some
decent
tutorials
I
followed
the
basics
tutorial
along
and
basically
it
was
pretty
easy
to
get
up
and
going.
B
One
of
the
nice
you
can
think
of
spell
is
kind
of
like
the
a
lightweight
version
of
react
so
and
it's
based
on
components.
So
there
are
UI
components.
B
Basically,
you
can
create,
like
let's
say
we
have
like
a
git
detail
box
and
we
want
to
show
that
get
detail.
Box
can
be
a
component
that
code
gets
placed
in
its
own
file
and
then
it's
included
into
the
template.
So
it's
going
to
kind
of
follow
along
with
our
microservice
component
design
at
that
level,
so
the
routing
side,
basically
every
page
is
a
new
route
and
all
the
routings
handled
internally.
B
So
there's
not
a
lot
of
extra
work.
We
need
to
do
on
that
front
for
routing
between
pages
and
passing
stuff.
One
of
the
interesting
things
asphalt
does
is,
even
though
it's
kind
of
like
Hugo
or
doxy
it.
What
it
does.
Is
it
and
it's
a
little
bit
different
from
react
in
this
in
this
aspect?
Is
it
will
you
have
to
run
it
through
a
compiler
and
it'll,
take
all
of
the
templating
and
all
the
the
component
tags
and
expand
them
out
into
native
JavaScript
code?
B
So
it
is,
it
ends
up
being
very
lightweight
and
a
very
small
footprint,
and
because
of
that,
it's
fast.
B
B
Our
our
data
model
is
so
huge
that
we
have
a
lot
of
data
to
display
and
it's
just
not
practical
to
display
it
on
a
phone.
At
this
point
there
may
be
some
actions
because
we're
more
of
like
a
reporting,
you
can
think
of
us
more
on
the
reporting
side
than
like,
where
you're
going
to
interact
and
have
to
do
things.
B
That's
why
we're
going
to
be
that
those
those
platforms
just
don't
make
much
sense
to
do
that
type
of
reporting
on
a
phone
when
we
get
it.
If
we
had
the
need
to,
let's
say
you
wanted
to
generate
a
report
kind
of
like
offline
and
then
send
it
to
somebody
like
maybe
an
s-bomb
report,
or
something
like
that.
That
may
be
one
little
piece
of
the
whole
puzzle
that
we
would
be
able
to
put
into
a
mobile,
but
I
think
that
would
be
a
totally
separate.
B
You
know,
interface
that
would
be
different
than
the
main
UI
on
that
front.
Can.
D
I
can
I
cut
in
for
a
sec
yeah
as
the
person
with
the
most
UI
expertise.
I
have
to
wonder
why
you
keep
veering
away
from
react
because
there's
something
about
react
that
doesn't
appeal
to
you
because
react
has
the
most
documentation,
the
most
plugins,
the
largest
audience,
a
great
interface
systems
like
next
JS,
which
will
do
server-side
rendering
and
you
know-
has
a
dominant
Force
I
mean
why.
Why
are
you
particularly
so
adverse
to
just
adopting
the
industry
standard.
B
D
There
are,
you
know,
a
lot
of
Frameworks
out
there,
but
when
you're
dealing
with
open
source
and
people
coming
in
and
out
yeah,
one
of
the
main
concerns
is
you
know:
can
you
get?
Is
either
the
majority
of
the
people
who
are
going
to
be
working
on
it,
not
necessarily
within
the
interim
team,
but
on
the
outer
team,
familiar
and
educated,
with
the
platform
enough
that
they
can
do
meaningful
work
yeah
without
having
to
learn
a
new
framework?
D
I
really
advocate
for
going
with
industry
standards
from
the
point
of
view
of
diminishing
the
amount
of
Education
you
need
to
do
to
anyone
coming
in
and
learning
it
from
the
outside
and
taking
advantage
of
a
large
amount
of
support,
whether
it's
on
you
know,
Frameworks,
like
stack
Overflow
or
just
in
the
general
Community
yeah
to
you,
know
a
very
proven
and
thoroughly
documented
API
system,
yeah.
B
And
we
could
take
a
look
at
react
again.
That's
we.
We
haven't
really
started
on
the
front
end.
So
either
way
it's
early
enough
to
go
ahead
and
and
take
a
look
at
that.
D
All
right,
I
would
say:
I'll
drop
a
link
but
as
I'm
doing
sober
so.
D
Xps
there
we
go
next.
Js
is
a
framework
with
server-side,
rendering,
okay,
implicit
routing.
You
just
have
to
create
a
page,
and
it's
implicitly
linked
to
middleware
for
trying
to
get
back
to
the
Zone
here.
Yeah.
B
D
D
I've
used
it
for
every
personally
launched
web
project,
I've
done
for
the
last
few
years.
It's
got
a
location,
optimization
for
various
mirrors.
It
doesn't
force
you
to
use
a
particular
UI
system
in
I
would
point
for.
If
you
wanted
to
look
at
a
particular
set
of
UI
components,
it's.
D
D
It's
it
has
some
ability
to
do
what
you
call
reactive
styling,
you
can
type
in
HTML
style
features
directly
into
the
components
like
height
width
overflow
without
having
to
Dash.
You
know,
keep
on
going
a
being
between
your
style
sheet
and
your
right
component
layer.
It
has
most
of
the
UI
components
you
need
for
any
sort
of
form
system,
so.
D
The
next
year,
I'm
currently
working
on
something
which
is
like
a
glyphy
analog
and
yes,
chakra
not
only
has
specific
documentation
for
how
to
integrate
itself
inside
of
next,
but
it's
either.
The
system
could
be
used
independently
and
also
as
I.
Would.
This
is
kind
of
a
a
side
vector
as
a
system
which
works
very
well
for
kind
of
like
putting
a
lot
of
data
into
say.
A
front-end
mirror
rxjs
is
a
great
state
system
that
works
well
with
chakra.
D
Next,
it
allows
you
to
use
things
like
index
DB
as
a
mirror
for
your
data,
so
you
could
do
local
transforms
and
search
in
detail
and
and
it'll
handle
a
lot
of
the
things,
including
observing
changes
in
the
data
layer.
Loading
in
you
know
a
schema
and
doing
a
lot
of
middleware
stuff.
Again.
This
is
something
could
be
used
to
swelt
as
well.
It's
felt
as
well,
but
these
are
some
of
the
utilities
I've
used
as
well
as
and
I'm
just
kind
of
like
dumping.
My.
D
Here's
like
for
some
things,
I've
done
in
terms
of
being
able
to
put
visualizations
up
both
SVG
and
when
it
comes
to
one
of
the
you
know
benefits
to
using
a
popular
language.
Is
you
get
things
like
sorry?
This
is
actually
what
I
meant
to
paste.
Svgr
is
a
system
which
will
convert
any
SVG
into
an
interactive
and
dynamic
react
component,
so
you
can.
D
Actually,
if
you
have
something
which
has
you
know,
a
fairly
complex
UI,
you
could
just
dump
an
SVG,
prelim
and
svgr
and
turn
it
into
a
react
component
and
it'll
bring
all
your
Styles
in
and,
for
example,
I
had
an
icon
that
I
wanted
to
be
able
to
change
color
when
it
hovers
over.
It's
very
easy
to
create
an
icon
and
then
expose
things
like
the
color
to
a
a
an
enclosing
context,
so
they
can
change
and
hover
over
or
potentially
like
scale
and
change
the
size.
D
D
Then
they
start
to
accommodate
each
other's
UI,
and
you
also
have
the
system
where
you're
likely
to
find
you
know
a
fair
number
of
people
who
have
used
them
in
combination
and
might
be
familiar
with
border
issues
yeah
if
there
are,
and
in
general
I
find
it's
always
a
good
idea
to
use
a
platform
wherein
if
you
do
paint
yourself
into
a
corner,
they
have
active
discourse
Discord
channels.
They
have
a
large
number
of
users.
I've
gotten
support.
B
Have
you
have
you
worked
with
any
of
these
with
like
a
d3s
or
viz.js
for
the.
D
Well,
I
mean
I've
done
a
couple
of
D3
injection
to
react
for
the
most
part.
You
know
it's
just
essentially
what
you
end
up
doing
is
they
have
a
system
called
reference
and
and
react
wherein
you
throw
up
a
Dom
into
your
template.
D
You
export
something
that
allows
you
to
refer
to
its
element
directly
and
you
pass
that
element
to
like
that's
how
I
do
the
first
thing
I
pass
in
the
SVG
JS
allows
you
to
use
like
vector,
commands
to
draw
an
SVG
like
from
scratch.
Yeah,
like
I,
said
I'm
working
on
a
glyphy
thing.
So
what
I
have
is
a
lot
of
down
boxes
and
I
want
to
draw
so
I,
throw
in
an
SVG
into
a
layer
which
is
again
overflow,
show
and
then
I
draw
my
lines
between
any
number
of
X.
D
Y
coordinates
and
jump
and
you're
done
and
and
that's
all
it
takes
and
all
right
fast
enough
to
be
responsive
with
a
mouse
when
I
start
dragging
the
Box
around
I
can
redraw
the
lines
and
it
shows
in
real
time
and
it's
practical
and
and
very
low
impact
on
terms
of
what
it
demands
from
the
browser
and
you
can
import
other
svgs
into
it.
So
these
are
the
sort
of
things
I
do
on
a
routine
basis.
You
do
extremely
fast
and
high
power
development.
Nice.
B
Which
one
do
you
recommend
to
start
with?
Is
it
the
next
JS
or
like
this.
D
Foreign
I
would
I
suppose
it
would
depend
on
what
sort
of
things
you're
most
concerned
with
performance
or
interface
elements.
D
Would
say
if
you
want
to
look
at
how
you
could
save
a
lot
of
time
in
terms
of
not
being
having
to
develop
custom
utilities
for
every
particular
interface
scenario.
Right
chakra
is
a
great
way
to
see
a
lot
of
things
you
can
drop
in
and
use
and
offer
off
the
cuff,
as
well
as
how
it
how
it
integrates
as
we
CSS
directly
into
the
markup
okay
cool
great
great
way,
to
see
how
you
can
rapidly
customize
and
tweak
a
visual
component
layer
without
getting.
D
What
do
you
call
kind
of
like
without
committing
to
someone
else's
very
specific,
look
and
feel
right.
A
good
example
for
that
is
you
create
a
Json
file
which
has
all
of
the?
What
do
you
call
conventions
at
the
top
layer?
It
presents
downwards
on
a
Dom
element
and
everything
inside
that
Dom
element
inherits
the
Styles.
D
You
define
I've,
been
able
to
define
a
whole
lot
of
colors
that
I
use
in
icons
and
such
into
its
color
Library,
which
allows
you
to
very
fast
create
a
shared
color
Library,
which
works
through
the
entire
application
tree
yeah
to
a
point
where,
for
instance,
if
we
then
wanted
to
do
a
reverse
interface
at
some
layer,
one
could
easily
see.
B
That's
right,
so
the
chakra
UI
would
be
would
be
one
of
those
would
it
be
the
next
JS
or
the
Shocker
UI.
D
Let
me
put
it
this
way.
If
you
want
to
kind
of
see
the
fun
Factor
chakra
is.
Is
a
nice
nice
Jam
in
if
you
want
to
see
kind
of
a
way
to
save
times
in
terms
of
routing
and
optimizing
stuff
on
the
server
and
basically
a
good
convention
for
page
layouts,
so
that
they
have
like
pages
and
then
layouts
which
wrap
around
the
pages
yeah
I
have
a
you,
can
have
a
shared
layout
for
the
entire
document.
You
can
have
custom
layouts
for
other
sub-components.
D
D
My
last
contract
was
with
armor,
which
is
a
Under
Armor,
which
is
a
fashion
system
out
of
east
coast,
and
they
they
use
the
hell
out
of
it
to
make
an
extremely
large
e-commerce
platform,
very
responsive
to
the
kind
of
work
they're
doing,
for
instance,
one
of
the
nice
things
about
it
is.
If
there
are
kind
of
like
Leaf
components,
you
don't
expect
to
be
required,
expect
in
certain
scenarios
you
don't
have
to
load
your
entire
application
single
page
immediately.
D
You
can
load
the
main
components
and
then
dynamically
load
sub-components
as
they're
needed
by
the
UI
right.
We
will
allow
you
a
faster
initial
load
time
and
they
have
whole
mechanics
in
there
for
that
a
mechanic
they
call
suspend,
which
is
the
leverage
stuff.
That's
part
of
the
basic
react
component,
but
it
shows
how
you
don't
need
to
go
like
div
dive
dive
into
webpack
in
order
to
minimize
the
loading
of
infrequently
used
components
and
increase
the
load.
Time
of
your
initial
hit,
perfect.
B
All
right,
I
will
take
a
look
at
those
like
that
sounds
like
a
good
good
way
that
we
should
look
at
going.
The
one
like
one
of
the
main
things
with
this
felt
was
that
it
had
a
bunch
of
pre-built
components
that
we
could
reuse
and
it
sounds
like
the
ones
that
you've
laid
out
here
are
have
that
same
functionality.
So
yeah.
D
And
I
am
not
trying
to
diminish
the
fact
that
stealth
is,
you
know
a
strong
platform
and
does
have
a
lot
of
good.
You
know
elements
to
it:
I'm,
not
I'm,
not
trying
to
diminish
other
systems
or
saying
if
I,
don't
you
know,
if
I
don't
get
my
tools,
I'll
I'll,
probably
go
home,
I'd,
be
happy
to
learn
and
pick
up
spelled
I'm
sure
it'd
be
fine.
I
am
just
concerned
that
we
as
something
that's
not
40
hour
a
week
job
for
any
of
us.
D
B
Totally
agree
and
thank
you
for
bringing
this
out
and
I
will
take
a
look
at
them
on
everybody
else,
poke
around
on
the
links
that
Dave
put
out
here
and
we'll
Circle
back
around
on
Discord
on
that
topic.
D
Sure,
and
and
I
also
I
mean
this
is
by
the
way.
None
of
the
the
only
thing
on
these
whole
rxjs
is
something
which
is
a
consideration
that
doesn't
depend
on
the
adoption
of
any
of
the
other
things
I've
put
forward.
It's
a
way
to
mirror
large
data
collections
in
the
client.
In
order
to
do
say,
you
know
a
quick
sort,
filter,
Atomic
operations
without
having
to
put
a
whole
lot
of
time
into
developing
a
client-side
database,
yeah.
B
I
think
the
biggest
thing
that
we're
going
to
have
to
figure
out
is
how
to
manage
large
lists
and
how
to
do
like
pagination
and
stuff
like
that
right
and
I,
don't
know
if
they'd
be
the
rxgs
or
some
other
like
in
our
current
UI.
We
use
datatables.net,
which
is
a
basically
a
jQuery
plug-in
so
but
I'm
not
I.
Don't
care
for
the
way
our
our
our
tables
working
handle
the
in
our
current
version,
right,
I
think,
there's
better
ways.
There's.
D
A
whole
table
Library,
which
essentially
wraps
around
the
HTML
table
that
I've
used
in
the
past.
There's
a
lot
of
good
table
stuff
out
that
just
discussing
tables
would
could
be
an
entire
meeting.
Oh
yeah.
D
There's
a
lot
of
options
as
a
kind
of
a
general
point
of
like
table
this
one
of
the
things
I've
found
extremely
effective
in
my
own
work.
D
Is
and
kind
of
pulling
up
a
guide
for
them
now
it's
right,
yeah
CSS
grid,
allows
you
to
do
a
lot
of
very
what
you
call
very
targeted
sizing
and
styling
of
grid
type
elements
in
CSS
using
a
a
browser
native
method.
D
So,
for
instance,
you
can
specify
columns
as
having
absolute
size
or
you
can
specify
them
as
being
okay.
If
you
have
like
three
absolute
size,
Columns
of
three
other
columns,
you
could
say,
I
want
one
of
the
columns.
C
is
50
of
the
remaining
space.
I
want
another
column
to
use
25
percent
of
the
remaining
space
and
then
or
20
units
of
a
remaining
space.
D
Now,
when
another
columns
use
15
units
of
remaining
space
so
that,
instead
of
having
to
do
a
lot
of
complex
math
in
terms
of
percents
and
figuring
out,
like
oh,
we
add
another
column,
I
guess
we
have
to
take
five
percent
off
everyone
right.
We
create
a
standard
Athena.
Every
every
free
column
uses
ten
ten
units
of
free
space
as
a
standard.
If
it's
a
big
one,
it
uses
20.
D
If
the
small
one
uses
five
and
then
if
you
add
another
one,
it's
just
another
10
units
of
free
space-
you
have
to
flip
around.
So
it's
a
good
way
of
styling
and
using
a
native
CSS
grid
system
to
to
rapidly
develop
a
lot
of
grid
components.
Nice
and
again,
this
isn't
something
that
depends
on
adoption
of
any
particular
framework,
whether
it's
felt
chakra
next
or
RX,
or
react
yeah.
It's
just
a
good
way
in
general
to
style
lists
on
the
browser
yeah.
C
We
have
to
find
a
library
for
making
the
dashboard
so
for
react.
This
is
the
react
admin
and
for
the
necklace.
We
have
lost
our
Alternatives,
so
we
have
to
choose
one
for
them.
B
Right
and
I
think
the
way
I'm
kind
of
approaching
the
development
is
working
backwards
from
the
detail
screen.
So
we'll
we'll
start
with
the
a
single
component
version,
for
example,
in
all
the
the
data
around
that
single
component
version
and
then
once
we
have
that
where
we
like
it,
then
we
can
work
backwards
to
the
lists
and
things
like
that
to
be
able
to
navigate
to
find
that
component
version.
C
Yeah
I
hear
that
demo
in
the
chat
can
it
okay.
D
B
D
Yeah,
there's
there's
ways
to
go
from
pigmented
reaction,
honestly,
the
way
I'm
doing
things
I,
don't
necessarily
know
that.
That's
that's
gonna
be
a
particular
great
time
saver,
so,
basically
I'm
a
big
fan
of
the
general
utility.
You
get
out
of
components
out
of
applications
like
Craigslist
and
Google,
and
so
my
general
approach
would
be
you
know,
do
a
searchable
list
of
the
various
top
tone
components
as
a
very
clean,
open
home,
page
yep.
D
If
you've
seen
the
top
header,
you
can
type
anything
you
want
and
it
doesn't
care
it
doesn't
matter
which
particular
School
of
things
you
and
then
you
do
a
you
know,
server-side
poll
of
all
the
applications,
documents,
environments,
components
that
have
that
in
them
and
then
by
clicking
on
say
a
domain.
D
You
get
a
easily
searchable
kind
of
tree
view
where
you
can
on
any
particular
place.
D
I
guess
this
should
be
both
I
there
we
go
so
when
you,
basically,
when
you
click
on
any
particular
component.
Not
only
do
you
see
its
children
immediately,
but
you
see
a
quick
list
of
all
of
its
immediate
content
and
then,
if
you
toggle
off
the
top
drop
down,
you
could
see
some
of
its
major
properties
again.
D
B
D
D
And
then
you
get
a
list
of
a
few
things
you
can
compare
and
if
you
see
down
the
below
the
Red
Dot
the
compare
element
yep
once
you
have
two
or
more
things
you
can
hit,
compare
and
go
to
computer
screen.
I
have
not
visually
drilled
down
to
that
layer,
but
it
kind
of
shows
you
an
approach.
Similarly
with
components
you
drill
down
into
a
component,
you
see
a
quick
pop-up
of
if
it's
got
a
parent
when
it's
parent
R,
what
it's
immediate
dependencies
are,
at
least.
D
Maybe
you
know
you
know
up
to
10
or
so,
which
particular
things
depend
are
using
it
at
a
component
layer
and
again
which
environments
it's
in,
which
applications
use
it,
which
domains
feature
it
as
a
quick
way
to
just
see
its
context,
not
an
infinitive
list,
but
just
a
list
of
say
the
top
20
or
whatever,
and
a
quick
way
to
toggle
over
to
its
properties,
to
see
some
of
the
statistics
about
it,
the
one
of
the
things
I
didn't
encounter
into
these
and
I,
don't
know
exactly
how
or
where
it
would
be
is
you
might
also
want
to
paddle
for
most
recent
deployments
but
I
think
that's
more
about
applications.
D
B
D
So
and
then
there
we
go
so
when
you
get
down
into
a
Explorer
list,
you
could
get
to
this
by
say
on
the
top
here.
If
you
were
simply
click
on
domains
or
environments
or
applications,
you
would
go
to
an
Explorer
list.
This
would
be
a
if
you
clicked
on
components,
but
not
a
specific
component,
just
an
alphabis
list,
with
the
search
again
the
search
ability.
All
these
drop
downs
are
showing
like
locked
in
an
open
position.
D
It
would
look
a
little
bit
more
like
this,
but
if,
for
instance,
you
go
and
you
Group
by
domain
here,
then
essentially
the
list
toggles
to
if
you
notice,
there's
no
hairlines
I
find
in
general.
Hairlines
are
just
visual
noise.
You
don't
need
right
and
the
deployments
then
will
Orient
around
the
domains
starting
by
domains.
So
you
can
see
how
the
components
fall
down
in
a
domain
by
the
main
level.
D
Again,
there
is
a
potential
that
if
the
list
becomes
too
exhaustive,
we
may
want
to
have
like
a
more
Link
at
the
above,
the
pink
line
to
show
a
domain
with
large
numbers.
One
scripture
most
of
them
have
yeah,
but
at
least
it'll
give
kind
of
a
a
starting
taste
for
how
these
things
play
out,
or
maybe
we
don't.
D
Maybe
we
literally
want
to
show
all
the
components
under
your
domain
and
just
use
like
Mouse
wheel,
scrolling
or
like
the
tab
down
button
and
again
any
one
of
these
can
components
can
be
dragged
down
into
the
by
the
component
name
down
to
here.
B
B
A
Now
I
just
want
to
let
everybody
know
that
I
put
put
in
the
chat
a
zoom
meeting
invite
to
continue
this
conversation
in
45
minutes.
D
A
If
you're
interested
in
digging
down
any
deeper
yeah.
D
I
only
have
like
another
15
seconds
left,
so
I
just
wanted
to
quickly
go
as
you
hover
over
any
of
these
headlines.
It
gives
you
an
option
for
agility
to
do
quick,
I
see
the
group
by
domain,
which
I
show
below
collapse.
Domains
would
basically
if
a
component
is
more
than
one
domain.
You
would
just
list
the
number
of
domains
by
here
and
and
the
ability
to
click
on
a
domain
either
filter
for
it.
D
D
I
haven't
actually
been
deployed
yet
which
you
could
again
use
as
a
focus
system
and
I
I
left
out
the
parent
component,
because
I
wasn't
completely
sure
how
informative
it
was
on
a
first
blush
list,
but
if
you
wanted
to
go
into
columns
and
add
it
back
in
or
if
you
wanted
to
remove
components
or
our
columns
to
reduce
your
visual
noise,
you
could
do
things
here
with
the
gear
system,
and
this
is
a
general
Motif.
We
could
use
for
all
the
grids
whether
it's
a
domain
grid
and
environment
create
an
application
grid.
D
Now,
once
we
develop
a
motif
and
a
system
of
filtration
one
could
easily
shop
drop
in
a
config
and
use
it
for
any
number
of
different
environments
to
make
sure-
and
that's
one
of
the
reasons
I
didn't
particularly
want
to
do.
Let's
drill
down
to
a
one
one
component,
one
system
and
build
it
to
death.
I
wanted
to
develop
a
visual
language
that
we
could
use
across
multiple
components
and
then
just
expand
it
with
a
configuration
by
configure
configuration
basis
for
different
scenarios
in
different
contexts.
D
So
that's!
That's
it!
That's
the
end
of
this
presentation.
Obviously
there's
a
lot
more
as
in
well
where,
where
the
properties,
when
you
click
on
an
element,
that's
Post
tracking
it
you
would
go
to
a
property
screen.
I
haven't
done
the
ux
for
that.
Yet
because
I
wanted
to
basically
do
a
strategic
to
Tactical
drill,
drown
of
just
the
first
two
levels
of
the
application.
A
And
more
to
come,
yeah
lots
more
discussion
on
this.
This
is
kind
of
an
important
topic
for
us,
because
we've
been
talking
about
you
know:
redoing,
the
the
UI
and
Dave
has
really
stepped
up
to
dig
into
it,
and
this
is
all
part
of
our
you
know
our
bounties
and
the
work
that
we're
doing
around
the
Ripple
Grant.
So
please
join
us
in
45
minutes.
D
C
A
So
yeah,
if
you
want
to
get
involved
in
you,
know,
working
with
Dave
on
this
effort,
be
sure
and
join
us
in
45
minutes
and
on
that
I
am
going
to
end
the
meeting
and
we
will
see
you
all
shortly,
possibly
or
not.
In
two
weeks.