►
From YouTube: YUI Open RoundTable October 10, 2013
Description
YUI Open RoundTable October 10, 2013
B
Cool
we
caught
the
tail
end
of
your
conversation
at
the
beginning
of
our
yy
open
round
table
for
october
2013..
We
were
talking
trash
talking
all
kinds
of
people,
but
thank
goodness,
they're,
not
on
there
and
no,
we
weren't
really
so
today,
we've
got
a
number
of
things
planned
up.
It's
going
to
be
interesting,
but
first
off,
I
wanted
to
cover
a
few
housekeeping
chores.
Why
conf
is
coming
rapidly?
B
B
B
B
A
B
Yeah,
maybe
a
minute
you
can
tell
us
what
you're
what
you're
working
on
yeah
yeah.
So,
if
you're
a
speaker
right
now,
you
submitted
a
talk
proposal
and
you're
you're
watching
this
thinking,
you're
going
to
hear
some
more
information
about.
What's
going
on,
I
can
tell
you
that
you
will
hear
something
very
soon,
especially
post
the
deadline
from
what
I
know
right
now.
Jenny
has
like
a
big
trello
board
with
all
the
speakers
on
that
and
she's.
Getting
the
schedule
arranged
the
right
people
right
time
and
all
that
kind
of
stuff.
B
So
I
would
say,
there's
a
pretty
good
chance
that
if
you
did
submit
a
talk
that
you
will
get
to
talk,
I
don't
know
the
details,
but
it
will
be
barely
on
par,
but
we'll
fight
you'll
probably
find
that
next
week
and
then
so
going
into
that
we
were.
I
wanted
to
talk
a
little
bit
about
our
latest
release,
which
was
yy313.0
3.13.0,
and
I
have
asked
tony
to
come
and
talk
about
the
main,
the
main
sort
of
component
that
we,
the
main
drive
behind
this
release,
was
the
editor
stuff.
A
Was
my
turn
now?
Okay
yeah,
so
we
released
content
editable
into
editor,
it's
both
a
plugin
and
a
freestanding
component,
or
I
guess
a
pseudo
freestanding
component.
If
you
instantiate
inline
editor,
it
creates
a
base,
editor
and
plugs
in
the
content.
Editable
plugin
under
the
hood,
according
to
the
docs
that
we
wrote
up,
that's
kind
of
the
ideal
way
to
do
it,
but
there's
no
reason
why
you
can't
instantiate
a
base
editor
and
then
swap
the
plugins
and
or
plug
in
what
you
need
to
based
on
the
context
of
the
situation.
A
A
B
A
Yeah,
I
mean
what
the
styles
get
carried
over
every
everything
really
gets
carried
over
like
in
that
scenario.
If
you
went
to,
if
you
went
to
edit
a
page
and
you
had
you're
logged
in
as
the
admin
you
could
go
to,
the
blog
post
as
everyone
in
the
world
sees
it
and
click
a
button
that
would
say
edit
and
edit
the
page
in
line
with
all
the
rest
of
the
content,
and
then
you
know
hit
another
button
based
on
how
the,
however,
the
ui
would
be
set
up.
A
A
B
A
B
A
In
my
to
my
knowledge,
it's
resting
unless
we
get
some
pull
requests
or
bug
reports,
there's
been
a
couple
of
them
that
have
come
out
and
hopefully
people
in
the
community.
Can
you
know
hedge
from
that
to
get
those
kind
of
tweaked
out
and
leave
us
to
you
know
taking
taking
on
other
tasks
that
are
internal.
D
A
B
B
We
want
to
press
upon
the
fact
that
we
appreciate
every
all
the
work
that
you
do
and
all
work
you
continue
to
do
even
even
not
just
pull
requests
but
like
comments
and
forums,
and
you
know
I
went
back
and
saw
a
blog
post
that
he
wrote
like
you
know
two
three
years
ago,
you
know
still
like
you
know,
referenced
in
lots
of
ways.
So
I
want
to
give
a
big
shout
out
to
satyam,
because
you're
awesome.
A
Yeah
absolutely
yeah,
but
the
stuff
that
he's
put
out
there
for
data
tables
just
has
been.
You
know,
really
exceptional,
just
a
few
tests
and
maybe
some
documentation
that
I
have
to
write
for
it.
But
overall
it's
been
really
solid
and
you
know
that
it
makes
my
my
job
a
lot
easier
whenever
it's
just
testing
and
validating
community
contributions
than
having
to
to
come
up
with
all
of
these
features
on
my
own.
A
A
Oh
there's
one
one
thing
that
I'm
actually
working,
I
just
finished
up
writing
the
test
for
it
to
get
that
pulled
in
is,
if
you
render
a
data
table
with
a
fifty
percent
width.
The
data
table
itself.
The
table
node
is
actually
25
width
because
the
bounding
box
of
the
widget
is
50
width
of
the
container,
and
then
the
table
is
50
width
of
the
widget
bounding
box,
yeah.
B
B
B
B
A
B
B
C
C
C
One
post
and
that
actually
contains
a
full
change
log
of
pretty
much
everything
that
was
in
3.13,
so
just
quickly
running
through
it
yeah
there's
a
text,
editor
stuff,
app
framework
button,
widget
changes,
calendar
data
table,
oh
yeah,
some
stuff,
yeah,
so
lots
of
and
then
quite
a
bit
more
stuff
general
bug
fixes
and
everything.
So
yeah.
C
Yeah,
like
the-
and
I
think,
we've
talked
about
it
a
couple
times
in
the
past,
but
one
of
the
things
that
was
introduced
was
a
bug
fix
for
widget
that
allows
the
single
that
allows
single
box
widgets
and
it
doesn't
force
essentially
a
new,
a
wrapper
around
your
widget,
so
you
can
take
any
dom
node
and
in
a
way,
turn
that
dom
node
into
a
widget
while
preserving
all
of
the
original
html.
So
you
have
these
really
lightweight.
Markup
objects
that
have
a
ton
of
functionality
and
capabilities
with
them.
Well,
another.
C
I
mean
it's
been
in
there
since,
like
what
white
way,
3.2,
I
think,
was
when
I,
when
the
first
bug
report
for
that
came
in,
but
it's
just
never
never
actually
been
fixed
so
but
yeah
we.
So
we
got
that
fixed.
I
think
what
was
that
pull
request,
one
one,
two
five
so
yeah
now
you
can
do
single
box
widgets,
which
up
until
actually
fixing
that
I
didn't
realize
kind
of
how
how
cool
it.
B
B
C
Like
the
only
the
only
really
really
lightweight
widget,
the
first
time,
at
least
that
I
came
up
with
a
reason
to
have
like
a
very
lightweight
markup,
wise
widget
is
for
button,
because
I
didn't
want
a
div
around
a
button
element.
I
just
if
it's
a
button,
it
should
just
be
a
button
element,
but
so
all
of
the
other
widgets
that
we
have
in
the
library
we've
always
just
had
the
wrappers
around
it,
because
you
do
get
very
complex,
html
structures
for.
B
B
C
C
B
C
H
C
H
I
B
G
B
A
J
B
B
B
Yay,
but
it's
something
I
keep
putting
off
and
I
don't
put
off
anymore,
so
we're
going
to
go
through
that
pretty
extensively,
but
before
that
I
want
to
check
with
clarence
to
see
what
what
fun
things
are
going
on
in
clarence's
world.
Oh,
so
some
fun
things
well,
for
instance,
you
know
the
there's
a
lot
of
the
es4
stuff.
You
mentioned
some
of
this
before
but
and
you've
given
you've
been
here
roundtable
before
so
just.
H
So
yeah
with
some
of
the
interesting
things
that
are
going
on,
let
me
think
so
yeah
most
of
the
work
that
I'm
doing
right
now
is
more
of
how
you
can
integrate
yui
on
the
client
and
server
and
that
stuff's
going
with
some
of
the
new,
like
node.js
modules,
that
yahoo
has
been
releasing
on
our
github
account.
So
if
you
go
to
like
github.com
yahoo,
you
can
take
a
look
at
some
of
like
the
new
modules
I
released
there.
H
Most
of
the
things
we've
released
are
express
ions
and
what
you
can
do
with
those
is
that
they,
basically
let
you
it
basically
synchronizes
together,
like
things
are
going
on
on
server
and
things
that
are
going
on
in
a
client
and
the
idea
behind
that
is
what
we
want
to
do.
Is
we
want
to
just
like
get
rid
of
the
whole
idea
of
having
to
set
up
like
configuration
files
whenever
you
have
to
make
like
a
large,
wi-framework
app,
and
that
would
calculate
all
like
the
entire
configurations
set
dependencies
for
you.
B
H
B
H
And
so
like
the
ultimate
goal
that
we
have
like
right
now,
instead
of
like
we're
moving
away
from
like
the
mosquito
idea
of
keeping
everything
like
really
tightly
integrated
everything's,
like
you
have
to
use
yui
here,
you
have
to
use
the
yui
everywhere.
We
want
it
to
be
more
like
separate
components,
and
then
we
want
to
bring
those
separate
components
together
with
tooling
so
like
with
yeoman.
H
We'll
see
we
haven't
like
gotten
that
far,
yet
a
lot
of
them
are
pretty
production
ready.
A
few
parts
of
yahoo
are
already
using
some
of
these
like
open
source
components
that
we've
developed.
So
if
you
want
to
like
check
them
out,
they're
on
our
github
account,
not
the
yui
github
account,
but
the
yahoo
github
account
right,
cool.
B
Let's
just
dive
right
into
this
other
fun
thing
that
we're
going
to
do.
I
know
everyone
is
like
so
looking
for
this,
but
I
think
this
is
fun,
because
these
are
things
that
outside
contributors
have
worked
on
they've
sort
of
put
their
heart
and
soul
into,
and
I
think
it's
awesome
that
we
can
like
visit
these
and
get
them
moving
forward.
B
Oh
you
see
just
like
wow
that
one
is
still
open,
yeah
yeah,
so
if
you
see
anything
with
a
whip
on
it,
we're
gonna
ignore
those
and
if
it's
anything
by
an
internal
user
like
a
yy
user,
like
say
you
know,
derek
or
somebody
we're
going
to
ignore
those
too,
because
this
is
this
is
all
about
the
community
contribution.
So
the
first
one
that
pops
up
is
from
jslayer
or
js
layer.
B
I
can't
remember,
if
you
pronounce
it,
but
to
me
it's
something
more
like
j
slayer
as
an
awesome
name,
and
this
one
looks
like
there's
a
lot
back
and
forth
with
ryan
and
then
satyan
says:
hey
I'll,
take
a
look
at
this,
but
then
it's
nothing's,
not
here
anymore.
So
the
question
I
have
is:
where
do
we?
Where
do
we?
How
do
we
get
this
moving
again?
This
is
the
oldest
pull
request.
F
B
D
H
B
H
G
H
H
C
C
So
anyways,
what
what
this
is
doing
is
instead
of
pointing
to
the
build
and
the
source
directory.
We
just
want
to
point
yeti
to
the
source
directory.
So
that's
why
I
feel
like
this
fix,
probably
is
accurate,
we'll
just
have
to
kind
of
make
sure
that
and
follow
up,
because
there's
no
point
in
referencing
star
test,
slash
units
html
outside
of
the
source
directory,
so
right
yeah
right,
so
it
probably
makes
sense
and
should
probably
be
pulled
in.
B
H
I
think
this
might
be
better
as
a
plug-in
I
I
would
need
to
double
check
about
this,
but
and
eric
mainly
handled
modelsync.rest,
but
I
do
know
some
of
the
modelsync
stuff
since
I
didn't
milestone.local
but
yeah
I
feel
like
this
might
be
better
suit
as
a
plug-in,
rather
than
something
that
would
go
into
core,
because
it's
very,
I
feel
like
it
might
be
more
specific
to
rails.
For
instance,
it's
okay,
can
you
add
a
comment
about
that
yeah?
I.
J
H
Most
of
what
I
want
already
said
is
already
there
that
you
want
it
to
be
a
plugin.
Oh,
I
wanted
to
be
a
plug-in
yeah
yeah,
oh
yeah
and
ryan
seems
to
have
gotten
to
that
already.
In
the
first
comment:
yeah
a
rail,
specific
subclass
of
milestone.rest,
which
could
live
in
the
gallery,
yeah
and
yeah.
I
think
that's
my
personal
feeling
about
that.
One
too.
C
B
H
B
H
H
H
B
B
H
B
H
I
H
H
G
G
B
H
C
B
C
F
B
B
Yeah
yeah,
okay,
so
that
one's
cool
yeah
talk
there
all
right.
Well,
then,
that
covers
everything
that
I
have
for
still
pull
requests
and
we've
touched
on
all
of
them.
So
I
feel
better
about
that.
I
still
think
like,
for
instance,
602
is
just
still
kind
of
hanging
out
there.
Sorry
602,
okay,
yeah!
That's
the.
B
So
yeah
this
is
one
we'll
just
talk
to
eric
about
and
see.
If,
because
this
to
me,
I
feel
like
if
we
get
to
always
attack
the
oldest
pull
request,
then
we
can
can
get
this
list
pretty
short.
So
that's
that's
all
I
have
for
now
see
if
there's
anything
on
the
which
one
one's
asking
which
one
the
one
I
just.