cycle through objects

Next topic

Author	Message
Frode Slettum	Saturday 14 October 2006 1:31:43 pm Hi I want to make a template that cycles through all objects within a node. It's almost identical with the full image template. That template have the "previous" and "next" links that jumps to the next image. I want the same thing, only that I want the page to be automatically redirected to the next object within x seconds. When it comes to the last object, it skips to the first. I took a look at the full image template and tried to modify it to fit my scenario, but I couldn't manage it to work. I'm not sure what I did wrong. Any tips folks? regards Frode S
Marco Zinn	Sunday 15 October 2006 4:59:36 am Hi, i guess, you need to solve two issues: 1. Wrap-Around: Loading the first image, after the last image ist shown. I think, that shouldn't be too hard, as the current template grays out the "next"-button, when you are at the last image; so you can re-use that code. 2. Auto-Forwarding after n seconds: Actually, this is what most user (and customers) expect from a "slideshow". If you solve this, it should make its way into the ez distribution ;) I'd try these things: 2a: Redirect the browser using a javascript, which waits n seconds and the overrides the location of the current window. This will load the next page. But it need JS. 2b: Have a look at the new eZpublish features, which allow a template to modify the HTTP headers, which are sent with the page. I _think_ you can achieve the loading of the next page with HTTP headers (redirect-to, including a delay). If this works, it would be better, as it does not rely on JS code, which is always a pain. Unfortunately, i didn't find a link for that feature right now, but i'm sure, i read about it somewhere ;) Maybe this helps Marco http://www.hyperroad-design.com

Author

Message

Saturday 14 October 2006 1:31:43 pm

I want to make a template that cycles through all objects within a node. It's almost identical with the full image template. That template have the "previous" and "next" links that jumps to the next image. I want the same thing, only that I want the page to be automatically redirected to the next object within x seconds. When it comes to the last object, it skips to the first.

I took a look at the full image template and tried to modify it to fit my scenario, but I couldn't manage it to work. I'm not sure what I did wrong.

Any tips folks?

regards
Frode S

Marco Zinn

Sunday 15 October 2006 4:59:36 am

Hi,

i guess, you need to solve two issues:
1. Wrap-Around:
Loading the first image, after the last image ist shown. I think, that shouldn't be too hard, as the current template grays out the "next"-button, when you are at the last image; so you can re-use that code.

2. Auto-Forwarding after n seconds:
Actually, this is what most user (and customers) expect from a "slideshow". If you solve this, it should make its way into the ez distribution ;)
I'd try these things:
2a: Redirect the browser using a javascript, which waits n seconds and the overrides the location of the current window. This will load the next page. But it need JS.
2b: Have a look at the new eZpublish features, which allow a template to modify the HTTP headers, which are sent with the page. I _think_ you can achieve the loading of the next page with HTTP headers (redirect-to, including a delay). If this works, it would be better, as it does not rely on JS code, which is always a pain. Unfortunately, i didn't find a link for that feature right now, but i'm sure, i read about it somewhere ;)

Maybe this helps

Marco
http://www.hyperroad-design.com

eZ debug

Timing:	Jan 18 2025 19:20:36
Script start
Timing:	Jan 18 2025 19:20:36
Module start 'layout'
Timing:	Jan 18 2025 19:20:36
Module start 'content'
Timing:	Jan 18 2025 19:20:37
Module end 'content'
Timing:	Jan 18 2025 19:20:37
Script end

Main resources:

Total runtime	0.9396 sec
Peak memory usage	4,096.0000 KB
Database Queries	54

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0054	589.0391	152.6250
Module start 'layout'	0.0054	0.0030	741.6641	39.4453
Module start 'content'	0.0084	0.9298	781.1094	532.9375
Module end 'content'	0.9382	0.0013	1,314.0469	12.1719
Script end	0.9395		1,326.2188

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0033	0.3506	16	0.0002
Check MTime	0.0013	0.1430	16	0.0001
Mysql Total
Database connection	0.0011	0.1129	1	0.0011
Mysqli_queries	0.8847	94.1618	54	0.0164
Looping result	0.0016	0.1677	52	0.0000
Template Total	0.8888	94.6	2	0.4444
Template load	0.0027	0.2829	2	0.0013
Template processing	0.8861	94.3123	2	0.4431
Template load and register function	0.0001	0.0120	1	0.0001
states
state_id_array	0.0048	0.5085	1	0.0048
state_identifier_array	0.0037	0.3971	2	0.0019
Override
Cache load	0.0021	0.2227	22	0.0001
Sytem overhead
Fetch class attribute can translate value	0.0009	0.1003	2	0.0005
Fetch class attribute name	0.0016	0.1686	4	0.0004
XML
Image XML parsing	0.0024	0.2532	2	0.0012
class_abstraction
Instantiating content class attribute	0.0000	0.0008	4	0.0000
General
dbfile	0.0023	0.2473	22	0.0001
String conversion	0.0000	0.0006	4	0.0000
Note: percentages do not add up to 100% because some accumulators overlap

Templates used to render the page:

Usage	Requested template	Template	Template loaded
1	node/view/full.tpl	full/forum_topic.tpl	extension/sevenx/design/simple/override/templates/full/forum_topic.tpl
2	content/datatype/view/ezimage.tpl	<No override>	extension/sevenx/design/simple/templates/content/datatype/view/ezimage.tpl
2	content/datatype/view/ezxmltext.tpl	<No override>	extension/community_design/design/suncana/templates/content/datatype/view/ezxmltext.tpl
5	content/datatype/view/ezxmltags/paragraph.tpl	<No override>	extension/ezwebin/design/ezwebin/templates/content/datatype/view/ezxmltags/paragraph.tpl
3	content/datatype/view/ezxmltags/line.tpl	<No override>	design/standard/templates/content/datatype/view/ezxmltags/line.tpl
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 14 Number of unique templates used: 6

Time used to render debug report: 0.0001 secs