search

uujgii / web-to-print-scripts

Automatically exported from code.google.com/p/web-to-print-scripts
0 stars 0 forks source link

Homepage slideshow #47

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
The slideshow on www.zetaprints.com is killing the browser.
The script needs to be optimized.

1. Optimize the performance.

2. Make sure that the images do not pile up first time the page is loaded. make 
them all hidden, except for the first one. Start the slideshow only when they 
are all loaded.

3. Commit the script to a branch called "homepage_slideshow".

Actually, I'm not 100% sure [2] has a good solution. Feel free to suggest 
something better.

Original issue reported on code.google.com by zetapri...@gmail.com on 7 Jul 2010 at 10:02

GoogleCodeExporter commented 9 years ago 
http://code.google.com/p/web-to-print-scripts/source/detail?r=131

Optimized. Memory leak is gone, but CPU loading still is a high. Slideshow is 
starting, when all images will be loaded.

Original comment by trilobit.alex@gmail.com on 9 Jul 2010 at 8:15

GoogleCodeExporter commented 9 years ago 
You can to see it and to test:
http://ec2-174-129-95-130.compute-1.amazonaws.com/

Original comment by trilobit.alex@gmail.com on 9 Jul 2010 at 8:18

GoogleCodeExporter commented 9 years ago 
No reason to have high CPU load.
What does need to be compromised to reduce it?

Original comment by zetapri...@gmail.com on 9 Jul 2010 at 8:20

GoogleCodeExporter commented 9 years ago 
The slideshow is really fast. What is the current transition time? We need to 
make individual slides stay still for a bit longer. I don't think it was this 
way before, slides start fading before they even load.

Original comment by agur...@gmail.com on 9 Jul 2010 at 8:37

GoogleCodeExporter commented 9 years ago 
It seems to be even speeding up.
Started slow and then went faster and faster.

Must be the same speed as on PROD.

Original comment by zetapri...@gmail.com on 9 Jul 2010 at 10:04

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 
  We use "flash and switch".
  Slides with different target link URLs get a special transition
  slides with the the same target link URLs switch with no transition

  SVN release
    http://code.google.com/p/web-to-print-scripts/source/detail?r=138

  You can copy files from SVN:
    http://code.google.com/p/web-to-print-scripts/source/browse/#svn/branches/homepage_slideshow/slideshow
  or you can copy files from /common/slideshow/.

  /common/slideshow/css/* - css-rules and button
  /common/slideshow/fade/* - the images for make fade effect
  /common/slideshow/js/slideshow.js - main slideshow script.

Original comment by trilobit.alex@gmail.com on 3 Aug 2010 at 4:07

GoogleCodeExporter commented 9 years ago 
last diffs:
http://code.google.com/p/web-to-print-scripts/source/diff?spec=svn138&r=138&form
at=side&path=/branches/homepage_slideshow/slideshow/js/slideshow.js
http://code.google.com/p/web-to-print-scripts/source/diff?format=side&path=/bran
ches/homepage_slideshow/slideshow/css/slideshow.css&r=138&spec=svn138

Original comment by trilobit.alex@gmail.com on 3 Aug 2010 at 4:10

GoogleCodeExporter commented 9 years ago 
CPU usage is considerably lower then before. I don't know what other 
compromises can be done without making the slideshow too dull.

Here's a screenshot for my PC perfomance:
With home page on PROD root opened (prod_root.png)
With home page on DEV root opened (dev_root.png)

Original comment by agur...@gmail.com on 3 Aug 2010 at 12:40

Attachments:

GoogleCodeExporter commented 9 years ago

Original comment by zetapri...@gmail.com on 4 Aug 2010 at 12:52