►
From YouTube: TTEOT Training Video - S2E23 - jQuery: Hide vs Remove
Description
You'd think it is an easy choice, but there are legitimate reasons to go one way or the other. We'll talk about some of these reasons, and as an added bonus, we'll recap our last video with a great practical application on using drilldown SQL reports.
Contents:
0:00 - Title
0:32 - Intro
0:58 - KohaCon22
2:32 - Episode 22 Recap and Application
11:58 - Hide vs Show
9:14 - How it Works
19:28 - Wrap Up
Referenced notes:
https://www.w3schools.com/jquery/eff_hide.asp
https://www.w3schools.com/jquery/jquery_dom_remove.asp
Music: https://www.bensound.com
A
B
There
here's
the
koha
Us
website
right
now,
you'll
see
a
logo
here
for
Quahog
con
22..
That's
a
combination
of
the
annual
International
koha
Conference
and
our
kohai
us
conference
it'll
be
held
here
where
I
am
in
Lawrence
Kansas.
There's
a
registration,
page
I
started
yesterday
or
the
day
before,
tweeting
every
day,
I'm
tweeting
the
name
of
our
local
restaurant,
a
locally
owned
restaurant,
so
that
you'll
know
where
to
eat.
If
you
come
to
Lawrence
and
join
us
at
the
conference,
the
registration
is
right
there.
B
Not
be
long
after
this
video
is
released
yep.
This
video
should
go
up
what
the
25th
for
the
18th.
So
when
you
see
this,
video
you'll
have
just
a
couple
of
weeks,
not
quite
two
weeks
left
to
register
so
be
sure
to
do
that
and
you
can
watch
online.
If
you
can't
come
to
Lawrence
Kansas,
you
can
it'll,
be
streamed,
live
on
YouTube,
and
so
please
come
to
the
conference,
meet
other
people
and,
of
course,
for
these
videos.
You
can
find
these
videos
on
the
learn
page.
B
B
Videos
so
lots
of
good
training,
and
actually,
since
we're
here,
I'll
mention
this
last
episode
we
did
was
on
SQL
drill.
Downs
yesterday
I
saw
a
comment
on
the
Bywater
Solutions
slack
Channel,
where
somebody
said
well.
Let
me
look
it
up
over
here
and
see
what
they
said.
Does
anyone
know
how
to
run
a
report
on
clubs
by
selecting
the
name
of
a
club
from
a
drop
down?
B
The
first
report
will
just
be
a
list
of
will
actually
get
the
information
you
want
from
the
club
and
it'll
have
a
free
text
field
in
there,
where
you
can
put
in
the
club
name
and
then
I
said,
and
then
you
create
a
second
report
so
that
you
can
link
the
club
name
to
that
report.
You
just
get
a
list
of
Club
names
and
who
wrote
that?
Oh,
it
was
you
yes.
B
A
Worked
out
really
well,
you
know
there
were
several
ways
to
approach
this
and
I
started
out.
Well,
let
me
give
you
a
back
story
here.
I
I
mean
when
you
work
on
something
and
you
approach
it
from
so
many
different
angles.
You
know
sometimes
some
of
the
easiest
Solutions
just
kind
of
Escape
you
so
so
we
have
a
a
newsletter
that
we
want
people
to
be
able
to
sign
up.
For
originally
we
had
staff
giving
patrons.
A
A
Well,
you
know
you're,
maintaining
separate
documents
about
the
stuff
and
I
and
I
thought
well,
why?
Why
don't
we
make
it
so
that
we
can
have
that
sign
up
within
the
patron
account?
And
so
I
was
thinking
about
this
and
I
thought.
Okay,
we'll
we'll
set
up
a
patreon
attribute
and
I
can
do
that.
But
then
she
wanted
the
the
dates
that
they
signed
up,
which
you
know
you
can
only
record
one
thing
in
a
patron
attribute,
so
I
thought:
okay,
I'll
create
a
second
Patron
attribute,
that's
hidden
and
anytime.
A
A
B
A
B
A
B
A
Didn't
work
because
it
was
tied
to
another
tribute
and
that
would
be
rather
difficult
to
accomplish.
So
this
was
a
perfect
solution,
so
I
converted
everything
over
to
that.
But
I
was
running
into
an
issue
with
the
report
on
it.
You
know
that
we
would
want
to
gather
all
the
emails
for
the
patron
for
and
so
I
I
threw
it
out
on
the
slack
channel
for
for
Bio
water
asking
if
there
were
any
good
ideas
and
while
I
threw
that
out
there
I
thought.
A
Okay,
what
I
was
trying
to
accomplish
was
I
didn't
want
to
have
staff
fill
in
the
name
of
the
the
newsletter
that
they
wanted.
You
know
the
enrollment
for
you
know,
because
there's
several
newsletters
or
clubs
or
whatever
in
there.
They
just
want
the
one
club
or
newsletter.
So
you
know
how
am
I
going
to
do
that
the
club
table
is
not
an
authorized
value
so
they're
and
it's
not
one
of
the
other
tables
that
you
can.
You
know,
grab
that
information
and
create
a
drop
down.
A
A
Report
that
gets
exactly
you
want,
and
so
in
fact
let
me
share
yeah
I'd
like
to
see
this
yeah,
okay,
so
here's
my
report
that
just
basically
gives
the
contents
of
a
specific
Club,
but
when
you
run
it
it
asks
for
the
ID.
So
it's
basically
the
idea
of
the
club,
and
so
what
I
have
here
is
I
have
another.
A
The
clubs
give
me
a
list
of
the
names
and
then
a
button
to
to
view
the
enrollment,
and
you
know
that's
basically
a
couple
lines
here:
right,
I'm
selecting
from
the
clubs
table
the
name
and
then
concatenating
the
ID
within
a
a
link
to
that
report
right
and
in
fact,
I'm
still
calling
it
test.
Let
me
update
this
real,
quick
here,
all
right
better
than
test
anyways.
So
you
know
that's
all
there
is
to
it
and
so
now.
B
A
A
A
I
have
to
maintain
that
list
of
newsletters
separately
to
work
with
this
report,
whereas
having
a
second
report
get
that
list
is
more
Dynamic,
so
all
I
have
to
do
is
create
a
club
or
newsletter,
and
it
will
automatically
be
in
this
list
and
linked
right
to
the
list
of
enrollments
for
that
list.
So
that
was
a
very
good
approach
and
very
timely.
A
B
And
remove
or
hide
and
removed.
Yes,
we
do.
A
lot
of
we've
talked
a
lot
about
hiding
things,
but
sometimes
it's
better
to
remove
them,
and
so
I've
got
a
couple
of
quick
examples
here.
So
here
in
the
OPAC
I'm
in
advanced
search
and
I've
got
this
item
type
here
magazine,
and
maybe
that's
a
an
item
type
that
for
whatever
reason,
I
want
to
hide
this
I.
Don't
want
people
to
be
able
to
see
it.
B
So
I've
got
two
choices
here:
I
can
use
I
can
I've
got
the
selectors
to
isolate
that
check
box
in
under
magazine
here
and
I'm
going
to
go
ahead
and
save
that
and
right
now,
I'm
just
going
to
hide
it.
So
if
I
reload,
the
page
you'll
see
magazine,
will
disappear,
cool
no
longer
there
and
that's
hide
okay,
and
this
one
is
remove.
A
B
A
B
B
It's
actually
still
there
in
the
in
the
substructure
of
the
page
and
all
of
the
code
that
builds
the
page.
That's
still
here
so
I
could
actually
go
in
if
I.
If
I
know
that
it's
there
I
can
go
in
and
I
can
unhide
it.
You
know
anybody.
Can
anybody
can
use
their
browser
to
go
in
there
and
bring
it
back
to
life
to
bring
it
out
of
the
dead
because
we
haven't
taken
it
off
the
page
we've
just
made
it
invisible
on
the
page.
So
let
me
do
remove.
B
B
A
And
that-
and
you
reminded
me
of
that
when
you
were
saying
that,
because
we're
trying
to
think
why
would
I
want
to
remove
when
I
can
always
hide,
and
sometimes
there
might
be
something
sensitive,
that
you
need
to
remove
something
that
you
really
don't
want
people
to
be
able
to
resurrect
like
you
said,
and
they
can,
if
they
I
mean
technically
with
JavaScript,
you
could
turn
off
JavaScript
altogether
and
prevent
it
from
happening,
prevent
the
removal
but
you're,
making
it
much
harder.
If
you
use,
remove
versus
hide.
B
And
I
found
a
couple
of
places
where,
if
you
there
there's
a
couple
of
instances,
I've
had
in
the
past,
where,
if
you
just
hide
something
you
it'll
it,
that
element
may
still
take
up
some
space
on
the
page,
and
so,
if
you
want
to
get
a
cleaner
look,
remove,
usually
works
better
because
remove
doesn't
just
make
it
invisible
and
leaves
maybe
a
placeholder
there.
You
know
remove,
removes
it
from
the
page
completely
right.
It
allows
the
other
elements
to
fit
into
that
space.
There's.
A
It
is
not
a
good
option
in
this
case,
because
you
don't
want
the
chance
of
that
hidden
object
having
some
ill
effect.
I
I
wanted
to
replace
the
button
with
same
name
and
characteristics,
so
it
would.
The
page
would
still
function
the
way
it's
supposed
to,
but
I
also
wanted
to
add
some
characteristics
to
it
that
I
couldn't
add
to
the
original
button.
So
in
that
case,
I
removed
that
button
I
didn't
hide
it
because
I
didn't
want
some
side
effect
with
that
hidden
button.
In
this
case.
A
Yeah,
if
you're,
if
you're
working
with
forms
yeah,
it
might
be
a
better
idea
if
you,
if
you
need
to
get
rid
of
an
element
in
a
form
better
to
hide
it
than
remove
it,
because
sometimes,
if
you're
trying
to
submit
a
form-
and
it
needs
something
there-
it's
expecting
something
there
and
it's
not
there.
It
might
barf
on
you
and
we
I've
dealt
with
broken
Pages
before
yeah
you
can.
A
You
can
get
into
some
trouble
if
you
remove
elements
that
the
page
is
expecting
to
see
when
when
it's
doing
something
else
or
something
else
on
that
page
relies
on
that
element.
So
you
know
you
kind
of
have
to
assess
whether
or
not
you
want
to
remove
or
hide
remove
is
a
good
option
if
you
want
to
keep
people
from
being
able
to
unhide
things,
and
it's
also
a
good
option.
A
If
you
want
to
be
able
to
clean
up
the
the
page
code
a
little
bit
and
not
have
to
sift
through
stuff,
that
isn't
necessary
height
is
the
way
to
go.
If
is
a
little
bit
safer,
it's
the
way
to
go
if
you're
dealing
with
form
elements
or
things
that
other
parts
of
the
page
still
rely
on,
even
though
you
don't
want
people
playing
with
it
right.
A
Right
just
a
reminder
to
everybody:
please
check
us
out
on
the
YouTube
channel.
Our
YouTube
channel
has
all
of
our
videos
and
we
would
love
it
if
you
would
like
our
videos
or
even
subscribe
to
the
playlist
and
comment
where
you
can.
We've
had
some
comments
back.
We
had
a
comment
on
one
of
our
previous
videos
that
we
responded
to.
A
It
wasn't
something
that
we
could
necessarily
cover
it
in
our
videos,
but
you
know
we'll
always
get
back
to
you
and
you
know
we're
free
to
somewhere
else
if
we
can't
cover
it
yeah.
Thank
you
very
much
for
checking
out
our
very
short
video
today
and
we'll
see
you
again
in
two
weeks,
see
you
later
foreign.