►
From YouTube: YUI Open RoundTable 03/14/2013
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
Hey
everybody.
Welcome
to
our
latest
yui
open
roundtable
day
is
thursday,
the
14th
march,
one
of
their
team,
and
we're
going
to
kick
things
off
with
the
number
of
folks
who
may
or
may
not
have
demos
depends
on
if
they're
here
I
know
dave.
You
said
something
about
one
bit
about
rent
you
want
to
talk
about
that
now.
Are
you
will
mate
yeah?
I.
A
Usually
have
America
to
folks
are
getting
the
invites
and
puffing
on
the
channel
home.
If
you're
watching
this
video
offline,
we
have
I
site
on
the
github
wiki
called
round
table
topics.
That
is
the
location
for
you
to
add
any
kind
of
discussion
item.
Do
you
want
to
add
for
any
given
around
him
so
this
week,
I
have
one
question
on
there
we
may
or
may
not
have
some
demos
and
then.
C
A
B
Right
so
I've
gotta
open,
pull
request
that
changes
our
build
system
over
to
grunt,
instead
of
a
bunch
of
antiquated
ant
files
and
make
files
that
we've
had.
B
So
the
background
is
that
we
have
a
set
of
ant
files
that
we
run
under
Hudson
that
generates
one
of
our
that
generates
our
actual
release,
which
is
the
zip
file
that
has
the
API
Doc's,
the
selic
Doc's,
the
built
files.
The
tests
read
me
all
that
good
stuff,
but
it
also
generates
our
CDN
deployment
as
well.
B
So
the
zip
file
that
we
then
tossed
up
under
the
CDN,
so
I
really
really
really
hate
aunt,
so
I've
written
a
module,
an
NPM
module
based
on
grunt
that
contains
all
the
various
tasks
we
need
to
actually
do
a
full
release,
which
means
that
any
developer
can
do
a
full
Yui
release
directly
from
their
their
own
machine.
So
it's
not
tied
to
any
of
our
build
servers.
It
just
generates
all
the
the
zip
files.
B
B
So
this
is
a
fully
qualified
NPM
package
that
can
just
be
NPM
published
from
right
here,
including
the
version
numbers
and
everything
that
it
needs.
You
see
there
actually
has
the
versions
in
it,
so
it
does
all
the
hard
work
of
replacing
like
the
at
version
at
in
all
the
files
does
all
the
CSS
post-processing
for
the
CDN
to
get
rid
of
all
the
relative
paths.
Things
like
that,
and
it
takes
about
eight
minutes
to
generate
a
fully
qualified
release.
B
It
also
has
some
shortcuts
in
it
too.
So
if
you
just
type
grunt
here,
we
have
a
main
grunt
file
that
sits
right
here
in
the
directory.
That
has
all
the
the
simple
tasks
in
it,
so
it
uses
it
uses
like
we've
got
their
syntax
in
here
for
like
creating
this
stamp,
the
copyright
stamp
that
goes
across
the
top
with
the
year
and
the
version
and
the
build
numbers
and
stuff
plus
it
uses
like
built-in
grunt
tools
to
the
zip.
So
it
creates
the
zip
files
with
the
right
stuff
in
them.
B
Now,
if
you
just
like
grunt,
it
actually
shows
you.
We
have
a
grunt
build
task
which
is
basically
yogi,
build
under
the
hood,
so
this
actually
has
just
a
bunch
of
shortcuts
to
our
normal
tools.
So
if
you
do
a
grunt
test,
it'll
do
a
yogi
test
under
the
hood
there's
a
couple
of
quick
tips
in
here
for
like
grunt
Travis,
which
will
perform
actually
the
Travis
build.
B
So
we
can
put
that
into
the
Travis
config
and
when
it
runs,
it's
actually
going
to
run
a
grunt
Travis,
so
I'm
just
trying
to
shortcut
all
these
things
down
into
really
small
things,
so
that
they're
very
easy
to
do.
You
can
do
this
type
like
grunt
test
CLI
and
it's
just
going
to
run
yogi
test
with
the
CLI
parameters
on
it.
You
know
it's
pretty
simple.
It's
just
that.
It's
wrapping
a
couple
of
these
things.
A
B
No
real
reason
to
do
a
dry
run,
because
the
to
do
a
dry
run
is
basically
to
do
a
build
right.
You
know,
so
the
zipping
doesn't
really
take
that
much
it's
the
prep
beforehand,
which
is
to
run
all
the
tests,
do
a
full
build
on
or
do
a
full
build
on
the
entire
library.
So
the
other
goal
this
is
going
to
do
is
to
get
rid
of
our
build
directory,
because
we
actually
have
a
official
way
said.
E
B
E
B
So
what
I'm
trying
to
work
out
now
is
the
proper
routine,
because
you
have
to
still
remember
that
you
need
to
run
a
couple
of
commands
before
you
can
run
your
tests
mm-hmm.
You
know
so
like
if
you're
working
on
something
like
say
I
owe
or
YQL
that
has
both
node
and
browser
based
tests.
You
not
only
have
to
run
your
I/o
bill,
but
you
also
have
to
run
an
NPM
built
real
quick
to
to
sync
up
that
source
tree
right.
B
A
B
Was
overwhelmingly
for
grunt,
even
though
I
prefer
Jake,
because
I,
like
my
mic
files,
we
went
with
grunt
anyway,
but
I
still
had
a
long
road
to
get
to
that
point.
You
know
props
to
the
grunt
guys
for
helping
me
out
with
that.
We
had
some
licensing
issues
with
a
couple
of
their
modules,
but
now
I
can
use
them.
I
also
went
through
the
entire
library
and
removed
every
make
file
and
replace
them
all
with
grunt
files,
so
handlebars
normalize.
B
B
The
other
thing
this
changes
to
is
that
changes.
A
lot
of
the
sorcery
that
went
under
our
npm
build
so
there's
an
actual
package.json
file
that
sits
in
the
main
route
and
it
has
a
post
install.
That's
it
that
does
a
grunt
build.
So
when
you
say
NPM
I
to
install
Yui,
it's
going
to
go
out
and
get
grunt
it's
going
to
get
all
of
our
dependencies
and
then
it's
going
to
run
a
grunt,
build
to
sync
up
the
build
directory,
and
then
it's
going
to
run
a
grunt
test,
I
believe
yeah.
B
So
then
it's
got
an
NPM
test
of
being
grunt
test,
so
you
actually
have
n
PMI,
which
will
go
through
and
sink
the
whole
source
directory
and
build
everything
for
you.
And
then
you
can
do
an
NPM
test
and
it's
just
going
to
run
grunt
test
under
the
hood.
So
it
kind
of
sinks
this
up
with
like
what
a
real
node
package
should
look
like.
B
Spread
it
should
land
sometime
next
week.
It's
actually
already
in
sync,
with
master
I,
just
pulled
that
this
morning
there
was
a
couple
of
bugs
introduced
in
node,
0
10,
not
technically
bugs,
but
still
they
broke
some
things
so
I'm
trying
to
go
through
and
clean
them
up
is
that
I'm
hoping
to
hoping
to
land
it
next
week
so
that
we
can
have
a
stable,
Travis,
build
and
stable
builds
and
then
once
that
lands,
then
we
can
start
dropping
the
build
directory
in.
B
Yes,
they
could
pull
down
the
git
repo
and
then
they
could
just
remove
the
things
they
want
to
remove
and
they
could
add
in
the
things
they
want
to
add
in
and
then
just
run
a
grunt
build
and
it
will
build
it.
Cool
I.
Think.
That's
kind
of
the
that's
kind
of
the
goal
is
to
get
to
that
point
where
these
tools
just
work
and
it
just
it.
You
know
that
they
build
their
release.
The
same
way.
We
build
our
release
right.
B
So
so
what
I'm
going
to
do
is
I'm
going
to
actually
generate
a
390
dash
grunt,
that's
from
the
same
tag.
The
390
was
generated
and
I'm
going
to
deploy
that
to
the
CDN.
So
then
you
can
just
go
390
dash,
grunts
and
be
done
with
it
and
then
run
it
and
make
sure
everything
is
exactly
the
same.
I'm
doing
a
bunch
of
verification
under
the
hood
to
make
sure
that
it
worked,
but
I
want
to
make
sure
that
everything
is
spot-on
and
you
know.
B
Hopefully
this
will
allow
us
to
have
really
fast
builds
because
one
of
the
other
things
it
does
is
you
can.
When
you
do
a
grunt
release,
you
can
specify
the
version
number,
but
if
you
leave
off
the
build
number,
it
just
grabs
the
shock
so
that
we
have
a
way
to
identify
exactly
where
that
build
was
generated
from
which
would
be
really
nice
to
like
I
said
once
Travis
gets
artifacts.
B
A
B
A
D
A
Movies,
well,
why
you're
here
and
I
know
you
you
may
have
to
drop
off
them.
I
know
that
this
questions
been
asked
a
hundred
times
and
it
was
from
round
table
page
I.
Think
it's
specifically
about
the
yogi
stuff,
but
I
think
it's
a
there's,
a
bigger
question
behind
us
and
I
had
to
do
with
someone
asked
about
the
gallery:
module.
A
And
this
is
specifically
about
the
about
that
question,
but
one
of
the
things
I
want
to
ask-
and
we
mentioned
yesterday
last
and
we
came
up-
was
them
there
are
topics
and
their
goals
of
the
y
ye
project
that
aren't
necessarily
specific
to
any
one
person.
So
people
are
asking
it
is
there
anything
that
they
can
do
to
help
you
with
the
gallery
project.
That's
the
bigger
question.
Yeah.
B
So
we
we
talked
about
that
at
the
last
round
table
is
the
fact
that
I
can't
open
source
the
website.
So
I
can't
let
anybody
else.
Do
it
all
right
and
it's
just
it's
on
my
list
and
I
know
I
need
to
do
it,
but
I'm
a
little
swamped
at
the
moment,
but
it's
it's
there
and
it's
getting
really
close.
We
just
we
had
a
big
update
to
the
site
for
this
release.
B
A
B
The
what
what
really
helps
is
for
them
to
actually
convert
their
modules
over
and
have
their
documentation
set
up
in
a
yogi
for
module,
so
if
they
have
their
docs
and
their
api
docs
and
everything
in
place
with
the
new
modules.
That
will
make
it
much
easier
for
me
to
just
flip
the
button
and
import
these
things
in
okay,.
E
B
The
whole
point
is:
is
that
those
modules
look
exactly
like
our
Yui
module,
so
there's
not
a
whole
lot
of
tweaking
I
have
to
do,
but
there's
a
couple
of
things
in
the
backend
of
the
site
that
I
have
to
do
because
Yui
itself
doesn't
like.
We
don't
have
singular
clap
or
more
than
one
class,
so
we
always
have
one
class,
a
specific
class
name.
That
goes
on
the
specific
name
space.
But
the
gallery
is
a
different
story.
You
could
have
three
YQL
modules
in
there.
B
You
could
have
five
charts
modules
in
there
are
seven
calendars
or
four
accordions
and
they
all
use
the
same
namespace.
Well,
the
problem
is
that
really
screws
with
like
why?
Why
doc,
because
Yui
doc
doesn't
understand
that
you've
got
two
classes
with
the
same
name,
because
that's
just
yo
wrong.
So
we
have
to
figure
out
how
to
namespace
these
things
correctly
so
that
they
show
up
in
the
API
Doc's
they
show
up
in
the
search
and
everything
else.
So
I
have
to
do
some
data
munging
and
it
just
it's
kind
of
like
trial
and
error.
B
Is
a
feature
that
somebody's
asked
for
and
I'm
working
on
it
I
just
haven't
implemented
the
API
art
of
being
able
to
assign
it
I
want
to
follow
the
path
that
NPM
had,
which
is
the
ability
to
add
more
than
one
owner.
So
then,
theoretically,
you
can
have
the
original
owner
assign
this
to
add
somebody
else's
an
owner
and
then
delete
them
self.
Great.
A
H
Yeah
I
didn't
want
to
show
the
site
yet
because
I
wanted
to
and
I'm
just
kind
of
speaking
for,
like
I
was
just
talking
to
Eric
and
Jeff
in
the
room
to
which
is
good.
But
we
were
thinking
that
we
should.
We
will
show
the
site
once
it's
fully
done,
because
it's
not
totally
done
yet
so,
as
for
as
for
the
CSS
stuff
that
I'm
working
on
they've
been
in
gallery
for
a
while,
though,
in
fact
I
think
there
was
a
gallery
pushed
yesterday.
H
Obviously
we're
going
through
some
code,
reviews
and
stuff
like
that.
So
there
are
some
small
things
that
will
change
and
I
kick
mostly
mostly
class
names
to
be
becoming
less
semantic
arm.
Stink,
changes
things
such
as
changing
form,
horizontal
to
form,
aligned
or
form
vertical,
or
something
that
to
form
stacked,
or
something
like
that.
So
there's
some
class
name
change
that
are
going
to
happen,
but
it's
a
little
early
just
exactly
what
those
are,
because
we're
still
going
through
the
code
review
phase.
H
As
for
ya,
as
for
everything
else,
I
mean,
apart
from
the
390
CSS
stuff,
I
think
the
rest
of
the
site
stuff.
We
just
just
hang
tight
because
I
I
I'd
like
to
show
it
all
at
once.
It's
sort
of
like
one.
A
H
We
are
actually
still
not
one
hundred
percent
on
that,
because
there
are
well
after
at
a
certain
point.
Grouping
class
names
does
make
sense,
especially
if
you
want
to
do
a
lot
of
permutations
and
combinations
of
different
styles.
H
I
know,
Jeff
and
I
have
talked
a
little
bit
about
this
with
some
other
people
at
Yahoo
who
have
been
working
on
CSS
offerings
so
for
the
purposes
of
Yui,
CSS
I,
don't
think
it'll
change
much
from
what
it
is
right
now,
which
is
a
kind
of
a
more
come
on
smoke
kind
of
a
more
combined
structure
but
but
yeah
it's
still.
It's
still
something
I'm
talking
to
Matt
about,
and
that's
one
of
the
things
we're
looking
at
for
the
code
review.
Okay,.
A
H
Just
I
would
just
ask
so
like
the
new
CSS
gal
modules
are
in
the
gallery,
but
there
have
been
using
yogi,
so
they
don't
actually
show
up
on
the
gallery.
So
I
think
the
best
thing
is,
but
they
are
on
on
my
they're
on
there
on
my
github
and
if
you
do
a
yogi
search,
CSS
form
or
yogi
sir
CSS
list,
they
do
show
up
there
and
the
best
way
to
find
X
get
to
the
Miss,
probably
through
my
through
my
github
directly.
H
So
if
people
are
and
people
have
been
using
them
and
people
have
been
all
giving
me
feedback
on
some
stuff.
So
that
really
helps
because
that's
going
to
help
bake
it
out
even
more
when
it
comes
when
it
would
be
actually
launch
everything
together.
So
that's
really
the
best
wait
till
I
contribute
to
the
stuff.
Okay,.
A
A
The
first
one
that
kind
of
comes
up
that
has
a
phone
that
that
we've
been
talking
about
a
little
bit.
Is
this
fix
for
the
wrong
event?
Names
fired
by
Swift
event
handler
and
that's
for
quest
for
28,
and
basically,
what
we
were
originally
discussing
was
getting
Allen
to
respond
to
this
person,
but
he
hasn't
had
a
chance.
Yet
so
I
have
an
open
question
for
folks
here
like
where
should
we
take
this?
A
A
E
A
A
The
only
thing
is
this
is
someone
from
the
community.
They
may
not
have
any
idea
that
we're
looking
into
it
I.
H
Have
a
I
have
a
bog
filed
against
this
in
general,
but
I
haven't
got
a
chance
to
get
go
into
it
yet
the
whole
look
for
I.
Think
I
brought
this
up
during
last
week's
thursday.
Just
listening
to
the
22
event,
listeners
I
think
I
can
reach.
Just
I
can
talk
to
said.
You
know
about
that,
but
I
have
a
bug
filed
against
myself
for
that.
Okay.
B
H
Because
this,
this
fix
actually
doesn't
do
anything,
because,
even
if
you
have
that
in
the
gesture
map,
there's
no
the
Jess
remembers
and
do
like
in
each
iteration
or
something
like
that.
So
it's
those
aren't
going
to
get
touched.
Okay,
so
I
I
can
just
I
can
close
this
in
and
point
him
to
the
bug.
Okay,.
A
Thanks
the
next
one
that
comes
up
is
the
power
quest
for
76
is
from
Eduardo
Lundgren
and
title
isn't
very
descriptive,
but
it
talks
about
heavy
source
code,
lengths
of
private
underscore
class
names
variable
and
its
method,
implementation
and
properties.
Initialization.
This
practice
doesn't
allow
class
extensions
to
overwrite
those
values
in
the
proper
way.
In
order
to
get
fixed,
it
needs
to
need
create
the
fresh
values
from
the
static
reference
instead
and
Dave.
A
A
A
A
A
B
G
A
B
A
H
F
A
A
That's
pretty
much
forced
to
stay
up
for
requests
in
terms
of
the
other
item
we
have,
which
is
unassigned
bugs
it's.
Basically,
an
ongoing
open
request
for
people
in
the
community
to
look
at
the
bugs
that
are
submitted
to
unassigned
and
that's
a
report.
146
there
were
a
couple
new
ones
this
week
one
was
for
uploader
and
one
was
for
data
schema.