diff options
| author | erdgeist <erdgeist@erdgeist.org> | 2026-06-30 17:11:32 +0200 |
|---|---|---|
| committer | erdgeist <erdgeist@erdgeist.org> | 2026-06-30 17:29:12 +0200 |
| commit | 3e87925a35f73aa2261eb66df3ef4ca11b64eeea (patch) | |
| tree | 8a9a6da1f99b4480e07548ffaf5d5b4945603ba9 /public/javascripts/shadowbox/adapters/README | |
| parent | b97466cdfbcb5b02d4eaf38661c051d1a095838e (diff) | |
Replace Shadowbox with GLightbox, drop jQuery from public site
Vendors GLightbox 3.3.1 (MIT, dependency-free) as static files in
public/javascripts and public/stylesheets, replacing the Shadowbox
2009 vendor tree and its jQuery adapter. Public site no longer loads
jQuery at all.
- app/views/layouts/application.html.erb: swap Shadowbox script/style
includes and the public_bundle (jQuery) include for GLightbox's
CSS/JS
- app/views/content/_headline_image.html.erb: headline image is now
itself a GLightbox trigger; additional images are direct
a.glightbox links sharing a per-page data-gallery group, replacing
the hidden shadowbox_images div and its click-forwarding trigger
- public/javascripts/public.js: replace Shadowbox.init/setup and the
click-forwarding handler with a single GLightbox() init call;
remove the unused image_handler object
- Remove public/javascripts/shadowbox/ (including vendored Sizzle,
swfobject, and unused video/Flash players) and
public/stylesheets/shadowbox.css
- Remove app/assets/javascripts/public_bundle.js (jquery require)
Diffstat (limited to 'public/javascripts/shadowbox/adapters/README')
| -rw-r--r-- | public/javascripts/shadowbox/adapters/README | 11 |
1 files changed, 0 insertions, 11 deletions
diff --git a/public/javascripts/shadowbox/adapters/README b/public/javascripts/shadowbox/adapters/README deleted file mode 100644 index 5083961..0000000 --- a/public/javascripts/shadowbox/adapters/README +++ /dev/null | |||
| @@ -1,11 +0,0 @@ | |||
| 1 | A Shadowbox "adapter" is a small helper file that makes it easy to use | ||
| 2 | Shadowbox with a given JavaScript framework. Since most JavaScript frameworks | ||
| 3 | tend to contain a basic set of very similar functions (for retrieving style | ||
| 4 | information on elements or handling events, for example) it is not necessary to | ||
| 5 | tie Shadowbox to a particular framework. Instead, the adapter can use the | ||
| 6 | underlying framework that is already loaded on the page to reuse some of the | ||
| 7 | code. | ||
| 8 | |||
| 9 | If you do not see an adapter for your favorite framework in this directory, feel | ||
| 10 | free to create your own and implement the same interface as the others. It may | ||
| 11 | then be used the same as you would use any other. | ||
