►
From YouTube: YUI in the Wild #2: Interview with Mayumi
Description
Chatting about all things YUI
A
All
right
thanks
everybody
for
coming.
This
is
our
last
yy
open
round
table
for
the
year,
it's
thursday
december
19th
2013
and
I'm
happy
to
say
that
we
have
a
awesome
guest.
Today,
it's
nicole
from
rc
channel
and
from
the
y
white
community
she's
been
working
on
yui
since
with
yui
since
about
2008.
Is
that
right?
Yes,
awesome?
So
we
wanted
to
kick
things
off.
Maybe
tell
us
a
little
about.
You
know
what
you're
doing
and
kind
of
the
stuff
you're
working
on.
B
A
B
You
can
see
it
all
right,
so
I
think
some
of
you
guys
may
have
seen
this.
I
already
showed
you
guys
this.
While
I
was
working
on
it.
This
is
an
image
manager
for
rcms.
It
uses
yui
app
framework
model
model
list,
io
jsonparse.
It
uses
several
different,
yui
components.
It
offers
two
different
views.
This
is
new,
and
I
just
did
this
yesterday,
so
it
offers
this
kind
of
modernized
masonry
grid
pattern,
as
well
as
a
list
view
which
is
new.
B
You
can
see
when
you
scroll,
you
can
still
see
sort
of
hides
until
you
put
your
mouse
over
it.
I
had
a
lot
of
people
complaining.
They
wanted
this
because
they
wanted
the
functionality
to
sort
easy
and
just
look
through
things
easier.
This
was
kind
of
confusing
for
people,
but
I
mean
you
can
just
hover
over
and
it
pops
little
things
up.
B
Well,
our
admin
application
is
built
upon
yui,
there's
many
many
uses
of
it.
I
showed
you
guys
this
nifty
looking
thing
which
pretty
much
showcases
a
lot
of
modern
stuff
with
app
framework,
but
if
you
notice,
if
we
come
under,
like
a
pages
listing,
you'll
see
use
of
yy
data
table
with
automatic
search
filtering
which
uses
ajax
behind
the
scenes
and
there's
pagination
as
well,
but
I
don't
have
a
data
table
large
enough
online
development
server
to
show
you
guys
imagination,
but
you
get
the
hint
so
yeah.
B
We
have
many
many
different
listings
that
use
this.
We
also
have.
This
is
something
else.
Recent
too.
This
is
our
site
setup
tool,
and
this
is
geared
towards
people
in
our
office
that
need
to
build
out
sites
for
clients
very
quickly
because
they
didn't
want
to
have
to
go
through
and
set
up.
The
user
account
the
site
stuff,
the
dns
all
that
stuff.
Some
people
can't
do
that.
So
this
uses
that
framework
too.
We
can
check
off
things
that
we
want.
We
can
give
it
a
name.
B
B
And
when
you
click
this
step,
it
actually
goes
ahead.
It
copies
over
the
database
structure,
modifies
records
in
route
53
and
does
many
different
things
which
are
out
of
the
scope
of
this
conference,
but
it
uses
that
framework.
I
can
show
you
guys
some
code
if
you
want
to
see
that
or
we'll
look
at
the
image
manager,
that's
actually
a
little
more
exciting,
because
there's
there's
a
lot
more
going
on.
So
is
that.
B
The
image
manager
has
been.
I
made
an
image
manager,
the
first
version
about
a
year
ago,
and
it
was
it
wasn't
as
good.
It
didn't
use
that
framework.
It
was
just
pretty
crappy.
I
did
a
full
rewrite
a
few
months
ago
and
maybe
just
a
couple
months
ago,
and
then
recently
I
added
that
extra
view
that
I
was
showing
you
guys
over
and.
A
B
Wait,
that's
exactly
what
I
was
wanting
to
tell
you.
Guys
was
because
I
made
heavy
use
of
this.
It
was
extremely
easy
to
add
this
extra
view.
So,
if
you
look
here,
we
have
some
commented
code.
Here's
the
thumbnail
view.
This
is
the
original
view
which
does
not
use
the
data
table.
This
is
the
masonry
view
if
we
come
down
here.
Here's
our
list
view.
This
is
the
view
I
just
added
it's
a
pretty
short
view,
there's
really
not
too
much
to
it
and
then.
A
B
A
A
B
B
B
B
Function
and
this
is
being
called
after
this
is
successfully
rendered
and
the
reason
we
had
to
do
that
is
because
there
was
a
conflict
with
this,
with
an
order
of
operations
of
the
render
being
ran
along
with
the
view
render
being
ran.
This
was
running
before
the
view
was
finished
rendering
and
it
was
failing.
B
So
this
function
is
being
called
down
here
under
a
callback,
and
this
is
recommended
to
me
by
somebody
in
the
irc
chat
room.
I
don't
remember
who
it
was
exactly,
but,
as
you
can
see
here,
we're
loading
up
our
view
and
then
once
the
view
is
finished,
loading
we're
actually
running
that
post
render
function
which
is
going
to
then
render
the
data
table.
D
B
B
B
This
is
a
bad
one
to
look
at
if
you
come
in
admin
widgets
we
have.
This
is
a
progress
bar
widget.
We
built
that
extends
panel
and
adds
functionality
like
update
progress
so
that
we
can
instantiate
this.
It
shows
up
in
the
page
and
then
we
can
simply
call
update
progress
to
update
the
progress
of
the
bar
here's,
the
loading
bar.
It's
talking
about
all
sixtens
panel.
It's
very
simple.
C
B
B
F
B
B
D
B
Okay,
I
think
I
know
what
you're
saying
you're
saying
we
have
the
template
here.
That's
just
it's
only
here.
This
is
we're
rendering
the
panel
to
document.body
and
then
once
it's
rendered
we're
setting
the
template
from
this
and
then
we're
simply
re-rendering
the
content
here.
So
if
you
look
we're
setting
or
where
is
that,
I
got
it
okay,
so
when
it
initializes,
we
set
the
body
content
equal
to
the
template
thrown
through
handlebars
with
the
percentage.
B
B
G
B
G
We
wanted
to
have
something
like
how
grunt
lists
all
their
plugins
some
sort
of
a
place
where
you
can
discover
these
things
that
people
have
written,
but
then
there
can
be
multiple
variations
of
progress,
whereas
multiple
looks
and
fields
that
you
can
choose
from
and
at
the
same
time
you
can
kind
of
just
go.
Bower
install
xyz
to
get
whatever,
whichever
one
you
want.
So
that's
kind
of
what
we're
going
towards
not.
G
G
G
B
D
D
B
They
do
at
one
time
this
application
had
jquery
yy2
and
yui
3
running
and
prototype,
so
prototype
is
log
on.
I
know.
Prototype
is
long
gone,
we're
now
using
yui,
2
and
3.
Only
for
data
table
everything.
That's
yui
on
our
platform
has
been
replaced
with
version
three
from
version
two,
except
for
data
table.
A
B
In
some
of
our
modules,
we
make
pretty
extensive
use
of
it.
Things
like
inline
cell
editing,
I'm
trying
to
think
about
some
other
stuff,
the
the
list
of
events
and
functions
there
are
so
many
more
events
and
function
are
events
and
methods
for
version
two
than
there
are
for
version
three,
which
adds
to
flexibility.
D
D
B
B
It
would
be
pretty
helpful
and
like
for
people
that
are
new
to
yui
like
a
lot
of
applications.
There
are
a
lot
of
administrative
applications
that
need
data
tables,
complex
data
tables,
and,
and
you
know
this
is
one
of
them
and
we
haven't
upgraded
to
three
yet
because
we
just
haven't
really
pieced
together
a
solution.
A
B
Yeah
honestly,
it
held
us
back
for
a
very
long
time.
I
didn't.
I
was
originally
not
going
to
upgrade
us
to
3
at
all
until
there
was
a
more
robust
version
of
the
data
table
and
we
just
decided
to
go
and
go
with
that,
since
you
guys
ended
up,
dropping
support
for
two
altogether,
which
kind
of
leaves
people
like
us
in
the
middle
of
support,
because
we're
using
two.
We
don't
really
want
to
use
three
yet
because
we
don't
feel
that
it's
as
robust
as
we
need
and
then
two
is
no
longer
being
updated.
A
Right
because
then
you
have
to
go
back
to
the
drawing
board
and
say:
do
we
even
want
to
use
white
white
at
all?
We
want
to
just
do
some
other
things,
but
the
cool
thing
is
that,
like
the
module,
spec
that's
coming
out
soon,
a
lot
of
stuff
will
be
a
lot
more
modular,
so
you
can
make
those
choices
without
so
much.
You
know
you
have
to
worry
about.
Do
we
use
this
one
entire
framework
or
this
other
entire
framework,
we'll
be
able
to
use
bits
and
pieces
of
the
ones
you
like.
B
Right
exactly
and
that's
been
one
of
the
things
too-
that
we've
always
kind
of
hoped
and
wished
for
was
to
be
able
to
ease
more
easily
customize
some
of
these
widgets
to
better
suit
our
needs.
Things
like
you
know,
row,
folding
and
stuff
for
data
table
would
be
nice
to
see
you
know.
So
we
don't
have
to
click
into
things,
to
view
full
record
data-
and
I
know
there's
some
modules
in
yui
gallery
that
do
some
of
this
stuff,
though
those
are
worth
whatever
they're
worth.
B
Right
and
that's
kind
of
one
of
the
things
that's
held
us
back
from
for
so
long
upgrading
to
version
3
was
yoi2.
Was
this
all-encompassing
package
that
was
made
and
supported
by
a
large
company
and
then
yui
3
has
been
this
kind
of
mixture
of
this
product
supported
by
a
company,
and
then
you
got
all
these
gallery
modules
that
you
need
to
tie
in
to
do
some
of
the
more
nitty
gritty
stuff
or
you
write
your
own,
and
you
know
the
support
on
the
gallery.
B
We
we
are
very
interested
in
their
form
builder.
Actually,
however,
I
noticed
that
there's
this
weird
thing
with
aloe
ui,
like
their
website,
has
allo
ui
packaged
with
some
archaic
version
of
yui
three,
and
then
they
also
have
gallery
modules
that
I
suppose
are
supposed
to
work
with
any
version.
At
least
I'm
assuming
and
the
form
builder
is
on
their
website,
but
it
is
not
in
gallery,
so
we
have
been
dying
to
get
our
hands
on
that
for
a
while
to
use
that
and
replace
our
own
form
builder.
B
F
B
B
A
A
B
B
B
B
Because
the
last
time
we
looked
at
it,
the
reason
it
ended
up
getting
shot
down
was
we
would
be
loading
like
two
versions
of
yui
in
some
crazy
manner
in
order
to
use
the
form
builder.
So
if
we
don't
need
to
do
that
anymore,
if
we
can
just
download
their
modules
and
then
put
them
into
a
folder
of
some
sort
and
use
them,
we
would
be
very
happy.
B
B
A
E
B
And
honestly,
I
gotta
say
the
one
thing
that
helped
me
learn:
it
very
quickly
was
the
examples.
There
were
many
many
examples
of
every
single
thing
imaginable.
There
was
an
example
for
anything
you
could
want
to
do
and
those
really
really
helped
me
get
rolling
with
yui.
So
you
know
at
first
I
ended
up
piecing
together.
Some
of
these
examples
to
do
things
and
then
I
ended
up.
You
know
customizing
them
and
then,
of
course
eventually,
I
just
ended
up
writing
my
own
stuff.
A
E
D
B
A
Coming
year,
I
want
to
start
working
more
toward
that,
like
having
like
templates,
that
you
could
start
from
like
here's
a
basic.
You
know:
here's
a
hello
world
kind
of
thing,
because
I've
seen
even
even
the
examples
we
have
a
lot
of
those
are
kind
of
kitchen
sink.
Where
it'll
be
like
here's,
how
you
do
this
thing,
but
then
it's
got
all
this
other
code
in
there
like.
Well,
what
in
the
world
is
all
this
other
stuff
doing?
B
B
There
was
a
to-do
list
and
a
repo
list
or
something
like
that,
and
they
were
both
very
lengthy.
There
was
very
lengthy,
but
by
nature
apps,
I
suppose,
can
end
up
being
lengthy,
but
I
remember
it
being
a
little
confusing
is
to
have
some
of
the
stuff
was
working
together.
It
took
me
a
while
to
piece
together
my.
A
H
A
B
A
Yeah
and
that
could
even
be
solved
just
by
a
sheer
number
of
examples,
because
you
can
see
the
commonalities
between
them,
you'd
be
like,
oh,
I
always
have
to
have
you
know
this
include
and
always
have
to
include.
You
know.
You
know
you
know
whatever
your
whatever
template
stuff,
you
have
to
do.
That's
the
same,
so
yeah!
A
A
A
C
A
Yeah,
I'm
almost
like
code
listings
like
here's,
you
know
we'll
use
it
like
almost
when
you
do
like
a
help
for
a
certain
command.
It'll
give
you
like
here's.
What
great
example
yeah
they're,
not
as
cross-referenced
as
they
could
be
too.
It
could
be
like
you
know,
go
see,
lioness
and
get
up.
You
know
tell
exactly
what
you
know:
that's
cool.
B
It
was
it
wasn't
too
bad
before
we
or
about
the
same
time
we
were
doing
that.
We
were
also
removing
prototype,
which
was
a
bit
of
a
nightmare
because
it's
not
as
easy
to
refactor,
especially
when
it
uses
the
dollar
sign,
which
is
the
same
thing,
jquery
uses
and
it
prototypes
itself
onto
base
objects,
so
that
was
kind
of
a
disaster
upgrading
to
3.0
wasn't
too
bad.
B
We
kind
of
did
it
piece
by
piece
and,
like
I
said,
we're
actually
still
using
2.0
for
for
data
table,
paginator,
autocomplete
and-
and
I
think
that's
it-
everything
else
we've
replaced,
though,
with
yui
three
and
it
I
honestly
can't
say
we
had
any
bugs
that
made
it
out
without
anybody
catching
them.
So
it
was.
It
was
pretty
easy.
G
B
I'm
pretty
sure
in
this.
This
is
a
very
large
application.
I
am
pretty
sure
that
we
are
not
using
any
jquery
plugins,
except
for
anything
for
bootstrap.
However,
there
are
little
snippets
of
miscellaneous
jquery
code
here
and
there
that
other
people
have
wrote
in
the
past
that
are
still
there
for
very,
very
simple
stuff.
B
B
A
B
Well,
we've
just
finished
a
lot
of
work
with
our
refactoring
to
version
three,
and
I
just
finished
the
next
round
of
updates
for
our
image
manager.
It's
hard
to
say
what
could
end
up
being
next,
I'm
actually
gonna
have
to
go
and
have
a
meeting
with
some
people
here
and
see
where
we
need
to
go
with
future
modules.
B
A
B
B
A
G
B
Okay,
so
we're
using
yy3
and
we're
using
two
and
three
for
two
and
three
we're
using
2.9,
which
is
obviously
the
last
version.
I
think
that's
the
number
and
we're
on
3.14.
We
try
to
update.
We
try
to
update
as
quickly
as
possible.
We
see
you
guys,
launch
a
new
version.
We
try
to
get
on
that
and
usually
we
do
it
pretty
quick.
So
usually.
B
B
A
Cool
well,
thank
you
so
much
for
coming.
I
know
that
everybody
here
is
like
squeezing
their
schedules
in,
so
I
wanted
to
tell
you.
I
really
appreciate
you
showing
us
what
you've
been
working
on
and
look
forward
to.
Let
us
know
if
we
can
help
at
all
with
the
talking
with
aloe
folks
and
I'll
also
follow
up
with
tony
on
the
daily
table.
Stuff.
B
D
A
E
A
Which
was
a
fixed
charts
issue
and
some
other
addison
support
for
target
environments,
ie11
and
android,
4.4
and
yeah.
That
was
really
good
yeah
for
travato,
saying
it's.
It's
interesting
how
the
people
are
using
yy,
though
that's
also
really
eliminate
for
me
too,
to
see
you
know.
You
always
have
this
in
your
mind
of
how
you
expect
people
to
be
using
the
product,
and
then
you
you
actually
see
the
code.
It
also
feels
that
that
you
know
I
think
we're
watching.
A
G
G
I
just
wanted
to
end
before
we
go
like
saying
thanks
to
andrew,
actually
for
setting
these
up
and
and
making
a
whole
host
of
different
roundtables,
all
of
which
have
been
like
interesting
and
have
had
good,
like
diversity
in
topics.
So
thanks
a
lot
for
setting
up
these
round
tables
and
making
them
such
a
success.
Thanks
and.