ez publish used as "slideshow"

«

Previous topic

|

|

Next topic

»

Author	Message
Frode Slettum	Tuesday 29 August 2006 4:47:22 am Hi A customer of mine today uses powerpoint to show a slideshow presentation on a big monitor. It has about 4 slides that's looping. It's a ok solution, but it's a bitch to update. It's very static and he has to stop the slideshow when updating it. I thought I maybe could use eZ publish to this. My idea was to make 4 dummy folders from root node, make a template override for each folder that displayed different information (ads, news etc) and some kind of code on each template to redirect to the next page within <x> seconds. Does this sounds like a good ide? If yes, what code should I use to redirect to the next page? If there is no easy way, I guess I could do a <meta> redirect manually on each template, and the 4. template to point to the first node.
Christian Johansen	Tuesday 29 August 2006 11:57:11 pm If it's a presentation that's running in a single location you have full control of your environment, so how you create your redirecting doesn't really matter, as long as it works in the environment you'll be using it in. You can do <meta>-redirects or do some javascript. Sounds like a nice way to do slide shows to me. You can even use Opera in fullscreen view to project it without showing the browser.
Frode Slettum	Wednesday 30 August 2006 7:34:03 am Thank you for your feedback. Didn't really thought abouth that opera-trick .. Great idea. One other thing, how can i accomplish this with <meta> when the template code comes within the <body> tag? Do I have to use java script?
Christian Johansen	Wednesday 30 August 2006 9:56:33 am I'm not sure whether or not meta redirect works in body or not, just try it. If it doesn't work, create a pagelayout override for the slideshow section that just does the basic head things and leaves the rest of head as well as all of body to the node template: <!DOCTYPE ...> <html> <head> <title>...</title> [more] {$module_result.content} </html> And then in node templates: <meta ...> </head> <body> [BODY here] </body> It's a bit dirty since the pagelayout doesn't nest properly, but it works.

Powered by eZ Publish™ CMS Open Source Web Content Management. Copyright © 1999-2014 eZ Systems AS (except where otherwise noted). All rights reserved.

eZ debug

Timing:	Jan 18 2025 18:42:02
Script start
Timing:	Jan 18 2025 18:42:02
Module start 'layout'
Timing:	Jan 18 2025 18:42:02
Module start 'content'
Timing:	Jan 18 2025 18:42:02
Module end 'content'
Timing:	Jan 18 2025 18:42:02
Script end

Main resources:

Total runtime	0.0134 sec
Peak memory usage	2,048.0000 KB
Database Queries	3

Timing points:

Checkpoint	Start (sec)	Duration (sec)	Memory at start (KB)	Memory used (KB)
Script start	0.0000	0.0057	587.9141	152.6250
Module start 'layout'	0.0057	0.0029	740.5391	39.4453
Module start 'content'	0.0087	0.0030	779.9844	93.3516
Module end 'content'	0.0117	0.0017	873.3359	34.3047
Script end	0.0133		907.6406

Time accumulators:

Accumulator	Duration (sec)	Duration (%)	Count	Average (sec)
Ini load
Load cache	0.0025	18.5008	14	0.0002
Check MTime	0.0012	9.2870	14	0.0001
Mysql Total
Database connection	0.0009	6.6432	1	0.0009
Mysqli_queries	0.0025	18.4509	3	0.0008
Looping result	0.0000	0.1481	1	0.0000
Template Total	0.0014	10.7	1	0.0014
Template load	0.0008	5.7620	1	0.0008
Template processing	0.0006	4.8629	1	0.0006
Override
Cache load	0.0005	3.6873	1	0.0005
General
dbfile	0.0002	1.1827	8	0.0000
String conversion	0.0000	0.0731	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	Edit	Override
1	print_pagelayout.tpl	<No override>	extension/community/design/community/templates/print_pagelayout.tpl
Number of times templates used: 1 Number of unique templates used: 1

Time used to render debug report: 0.0001 secs