►
From YouTube: Backdrop Weekly 1/5 (what's in Backdrop 1.6)
Description
Today’s development agenda: https://goo.gl/4qLdKY
A
Alright,
we
are
on
air
happy
new
year,
buddy,
it's
January
fifth,
and
we're
just
going
to
do
a
developer
rundown
for
what's
left
for
backdrop,
16
and
then
we'll
see.
If
there's
anything
else,
I
want
to
throw
on
the
agenda
for
today.
After
that,
let's
see
so,
this
monday
was
January
first
and
since
that
was
a
holiday,
we
decided
to
extend
the
feature
free
sideline
to
january
second,
which
was
great.
A
There
were
a
whole
ton
of
people
working
an
issue,
queue,
helping
us
review
and
revise
stuff
at
the
very
last
minute,
and
I
think
we
got
all
of
our
intended
feature
requests
with
the
exception
of
one
in
for
backup
16,
which
is
great,
and
we
even
tried
to
get
a
little
bonus.
One
we're
going
to
try
and
do
the
field
type.
I'm.
Sorry
page
element
blocks
for,
like
page
title
messages
tabs
we
thought.
Maybe
we
could
squeeze
that
one
in
also
but
hit
a
couple
snags
so
that
one
didn't
get
in.
A
B
I
would
say
any
kinks
I
still.
We
still
need
to
do
lots
of
test
coverage.
Fort
I
started
I've
been
working
on
that,
but
it's
just
there's
so
many
different
permutations
of
referencing
different
things
kristef
in
order
to
get
test
coverage
on
like
all
the
different
core
entities
and
things
like
that,
we're
going
to
do
to
do
I'm
gonna
need
to
do
a
lot
of
stuff
for
that
or
and
hopefully
people
will
help,
and
then
there
is
the
question
of
the
upgrade
path
and
what
what
it
should
be
upgrading
from
whether.
A
B
Upgrading
entity
reference
any
any
any
entity,
reference
fields
from
Drupal,
7
imports
or
whether
we
want
to
my
no
because,
okay
or
any
of
the
reference
fields
or
and
then
figure
out
what
to
do
with.
If
we
want
to
replace
the
taxonomy
reference,
we
need
to
look
at
replacing
the
functionality
of
the
existing
widget,
which
has
like
free
tagging
and
stuff
like
that
and
whether
that
should
just
be
for
taxonomy
or
whether
it
should
be
for
or
whether
we
should
allow
freitag
creation
of
other
entity
types
like
nodes
or
users
and
I'm.
A
B
Yeah
I
mean
I
think
we
just
have
a
lot
of
questions
about
how
it's
going
to
reside
in
core
all
right,
so,
like
I,
feel
like
the
basic
functionality.
Is
there
I
think
we
have
a
couple
issues
where
it's
not
working
properly
for
the
autocomplete
widget
is
not
working
properly
for
several
different
entity
types,
because
it
looks
like
there's
a
difference
in
the
how
the
stores
the
bundle
information.
B
So
we
might
need
to
do
some
more
work
with
that,
but
for
referencing
nose
and
things
like
that,
it
seems
to
be
working
fine,
as
far
as
I
can
tell
I
think,
but
yeah,
so
people
can
start
using
it.
I'd
like
to
get
a
release
of
it
sometime
soon
after
we
get
all
those
issues
so
yeah.
If
anyone
wants
to
help
out
by
trying
things
out
or
helping
write
tests
would
be
the
best
button.
I
know
that
no
one
really
wants
to
do
that.
A
Okay,
that
sounds
like
a
good
road
map.
I've
got
a
couple
sites,
I'm
working
on
this
month,
that
I
can
probably
throw
it
on
and
see
how
it's
gonna
perform.
I'm
not
sure
what
kind
of
use
cases
they'll
have
it'll,
probably
just
feel
like
a
term
reference
style
thing
or
file
references
or
something
but
it'll
be
fun
to
play
with
it.
So,
okay,
good
and
thanks
Mike,
for
your
continued
commitment
working
on
this
I
know.
A
C
Okay,
great
okay,
that
means
I
get
to
talk
about
the
ones
that
are
fun
because
they're
done
hey,
okay,
so
the
other
two
items
that
we
had
that
we're
that
we
were
really
focused
on
41.6
include
entity,
view
modes,
adding
the
ability
to
add
custom
view
modes.
Besides
things
like
teaser
and
fold
and
search
results.
C
C
So
if
you
download
the
latest
version
of
backdrop,
it's
a
good
thing
to
check
out
setting
up,
create
custom
view
modes
and
testing
out
that
functionality,
but
it,
like
I
said
to
the
test
coverage
is
fairly
comprehensive,
so
we
should
hopefully
not
have
too
many
issues
there
anything
else
on
energy
view,
modes,
Jenna
or
anyone.
Nope:
okay,
yeah:
it's
awesome.
C
Okay,
the
next
item
is
the
work
to
try
to
make
our
media
management
a
little
bit
better
and
the
first
step
in
doing
that
is
solving
a
problem
that
we
currently
have
that
in
1.5
we
added
the
ability
to
upload
an
image
through
ckeditor,
even
on
things
that
weren't
entities
such
as
blocks,
which
are
stored
in
configuration.
But
the
result
of
that
was
that
when
you
upload
an
image
into
a
block,
the
image
is
marked
permanent
immediately
and
it's
not
strictly
associated
with
that
block.
C
So
if
you
delete
the
block,
the
image
still
hangs
around
and
that's
a
problem,
because
once
you
upload
the
image
and
save
the
block
that
image,
you
could
no
longer
deleted
off
your
server
in
any
way.
It
would
just
be
there
on
your
server
without
any
interface,
for
you
to
remove
it
whatsoever
other
than
like
ft
peeing
up
and
deleting
it
or
something
like
that.
So
we
have
solved
that
problem
by
adding
a
view
for
managing
files
in
issue
2375,
and
this
kind
of
brings
files
into
more
of
kind
of
being.
C
C
So
that's
great,
is
you
2375?
Is
that
issue?
There
are
some
desires
that
we
didn't
complete
in
that
issue,
that
I'm
not
even
sure
that
follow
ups
have
been
created.
Yet,
for
things
like
a
when
you
bulk
delete
a
group
of
files,
it
tells
you
how
many
times
each
one
of
those
files
is
in
use
that
we
know
about,
but
there's
no
listing
of
where
those
files
are
in
use.
Unless
you
delete
the
file
individually.
C
C
But
you
know
that
that
feature
in
particular
might
be
possible
for
1.6
as
a
Lincoln
improvement
on
the
user
interface
essentially,
but
any
further
changes
to
managing
files.
Things
like
this
edit
file
ability
or
feel
double
files,
and
things
like
that
that'll
I'll,
definitely
be
post
1.6.
So
that's
pretty
much.
All
that
we
have
to
talk
about
at
this
point
is
testing
that
view
outs,
making
sure
everything
works
correctly
and
then
improving
in
a
user
interface
tweaks,
basically
that
that
we
think
might
be
possible
yet.
C
C
Great
those
are
the
items,
those
three
where
the
items
that
have
long
been
on
our
weekly
agendas
and
it's
awesome
to
see
least
two
out
of
three
coming
together.
You
know
before
code,
freezer
more
like
on
code
freeze,
so
we
still
got.
You
know
another
10
days
before
released
to
kind
of
polish
those
up
in
any
way
that
is
necessary.
C
There's
a
bunch
of
other
items
that
are
on
this
agenda,
though
of
other
neat
features
that
might
be
interesting
to
call
out
is
having
been
completed
that
got
into
1.6
before
feature
freeze
that
could
be
kind
of
fun
features
for
us
to
talk
about
in
marketing
and
in
a
blog
posts,
and
things
like
that,
once
we
actually
write
up
the
release,
blog
post
for
this
version
and
one
of
those
is
a
hamburger
menu,
a
hamburger
menu.
That's
you
can
now
I'll
share
my
screen.
C
C
This
home
/
about
and
you
when
your
menu
is
on
a
smaller
device.
Then
it
collapses
into
the
so
called
hamburger
with
these
three
lines
indicating
that
there's
a
menu
underneath
it
and
then,
when
clicking
it,
opens
and
collapses.
The
menu
underneath
here
and
this
menu
is
that
same
smart
mini's
library
that
we
had
to
do.
1.5
the
it
itself
is
also
a
hierarchical
collapsible
list,
so
you
can
collapse
your
entire
menu
down
to
just
one
item
on
small
screens
and
then
inside
of
here
expand
individual
items.
C
C
That
is
issued
2369
the
hamburger
menu.
We
talked
just
earlier
in
the
design
meeting
about
some
work
that
needs
to
be
done
regarding
these
the
secondary
menu
up
here,
the
my
account
and
log
out
links
that
we
need
some
additional
styling
on
here
to
kind
of
account
for
the
fact
that
now
that
the
primary
menu
is
hit
is,
is
under
a
hamburger.
That's
these
links
get
too
much
visual
weight.
Essentially,
so
we
are
hoping
to
address
that
before
the
release
of
1.6
a
solution
as
to
how
to
solve
that
is
still
in
flux.
C
Let's
see,
another
neat
feature
that
was
added
real
recently
also
relating
to
blocks
is
issued
2402
that
solves
this
very,
very
common
problem
of
the
breadcrumb.
If
the
breadcrumb,
if
you
would
like
to
show
the
current
page
title
in
the
breadcrumb,
there
is
now
a
menu
block
up
our
sorry,
a
breadcrumb
block
option
for
doing
that,
which
I
think
I
can
probably
demonstrate
that
as
well.
So
if
I
go
to
a
subpage
like
abouts
that
has
this
bright
chrome
on
here,
I
can
configure
this
block
and
check
this
box.
C
It
says
display
the
current
page
title
as
the
last
breadcrumb
and
hit
save,
and
now
this
about
page
you
can
see
like
the
title
bouts
is
now
in
the
breadcrumb,
but
it's
not
actually
linked
and
then
home
is
of
course
look
back
to
home.
So
that's
really
cool
and
a
very
trivial
change
as
far
as
implementation
goes,
and
it
doesn't
affect
be
mean
or
anything,
it's
just
an
option
in
the
block,
and
then
everything
else
stays
the
same.
C
C
At
here
you
go
like
admin
bar.
This
is
a
great
example
here.
This
is
the
difference
of
what
the
admin
bar
settings
form
used
to
be
like
and
what
it
is
now
that
we
added
pound
config
and
you
could
say,
admin
bar
dot
settings
to
say
what
config
file
this
form
will
save
into
and
then
down
at
the
bottom
of
the
form.
C
The
reason
why
this
was
so
problematic
and
why
we
didn't
have
it
initially
is
because,
unlike
variables
that
there's
only
a
single
table
for
all
variables,
config
can
save
into
multiple
locations,
so
one
form
might
actually
save
into
multiple
config
files,
and
this
solution
of
adding
pound
config
makes
it
so
that
you
can
by
default,
set
something
for
the
entire
forum.
But
then
you
can
also
do
it
on
a
per
element
or
per
group
basis,
so
you
can
put
it
on
a
field
set.
C
B
C
Solution,
it's
a
fantastic
implementation
to
and
although,
like
the
net
change
here,
is
actually
only
reducing
20
lines
because
there's
a
lot
of
additional
documentation
that
was
added
around
how
to
actually
use
this
but
yeah.
It
makes
it
fantastic,
oh
and
testing.
It
makes
it
fantastic
from
a
porting
standpoint
yeah.
This
is
the
dock
block
here
and
on
top
of
system
settings
form.
C
C
So
that's
that's
where
we
are
right
now.
We
are
not
adding
any
more
new
features
for
the
next
a
couple
of
weeks
essentially,
but
we
have
a
lot
of
work
to
do
still
as
far
as
fixing
as
many
things
as
we
can
making.
As
many
UX
minor
improvements
as
we
can
before
release,
but
yeah,
it's
great
we're
we're
in
a
really
great
great
position,
and
even
if
we
were
to
release
1.6
tomorrow,
we're
in
a
releasable
condition
already.
We
think
so.
D
E
A
Is
really
a
featured,
so
I
tagged
it
for
fisheries,
but
that
was
like
the
you
know
two
days
we
were
reviewing
major
issues
so
I
don't
know
how
the
issue
was
tagged
as
a
task
in
the
first
place.
If
people
think
is
a
task,
if
it's
something
we
should
be
trying
to
work
on
now
or
if
it's
something
we
should
push
to
17
yeah.
A
C
A
C
Wants
to
take
a
look
at
that
issue,
it
actually
it's
just
too
cool
that
the
makes
it
so
that
you
can
place
the
title
right,
cross,
tabs
action,
links
and
messages.
I
think
individually
is
blocks,
so
you
can
move
them
all
around
on
the
page
and
it
disables
the
equivalent
version
in
the
layout
templates.
So
basically
Blanca
fighing
every
element
on
the
page
are
making
it
possible
to
block
by
every
element
on
the
page.
It's
very
neat
and
could
use
additional
review.
Even
if
it's
not
going
to
get
into
1.6.
C
Since
Andy
is
here,
I
can
say
thank
you
Andy,
it's
totally
awesome
and
I
feel
extra
bad
because
it
was
filed
a
couple
of
weeks
ago,
but
I
am
not
sure
I
don't
think
it
was
labeled
or
oh,
no,
it
was
kicked
back
to
meets
work
and
then
it
didn't
bubble
back
up
into
my
attention
until
a
couple
days
ago.
So
I
was
really
just
unfortunate.
That
is
it
a
reviewing
problem
really
rather
than
nate
an
implementers
problem,
so
I
apologize
for
that.
C
D
C
Yeah
and
it
hasn't
even
been
brought
up
because
I
think
all
of
us
are
smart
enough
to
know
better
that
we're
not
tying
in
any
way
the
new
design
of
backdrop,
CMS
torg
to
the
release
of
1.6
they're,
just
totally
totally
separate,
although
that
would
be
cool
like
we're.
Not
even
saying
that
you
know
we're
gonna
try
to
get
the
redesign
out,
because
I
don't
think
that
we
are
because
really
our
attention
is
on
1.6
right
now
anyway.
So,
but
it
is,
it
is
fantastic
West.
C
C
Okay,
there's
one
item
here
in
the
general
discussion
list
for
officially
dropping
support
for
ie8,
which
is
issued
to
14
I,
think
we
actually
had
a
decision
on
this
from
the
PMC
that
basically
said
drop
it,
but
for
1.6
I
feel
like
actually
decoupling.
That
is,
shouldn't
really
be
a
priority
for
us,
so
maybe
our
stance
that
the
results
will
be
that
our
stances,
basically,
we
don't
officially
support
IE
8.
However,
it's
still
working
mostly.
A
We
just
talked
about
this
in
the
last
meeting
to
and
wanted
to
make
sure
that
we
brought
it
up
here
so
that
everybody
could
have
a
chance
to
weigh
in
we
decided
to
support
drop
for
a
drop
support.
Ie
8,
we
haven't
decided
exactly
like
what
that
looks
like
in
terms
of
if
we
need
to
do
anything
other
than
stay.
A
D
D
C
C
That
is
put
in
place
with
a
conditional
comment
that
says,
if
I
ate
or
less
put
in
the
html5
shim,
and
that
that
shim
allows
you
to
add
CSS
styling
to
html5
elements,
including
things
like
nav
and
article
and
footer,
and
things
like
that,
because
without
the
shim
styling
in
ie8
and
earlier
versions
doesn't
work.
Call
those
elements
I
feel
like
we
should
just.
C
B
Just
you
know,
because
chances
are,
someone
is
going
to
hit
the
site
eventually
evaluate.
So
it's
probably
good
if,
like
that,
those
Styles
work,
like
you
know
the
stuff
that
we're
talking
about
that.
Don't
workers
like
lessons
talking
about
the
transforms
and
stuff
like
that
which
yeah
we
don't
need
but
like
let's
not,
let's
not
remove
the
shin
well.
C
Because
it's
resolved
that
we're
not
going
to
do
anything
about
it
in
the
next
10
days,
so,
okay!
Well,
that's
something
to
think
about!
We
do
have
the
issue.
Is
you
to
14
where
this
is
being
discussed?
It's
still
open,
I
believe
yes
still
open,
and
so
we
can
actually
talk
about
the
implementation
of
how
we
actually
want
to
handle
that
now
the
decision
has
been
made.
A
Want
to
know
what
we
should
talk
about
next
week
like
now
that
were
passed
to
the
feature
edition
part.
Should
we
focus
on
like
issues
that
need
a
review
before
they
can
get
in
like
our
remaining
tasks
for
one
before
the
1.6
release,
or
should
we
go
back
to
the
previous
agenda
structure,
where
we
got
to
talk
about
things
like
the
website
in
the
newsletter
and
all
that
good
stuff.
C
I
think
we
should
probably
focus
on
the
the
bugs
that
remain
next
meeting.
If,
if
any
that
that
we
feel
are
important
enough,
that
we
should
call
out
all
of
the
bugs
right
now
are
like
you
know,
some
of
them
have
been
in
place
for
the
entire
1.5
release
its
it's,
not
that
they're
critical
issues,
although
you
know
it,
would
be
lovely
to
fix
as
many
of
them
as
we
can't
the
1.6.
C
C
A
So
since
we
have
some
time
right
now,
I
did
have
a
check-in
phone
call
last
night
with
a
facet
interactive,
a
group
that
has
offered
to
do
our
newsletter.
Sending
for
us
they're,
also
really
good
at
branding
and
marketing
in
general,
and
we
had
a
pretty
good
talk
about
having
them
take
over
the
newsletter,
but
also
like
rewrite
our
announcement
content
to
be
in
the
same
sort
of
voice
as
the
newsletter
to
kind
of
create
a
consistent
brand
impression
and
I
thought.
A
A
The
night
before
so
it
would
be
good
if
we
get
some
kind
of
process
around
that
so
I
don't
know
doing
right
now,
I
told
them.
We
would
write
the
blog
post
and
then
give
it
to
them,
and
they
could
help
us
change
the
content.
But
I
think
if
we
know
it's
going
to
be
in
it,
we
could
even
create
like
a
bolt
list
of
like
this
is
the
stuff
we
want
to
highlight
in
the
post
that
lists
all
the
new
features
or
whatever
it
is
so
I.
Don't
know.
A
A
C
Okay,
well,
I
think
that's
it
for
the
meeting
today
then
I
want
to
express
my
contentment
with
the
number
of
things
that
we
managed
to
get
together
and
complete
I
also
think
so
far
I'm
digging
the
code.
Freeze
like
this
is
fantastic,
like
all
of
the
stress,
was
taken
care
of
already
and
it's
kind
of
well
done,
and
now
it's
just
okay,
just
10
days
to
release,
and
just
we
do
what
we
can
so
much
better.
So.
A
We
had
a
whole
bunch
of
new
people
in
issue
queue
this
time
at
the
very
end
who
are
like.
Oh,
you
guys
need
help
and
just
jumped
in
and
helped
which
I
thought
was
fantastic.
So
thank
you
to
all
the
new
contributors
who
just
showed
up
and
helped
us
like
review
things
and
helped
us.
You
know
helped
me
write
JavaScript,
which
I'm
not
very
good
at
is
fantastic
yeah,
and
also
thanks
to
dr.
Wilmont
for
starting
everything
early
as
usual,
like
the
rest
of
us.