►
From YouTube: Xenial - Layout Builders
Description
Click Here to Subscribe: http://xaf.life/35
Websites:
https://xafmarin.com/
https://www.xafers.training/
http://xafersweekly.com/
Facebook Group
http://xaf.life/4g
A
A
Layer,
builders,
tokens
extensions
carlions,
everything
is
focused
more
or
less
around
code
and
best
practices,
but
it's
mixing
in
all
in
together.
I
showed
the
last
time
model
builders
and
today
I
want
to
show
layout
builders,
which
is
a
a
way
to
to
build
your
layouts
in
code
and
not
in
the
designer
or
not.
The
model
editor,
and
I
also
want
to
show
off.
There
is
the
docs.
I
am
not
sure
if
they
were
online
the
last
time.
A
There
are
a
lot
of
topics,
it's
nearly
not
finished,
but
it's
like
all
the
kind
of
stuff
I
can't
describe
in
in
the
feature
center.
There's
also
the
feature
center
for
all
guys
who
are
more
interesting
in
more
visual
stuff,
like
the
editor
staff,
token
editors,
html,
google,
web
ui
and
the
batches
of
course,
as
you
see
here,
there's
a
lot
of
stuff
and
it's
getting
added
up
all
the
time.
A
A
Helps
you
adding
metadata
to
your
business
classes
and
your
and
your
and
your
classes
without
having
to
write
attributes
on
top
of
your
business
objects
or
domain
objects
as
a
call
next
thing,
and
the
next
step
is
like
layout
builders,
it's
like
a
dsl,
how
you
can
write
layouts
in
code,
so
they
are
refactoring
safe.
So
you
don't.
A
Break
your
replication
or
your
applications
layout.
If
you
need
to
refactor
or
rename
your
application
or
at
least
get
an
indicator,
if
you
refactor
your
code
or
rename
your
code,
how
much
impact
it
might
have
on
your
application-
and
I
am
just
currently-
we
are
looking
at
the
person
class
like
it-
would
be
always
so.
This
is
a
person
class.
We
have
like
a
person
with
a
first
name
and
a
last
name
image
address
one
address
to
an
address
collection
and
the
secondary
class.
It's
the
address,
sublist!
A
A
A
A
A
A
A
A
That's
if
you're
super
prepared,
so
it's
an
mpxf
application.
Nothing
there!
Okay,
that's
fine!
So
we
are
going
to
copy
all
that
code
and
it's
just
a
xpo
class.
So
nothing
special
here!
Well,
oh,
I
think
I
might
not,
but
I
I
will
leave
this
open,
so
we
have
our
server.
So
we
need
this
in
our
module
because
we
want
to
share
our
business
codes,
even
if
this
is
xav
only.
I
am
adding
a
new
class.
A
A
A
A
A
A
A
A
B
A
A
Okay,
now
we
enabled
the
builders
and
now
the
next
thing
we
need
to
do
is
we
need
to
define
an
attribute
and
I'm
just
copying,
pasting
it
and
I'm
just
following
along
the
docs,
because
I'm
no
coding
hero
at
all
or
keyboard
hero
and
what
this
says
is
like.
Okay,
this
is
the
the
detail
view
layout
builder
attribute
and
it's
following
a
convention.
So
there
is
this:
can
you
can
read
this
stuff?
Can
I
zoom
in
on
that
somehow
no.
A
A
A
No,
no,
it
was
an
example.
I'm
not
sure
it.
It's
that
stripes
it
out,
but
nonetheless
it's
talking
about
that.
If
you
have
a
function,
that
is
called
build
layout
and
it's
static
and
it
returns
a
layout
and
you
have
this
attribute,
then
it
will
build
your
layout
from
this
method
and
to
prove
it.
I
just
started
started
and
now
we
should
see
an
empty
layout.
A
Okay
with
the
person
that
is
a
new
and
now
it's
empty,
okay,
so
not
not
very
special
right
now,
but
that
that
also
means
it
doesn't
interfere
anymore.
If
you,
if
you're,
adding
new
properties
or
something
like
this,
this
is
like
the
golden
master
for
your
layout,
but
you
also
can
use
the
model
designer
to
add
stuff.
Later.
A
Okay,
now
follow
along
the
the
the
dogs
and
we
we
want
to
have
a
layer
to
look
something
like
this,
and
now
we
have
all
the
kind
of
stuff
that's
going
on
with
horizontal
groups
and
how
the
property
editors
are
are
aligned
with
each
other.
And
now
we
have
these
tabs
that
are
going
on
and
we
have
two
tabs
that
are
the
same,
and
we
have
the
list
view
that
is
going
on
and
I'm
just
going
and
copy
this
layout
and
don't
be
totally
scared.
A
I'm
falling
through
through
when
this
is
loading
and
just
don't
get
me
wrong.
So
we
have
our
image
editor
here.
That's
not
perfect
in
blazer,
with
our
full
name:
first
name
last
name:
email,
street
city,
postal
code,
state
province,
country,
and
now
we
have
here
the
exact
same
thing,
but
with
the
secondary
address,
and
now
we
have
our
list
view
okay,
and
to
show
you
that
this
isn't
a
foolproof
joke.
A
A
You
can't
do
this
this
in
in
windfalls,
but
nonetheless
that
the
layout
is
exactly
the
same,
and
that's
that's
basically
how
you
can
apply
the
layouts.
But
the
neat
thing
is
like
this
is
a
very,
very,
very,
very
verbal
syntax.
You
have
to
say
what
is
going
on.
I
want
to
have
the
horizontal
group
and
the
layout
property
editor
and
the
vertical
group
and
the
layer.
A
A
Is,
for
example,
those
two
tops
are
basically
exactly
the
same
or
should
be
exactly
the
same,
and
they
are
perfectly
exact
the
same,
but
one
is
for
one
and
two
is
for
two
and
you
can't
do
this
easily
in
the
model
editor.
You
can
do
it
in
the
tree
structure,
but
you
can't
do
this
really
easily
with
drag
and
drop
in
your
in
the
model
editor
and
also
they
both
should
look
the
same.
A
So
I'm
switching
back
to
my
solution.
13
and
you
can
see
we
have
like
one
primary
address
and
we
have
a
secondary
address
and
those
are
basically
totally
the
same
and
we
don't
want
to
repeat
ourselves,
but
the
only
thing
that
is
changing
is
this
number
part.
So
it's
address
one
and
address
two.
So,
okay,
let's
go
into
that
real,
quick
refactoring.
B
A
A
A
A
A
If
so,
you
can
say,
I
have
an
empty
space
item
and
horizontal
grow,
one
horizontal
tab,
blah
blah
blah
blah
blah
blah
blah
all
the
option
options
you
have
like
view
items,
property,
editor,
cultural
items,
all
that
kind
of
stuff.
Instead
of
remembering
or
looking
up
all
the
details,
you
need
to
follow
up
with
newing
up
new
objects.
A
A
A
A
Always
the
same
wrong,
and
it
totally
looks
the
same.
Of
course
it
produces
the
same
result
because
the
syntax
itself
just
produces
the
same
object
graph
and
for
the
very,
very
brave
ones,
and
I
am
not
going
to
show
this
life
right
now,
because
there
is
a
little
bit
of
or
is
it
there
a
little
bit
of
wrinkling.
We
can
just
try
it.
A
A
Me
that's
fine,
let's
do
the
the
no.
I
show
it
just
in
the
in
the
other
solution,
language
yeah,
it's
the
language
version
and
we
need
to
settle
a
bit
if,
if,
if
it
was
that
five
with
21.1,
I
tried
it,
it
works
out
of
the
box
where's
my
layout
thing,
oh
and
of
course
it
works
with
with
model
builders
as
well,
of
course,
so
you
can
combine
it
with
model
builders
as
well,
and
just
do
this
away.
B
A
Namespaces,
because
that's
a
neat
thing
about
functional
style,
you
don't
need
to
import
any
a
lot
of
of
namespaces
because
you
just
need
to
import
the
namespaces,
the
compiler
don't
know
the
types
of,
and
now
you
can
see
it's
like
mixing
up
all
this
kind
of
stuff,
but
it's
always
the
width
expression.
So
it's
it's!
The
property
editor
is,
is
returning
a
property
editor
but
you're,
adding
those
properties.
A
So
this
is
this
new
immutable
record
style
and
I
think
it
makes
a
really
really
neat
combination
between
readability
and
and
usability
from
a
developer
perspective,
because
you
have
real
break
points
and
functions
and
all
that
kind
of
stuff.
So
and
basically
that's
it
and
last
one
that's
for
the
ultra
brave
you
can
mix
them,
so
you
can
go
with
with
expressions
and
with
expressions
and
then
do
newing
up
stuff
in
the
middle
between
and
then
do
like
the
lumber
stuff
in
between.
B
A
Every
every
everybody
tells
me,
oh,
the
first,
this
first
syntax
was
nice.
Alex
was
telling
me,
oh
no,
he
wants
to
write
it
like,
and
it's
even
of
course
it
is
possible.
You
can
go
and
say:
okay,
I
don't
do
this
approach,
you
can
go
the
old
route
off
after
all
and
I'm
just
going
doing
a
backpack
back
back
back
back
back
back
to
this
arrangement,
and
this
this
thing
and
like
there's
a
var
layout.
B
A
Say
layout:
oh
my
god,
somewhere
my
keyboard
is
not
and
there's
a
ads
and
I'm
adding
this
and
now
I
return
the
layout,
and
I
think
this
should
work
and
what
will
happen.
It
will
be
a
layout
with
just
one
property
editor
in
it,
and
this
time
I
don't
miss
the
oh
and
now,
of
course
it
opens
on
the
right
screen.