Summary | JavaScript code for embedding any API gallery view |
Queue | Ansel |
Type | Enhancement |
State | Resolved |
Priority | 1. Low |
Owners | mrubinsk (at) horde (dot) org |
Requester | chuck (at) horde (dot) org |
Created | 06/01/2008 (6232 days ago) |
Due | |
Updated | 07/04/2008 (6199 days ago) |
Assigned | |
Resolved | 07/04/2008 (6199 days ago) |
Milestone | 1 |
Patch | No |
Assigned to Michael Rubinsky
State ⇒ Resolved
"nice-to-haves" such a a embedded slideshow and carousel...
http://cvs.horde.org/co.php/ansel/js/embed.js?r=1.1
http://cvs.horde.org/co.php/ansel/js/src/embed.js?r=1.1
http://cvs.horde.org/co.php/ansel/jsapi.php?r=1.1
http://cvs.horde.org/co.php/ansel/themes/jsembed.css?r=1.1
This will be provided as some sort of pre-made widget that provides
some HTML on the caller side, and a <!--a75c305b1c0a6022--><script>
tag that would fetch JSON data representing the gallery from the Ansel
server (image src, caption text, links for each image etc..). The
returned javascript would also contain an onload event handler that
would populate the "caller side HTML".
only avoiding API calls, but avoiding having to rewrite the pager
links inside javascript.
view in an external page.
for the pager would mean the embedding code wouldn't have to do
anything special about pages.
the next gallery page, thus saving more api calls?
Priority ⇒ 1. Low
Type ⇒ Enhancement
Summary ⇒ JavaScript code for embedding any API gallery view
Queue ⇒ Ansel
Milestone ⇒
Patch ⇒ No
State ⇒ Accepted
view in an external page.
Having gallery views that used javascript (with fallback of course)
for the pager would mean the embedding code wouldn't have to do
anything special about pages.