This online help will synchronous update together with the increase of the slideshow templates.

If a decent fraction of your customers or visitors are using Google Chrome, the latest version (13) has a pretty slick new feature you can take advantage of called prerendering.

What is prerendering?

Prerendering is a more robust form of prefetching (which you can use in Firefox currently). With prefetching, you can instruct the browser to fetch the top-level resource (usually an HTML page) and load it up in the background. The problem with this is that the HTML pages aren’t what slow you down: CSS, JS, and especially images are. Prerendering actually renders the entire page in the background, rather than just grabbing the markup, so prerendered pages will load instantly rather than waiting on secondary resources.

How to use prerendering:

Getting going with prerendering is actually incredibly easy, you just have to understand the constraints and when to use it. In order to have Chrome prerender a page, embed the following link somewhere on the page:

<link rel="prerender" href="http://example.org/index.html">

There are a few things to note about prerendering:

• Chrome will only prerender one page per instance – not per tab. That means not only can you only have one page prerendered, and you may not get even that if another tab is using it.
• Prerendering occurs after the initial page has finished loading (so blocking scripts may prevent it from happening)
• If the user doesn’t click the link in 30 seconds, Chrome dumps the prerendered page. This one is kind of a bummer, as pages that require some decent comprehension or reading won’t benefit. The documentation suggests this may change in the future.

We’ve already deployed an update for Notable that includes prerendering on the marketing site — if you go from the homepage through the tour (which based on our analytics we determined to be the most likely path) you should see some significant speed improvements in Chrome 13.
Get to it!

If you want to learn more about this feature, check out the very helpful Google White Paper on prerendering — is has a more complete list of the constraints as well as more thorough explanations of what the browser does for certain edge cases. There’s definitely a lot of potential here, and we’ll be investigating how we can take advantage of it in our apps and other properties.

Styles Demo

Title Bar Position -> left; Title Bar Width -> 100	Title Bar Position -> right; Title Bar Width -> 100

Title Bar Position -> bottom; Title Bar Width -> 400	Title Bar Color ->#0000FF; Title Bar Opacity -> 50

Note:
If title bar position is top or bottom, it is recommended to use the same value of slideshow width.
If title bar position is left of right, it is recommended to use a value much smaller than slideshow width.

Showcase Interface

Key Properties

Transition Type: Specify the easing function of the transition effect, including ‘swing’, ‘easeOutElastic’,'easeOutBack’, ‘easeOutBounce’.

Note:
Image Width and Image Height will affect the width and height of slideshow, and the size of title and description will also be affected.

• auto start – The slideshow will be played automatically after loaded.
• show start button – There will be a start button overlay the slideshow waiting for play.
• click to show next – The slideshow won’t play until mouse click on the slide.

Can the pictures in the slideshow be re-sized?
Yes, please set yes to Resize Image then change the Image Width and Image Height as you wanted.

How to specify which picture will be shown as the first?
Please modify the value of Initial Item.

How to remove the panel?
Please set no to Show Panel.

How to make the panel shown when mouse hover on the slide?
Please set auto to Show Panel.

How to hide the title of each picture?
Please set no to Show Title.

How to make the slideshow play different transition effect between each slide?
Please set random to Transition Type.

How many transition types in the slideshow?
scrollUp, scrollDown, scrollLeft, scrollRight, zoom, zoomFade, zoomTL,zoomBR, growX, growY, random.

Click here for the detail information:

http://www.dreamingsoft.com/123flashmenu/support/app_q2.htm

It’s so easy, only few lines we get things done!

1) Save the project first

2) If you won’t want SEO code please uncheck the option ‘Include SEO Code’.

3)Click Copy button and paste it into your web page editor. You will get follow script (in this case script is without SEO code):

4) You can easily place these code into TABLE, DIV,over Text or anywhere in the page.

5) You needn’t to adjust the layer and position of the Flash menu.

6) The 123fm.js will auto detect the position of TAG that embeds Flash menu and adjust the position of Flash automatically.

It’s so easy, only few lines we get things done!