►
From YouTube: YUI Open Roundtable August 15 2013
Description
YUI Open Roundtable August 15 2013
A
I
have
with
me
derek
from
the
yy
team
and
rashad,
who
is
our
intern,
and
we
have
a
number
of
things
to
talk
about
today
in
terms
of
order,
I'll
probably
do
demos
first,
I
think
that'd
be
usually
how
we
do
stuff
so
rashad
been
with
us
for
what
about
a
month
now,
three
months,
three
months.
Yes,
yes,
it
seems
like
it's
been
such
a
short
time.
A
A
D
Yes,
so
my
project
that
I've
worked
on
a
major
project
that
I
worked
on
all
summer
is
called
pearl
edit
and
it's
a
web
page
wizzy
way
where
you
can,
edit,
you
can
drag
and
drop.
You
can
drag
and
drop
different
elements
inside
the
dom
change
color
of
the
page
and
and
everything
is
drag
and
drop
interface,
where
you
can
rearrange
elements
and
notes
on
a
page.
D
So
here
the
concept
of
pearl
edit
was
to
give
those
developers
who
do
not
have
a
front-end
sensor
or
design
sense,
and
we
want
to
start
them
off
with
a
boilerplate
already
made
based
on
category
whatever
category
that
they
want
to
make.
Do
they
want
to
make
a
blog
a
a
marketing
page
such
as
this
one
or
any
other
type
of
layout,
since
designers
tend
to
follow
specific
patterns
on
how
they
want
to
design,
and
this
is
just
the
easier
user
interface
where
those
developers
can
make
quick
themes
on
the
fly.
D
D
And
there
you
go
it's
very
easy,
responsive,
very
fast
yeah
and
definitely,
I
would
say
using
yui,
allowed
me
to
build
this
project
and
get
as
far
as
I've
gotten.
I
don't
think
I
would
have
gotten
this
far
with
vanilla
javascript,
but
many
other
live
javascript
frameworks
out
there
and
I
have
separate
branches.
I
haven't
completed
the
project.
D
I
merged
everything
to
my
master
brand
to
github
so
check
out
this
branch
called
color
where
we
have
live
color,
editing
through
editing
the
background
of
color,
and
I
use
a
gallery
module
called
color
picker
and
see
everything's
real
time.
You
can
change
color
and
the
benefit
of
having
something
like
this
is
you
can
see
how
your
project
looks
in
its
in
its
proposed
environment,
where
it's
going
to
be
hosted
live
so
rather
than
send
it
through
code
or
send
it
through
this,
this
wild
user
interface
for
other
wysiwyg.
D
D
D
D
A
D
In
a
few
minutes,
it's
it's
really
easy
to
use
and
also
understanding
after
three
months
of
working
with.
Why
understanding
that
it's
more
than
just
a
simple
framework
or
a
library
that
you
couldn't
consider
it
a
full
front-end
stack
in
a
sense
that,
when
you
think
of
stack,
you
think
of
the
entire
project's
architecture
from
database
frontend
client
side,
but
with
yui.
D
So
if
you
have
a
new
project
coming
up,
would
you
use
white?
Oh
definitely.
If
I
was
building
something
large-scale
and
I
needed
structure,
I
needed
organization
and
building
something
to
maintainable.
Yui
definitely
would
be
a
go-to
and,
and
it
forces
you
to
use
some
of
the
best
practices
in
javascript
in
front
of
development,
with
a
sandbox
library
that
it
is,
and
also
using
delegation
that
I've
learned
and
also
using
a
framework
to
organize
my
code.
D
It
forces
you
to
be
organized
and
that's
something
that
any
I
guess
advanced
developer
would
love
to
have
and
if
you
are
user
out
there
and
want
to
build
something
large
scale,
you're
thinking
about
stretching
the
limit
I'll,
definitely
use
yui
and
it'll
help
you
in
your
development
process.
Well,
I.
A
A
D
A
Yeah
well,
like
I
said
I
want
to
tell
you
like,
on
behalf
of
the
team.
It's
been
great
to
have
you
here
and
I'm
glad
you've
been
able
to
learn
stuff
and
it's
very
gratifying
to
have
someone
who's
completely
new
to
not
not
only
the
yui
but,
like
you
know,
just
kind
of
front
end
stuff
that
recognize
kind
of
the
things
that
it's
offering
mm-hmm
yeah.
So
we
need
to
unclip
the
yeah
click.
D
Oh
yeah
yeah.
Definitely
I
learned
much
more
than
I
can
say
I
contributed
just
coming
in.
I
javascript
was
my
favorite
language.
I've
been
doing
it
for
about
a
year
out
of
school.
I
spent
like
all
last
fall,
trying
to
cover
the
advanced
topics
of
javascript
and
trying
to
learn
how
to
be
a
better
software
engineer
through
javascript,
and
I
knew
coming
on
a
team
that
builds
a
framework
itself,
a
platform
that
you
know
that
that
can
span
a
large
user
base
easily.
D
I
know
you
guys,
you
know,
had
to
follow
the
best
practices
and
emphasize
performance
and
code
structure
and
scalability,
and
I
wanted
to
learn
from
that
environment
and
see
it
from
a
different
scope.
You
know
a
different
front
front
and
you
know
different
front
end
work.
You
know
rather
than
building
user
interfaces.
I
want
to
see
how
it's
done
at
the
bottom
level
and
how
it's
built
did.
D
Yeah
I
looked
around
source
code.
Actually,
we,
a
pull
request
is
going
to
be
sent
tony.
He
tony
pip
can
help.
He
helped
me
develop
a
plug-in.
I
was
building
this
project
and
I
had
something
for
a
dragon
drop
delegate.
I
wanted
to
have
multiple
containers
using
the
delegate,
drag
and
drop
delegate
class,
and
I
told
him
what
I
was
using
it
for
and
he
explained
how
to
develop
a
plug-in
and
never
done
that
before
and
how
the
code
works.
B
I
guess
that
you'll
find
elsewhere
out
there
on
the
web.
So
I
don't
know
I
was
just
kind
of
curious
if
you
view
if
you
have
a
much
greater
understanding
of
javascript
at
this
point
or
if
you
view
the
language
any
differently
or
if
there's
a
lot
of
things,
you
kind
of
learned
about
about
the
language
itself.
Oh.
D
Absolutely
I
was
a
beginner
at
javascript
coming
I
I
was
basically
a
beginner
in
software
engineering
in
general,
I'm
still
young
in
my
cs
degree,
but
learning
how
to
structure
code,
how
to
build
scalable
code
in
a
professional
environment
with
learning
the
mvc
structure
through
javascript.
I
was
able
to
learn
that
there
are
development
patterns
out
there.
B
A
D
D
To
begin
with,
well
I
had
the
experience
for
object,
oriented
program
in
general,
but
not
much
for
prototyping
things
yeah,
like
I
said
when
I
started
learning
javascript.
It
was
this
weird
concept
at
first
I
tried
my
best
to
learn,
but
I
only
you
know
briefly
skimmed
it
to
the
most
part
where
I
can
talk
about
what
it
exactly
was
but
actually
implement
it.
That's
something
that
I
learned
how
to
do.
While
I
was
here
and
what
it's
used
for.
D
But
before
I
came
here,
I
never
built
a
large
scale
application
to
this
extent
and
that's
what
I
wanted
to
do.
That's
what
I
want
to
gain
from
here.
My
javascript
experience
was
just
basic,
dom
manipulation.
You
know
making
slideshows
changing
color
here
and
there
some
stuff
that
I
don't
want
yeah
jquery,
but
but
definitely
I
know
why.
What
is
what's,
why
ui
used
for
why
you
should
use
it
when
you
use
it
and
and
the
benefits
that
it
can
help
for?
Do
you
think
I
think
it's
helped?
D
I
learned
many
new
terms
and
many
new
concepts
here.
I
just
love
the
javascript
language
itself.
I
never
100
committed
to
a
library
in
particular.
I
just
want
to
be
an
explorer,
and
this
project
is
based
built
off
a
node.
So
I
had
experience,
you
know
working
more
with
the
back-end
side
of
things
using
express
js
and
higher
than
merge,
and
also
one
of
the
first
projects.
B
D
D
A
A
D
B
A
Questions
in
them
there
is
one
thing,
though,
that
that
I've
noticed
that
something
we
need
to
work
on
in
the
future
is
that
you
can
get
documentation.
Tells
you
how
to
do
something
right.
They'll
say
you
know,
call
this
method
but
like
when
you're,
when
you're
around
us
and
stuff
you'll
pick
up
like
a
higher
level
thing
like
this.
Is
this:
this
method
was
created
to
do
these
three
things
and
it's
meant
to
be
used
in
conjunction
with
this
pattern,
or
something
like
that,
and
that's
not
something.
That's
conveyed
that
well
in
the
documentation.
D
A
D
A
You
might
know
how
delicate
works
but-
and
you
might
see
an
example
about
it,
but
you
may
not
know
that
delegate
is
when
you
have
a
collection
like
a
list
of
things
and
you
so
the
bindings
you
know,
do
a
bunch
of
bindings
on
a
100
different
things.
You
just
bind
the
container
and
then
you
know
you
pick
the
element
inside
a
lot
of
people.
Don't
pick
up
on
that.
They
just
know
delegate
well,
what's
that
used
for
okay,
it's
not
anything
for
me!
So
I'll
skip
it
all
right.
D
A
Mailing
list
is
there
and
the
forums
are
there
so
feel
free
to
continue
on
it's
like
you
know,
the
difference
is
just
you're,
not
really.
You
know
space
and
time.
It's
basically
you're
asking
a
question
and
you
get
an
answer
the
next
day,
but
it's
still
it's
like
talking
to
people
who
are
very
slow
right.
C
A
A
So
all
the
check-ins
that
were
made
to
the
tree
until
last
evening
will
be
included
in
3.2.0
and
we
have
a
new
methodology
this
time
around,
which
allows
us
to
keep
the
tree
open
in
the
past.
When
we
were
doing
some
of
the
we're
going
through
the
release
process,
we
close
the
tree
for
two
weeks.
We
do
testing,
we
do.
You
know
browser
testing
and
we
fix
the
national
stopper
bugs
and
unfortunately,
for
the
rest
of
the
community.
A
Be
like
oh
yeah,
I
had
that
bug
fixed
and
I
don't
remember
why
I
fixed
it
so
now
we
have
it
where
the
trees
only
close
for
a
very
brief
time.
You
know,
or
even
instantaneously
and
we'll
have
our
release
branch
now
and
what
will
happen
now
is
we'll
be
doing
testing
on
release
branch
and
anytime.
We
fix
somebody
find
something
we
need
to
fix
in
there
we'll
check
it
back
into
its
requisite
branch
as
well,
and
then
that
will
be
the
release
candidate
which
we'll
use
to
eventually
release
3d.
A
So
how
long
is
the
release
branch
expected
to
live
for?
It
will
be
around
until
it's
until
these
days
yeah
and
then
it
will
go
away
and
all
that
any
changes.
Typically,
what
should
happen
is
anytime.
That
cinema
makes
a
change
to
the
release
branch.
It
should
merely
go
into
its
representative
branch
as
well,
but
if
not
it'll
get
resolved,
then
so
that
branch
will
go
away
so
we'll
stick
around.
A
Yeah,
whichever
right
imagine
that
aspect
of
it
since
we're
this
is
all
new,
we
haven't
got
that
part,
we're
still
sort
of
figuring.
That
out.
I
believe,
I
think
that's.
Ideally,
if
you
read
ryan's
original
posts,
you
know
there's
sort
of
this
simultaneous
thing
that
happens.
I
think
in
practice,
what
will
happen
is
they'll,
probably
be
near
the
end
of
the
testing
cycle.
They'll,
probably
be
some
things
that
are
not
in
sync
and
there'll,
be
a
synchronization
that
happens.
We
could
usually
just
kind
of
do
a.
I
think
it.
A
B
Yeah
yeah,
I
guess
we'll
kind
of
cross
that
bridge
when
we
come
to
it,
whether
we
merge
the
release
branch
back
in
or
not.
I
think
the
the
proposal
ryan's
proposal
says
to
just
kill
it
and
not
merge
it
back
in,
but
I
don't
know-
and
ideally
it
probably
wouldn't,
even
matter
whether
it's
merged
or
not,
because
you
should
have
commits
yeah
in
both
places,
so
it
shouldn't
actually
matter
a
whole
lot.
A
So
one
thing
I
want
to
go
over
briefly
with
with
everyone
here
is
some
of
the
features
that
are
in
this
coming
release
and
what
I've
done
is
I've.
I've
gone
through
the
change
history
for
all
the
components
in
the
library,
and
I,
if
you
go
to
the
wiki
page
you'll,
see
there's
a
3.12.0
change
history,
roll
up,
that's
pretty
much
how
things
will
be
if
there's
only
time
it
may
change.
A
A
There
is
some
chinese
region,
language
support,
added
to
calendar,
which
was
cool.
Thank
you
at
schuner
for
that
there's,
a
change
in
charge,
charts
that
added
logarithmic
scaling
to
charts
in
the
event
infrastructure.
There's
some
event
tap
editions.
You!
I
no
longer
breaks
the
browser
back
forward
cache
by
attaching
an
unnecessary
unload
event
handler
from
ryan
that
was
cool
and
what
that
means
is
it
won't
reload
like
if
you
go
to
the
browser
back
button,
it
won't
like
try
to
reload
it
again.
B
A
B
A
Things
like
that,
there's
changes
in
tab
view,
there's
a
bug
fix
for
missing,
aria,
roll
and
tab
list
and
template
the
template.
There
says
it
says:
an
added
central
template
registry,
the
template
registry
decouples
making
templates
available
from
invoking
a
template
to
render
it
the
central
registry
and
abstraction
templates
to
names
separates
concerns,
creates
a
level
of
indirection
and
enables
templates
to
be
easily
overwritten
and
then
there's
a
fix
in
tree
that
fixed
the
tree.sortable.
B
Yeah,
I'm
taking
a
quick
look
through
all
the
performance
metrics
that
we've
been
getting
so
looking
at
the
3x
doesn't
look
like.
We
have
anything
too
significant
in
terms
of
performance
improvements,
which
is
unlike
the
last
few
releases,
which
have
been
very
performance,
heavy,
so
yeah.
I
think
we're.
A
B
A
And
then
there'll
be
a
build
up
again.
Yeah,
yeah
and
also
what's
interesting,
is
what's
not
in
here,
which
was
actually
a
good
thing.
There's
a
bit
more
review
needed
for
the
remove
simple
yy,
which
will
be
most
likely
in
a
313
beta
and
then
tony
has
been
working
on
with
who's
it.
Alien
content,
editable
stuff.
B
A
Yeah
yeah,
so
that
that's
a
that's
a
potential,
something
that
could
potentially
be
in
a
313
beta
soon
and
then
there's
other
new
things.
But
the
nice
thing
is
that
people
who
are
who
are
out
in
the
community
or
working
on
features
are
not
blocked
by
our
release
process.
Now,
so
that's
the
biggest
change.
I
think
it's
the
most
impactful
change,
because
two
weeks
out
of
a
month
is
quite
bad
time.
It's
like
half
the
month,
so
yeah!
A
So
that's
all!
I
have
for
312
features,
there'll
be
a
blog
post
about
this
most
likely
tomorrow,
and
it's
going
to
be
just
what
I've
said
as
well
as
also.
If
you
want
to
try
this
out,
there
will
be
a
link
to
a
beta
cdn
link,
so
you
can
try
things
out.
The
beta
candidate
release
candidate,
as
well
as
the
staging.yylever.com
site,
has
been
updated
with
beta
code.
So
if
there's
additional
docs
they'll
show
up
there,
so
that's
all
I've
got
that's
right.
B
So
wiki
slash
development
schedule
so
yeah.
I
guess
yesterday
marked
the
code
freeze
for
sprint.
Nine,
so
upcoming
is
the
august
20th
commit
freeze,
poor
request
deadline,
so
any
essential
bug
fixes
for
the
312
release
will
need
to
be.
I
need
to
have
a
pull
request
submitted
by
august
20th,
which
is
next
tuesday,
tuesday,
I'm
guessing
yeah.
So
then
the
commit
freeze
deadline
is
august.
23Rd
and
the
release
window
opens
up
on
august
27th,
which
is
two
weeks
from.
Is
that
no
that's
not
correct
27th?
A
Yeah,
I
don't
know
recently,
it's
happened.
That
means
recently,
but,
like
I
think
of
months
ago,
it's
it's
certainly
sort
of
a
couple
rounds
and
the
interesting
part
is
those
those
were
delayed,
because
we
had
an
increased
testing
coverage
and
allowed
us
to
find
things
that
we
wouldn't
have
found
before.
A
B
C
A
B
A
B
Yep
that
one
is
on
my
list
of
button
button
issues
to
fix.
So
maybe
you
can
give
us
update
because
that's
like
you
have
soon
enough.
Yeah
been
working
on
some
other
non-button
related
stuff,
the
last
few
days
after
spending
some
time
last
week,
working
on
buttons,
so
yeah
anyways
buttons
certainly
going
to
get
some
some
some
love
over
the
next
few
weeks,
and
I
don't.
A
B
Two
is
to
get
to
the
point
where
we
can
remove
the
beta
tag
if
we
want
to,
and
but
at
that
point
we
can
just
kind
of
take
a
look
and
say
make
a
judgment
call
and
if
this
is
for
sure
the
api
and
exactly
the
in
the
the
correct
architecture
and
everything
and
then
if
we
want
to,
we
can
pull
it
off,
but
there's
some
steps.
We
need
to
do
to
get
to
that
point,
which
is
just
cleaning
up
some
of
the
lingering
bugs
with
buttons.
So.
B
Please
yeah
there's
a
threat
I
created
on
the
contributor
mailing
list
of
last
week.
I
believe
just
to
kind
of
collect
some
feedback
and
some
of
those
were
on
my
radar.
But
there
were
some
other
new
ones
that
that
were
brought
up
that
that
I
hadn't
put
too
much
thought
into
at
that
point,
but
yeah
certainly
collecting
any
and
all
feedback
about
button
to
kind
of
chart
its
course
to
the
finish
line.
A
Awesome,
well,
that's
all
we
have
for
this
week.
I
appreciate
everybody
coming
if
you
have
any
topic
at
all
that
you'd
like
to
talk
about
regarding
yui,
let
us
know
either
via
irc
or
message
me
directly
and
you
can
be
a
guest
on
the
show
and
I'm
sure
that
the
other
five
people
that
are
watching
will
appreciate
that
there's
and
if
you
have
any
ideas
about
things,
you'd
like
to
see
out
here
or
things
that
we
aren't
covering.