Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>1) Flash intro: bad practice, especially as so many users are now surfing with devices that either don't come with Flash, or have disabled Flash entirely. Flash also completely destroys search engine results. #1 recommendation: learn how to do animation in HTML5/CSS3, if you absolutely must, but intro screens are incredibly harmful to usability in general. The only real excuse for using them is to provide some sort of feedback to users if you're trying to front-load assets (image sprites for a game, or data for a dashboard, for example).</p> <p>2) You can't load Flash before the <code>&lt;body&gt;</code> of a page. It just doesn't work. However, given that, you could put together a structure like this:</p> <pre><code>&lt;body&gt; &lt;div id="flashObj"&gt;&lt;!-- object for Flash --&gt;&lt;/div&gt; &lt;div id="mainContent"&gt;&lt;!-- rest of your page --&gt;&lt;/div&gt; &lt;/body&gt; </code></pre> <p>Then you could call a javascript function from the end of your Flash animation (see <a href="http://www.kirupa.com/flash/calling_javascript_flash_using_as3.htm" rel="nofollow">http://www.kirupa.com/flash/calling_javascript_flash_using_as3.htm</a> for a tutorial) using the ExternalInterface object, but note that there are several browsers that still have issues with that object, so your cross-platform usability goes even further down.</p> <p>Essentially, in your html, you would have:</p> <pre><code>&lt;style&gt; #mainContent { display:none; } &lt;/style&gt; &lt;script type="text/javascript"&gt; function startMainContent(){ var flash = document.getElementById("flashObj"); var main = document.getElementById("mainContent"); if(flash &amp;&amp; main){ flash.style.display == "none"; main.style.display == "block"; } } &lt;/script&gt; </code></pre> <p>Then in your ActionScript, after your animation completes, you would add something like:</p> <pre><code>ExternalInterface.call("startMainContent()"); </code></pre> <p>Assuming ExternalInterface is working correctly, and you've followed Adobe's documentation for setting the proper flags in your <code>&lt;object /&gt;</code> tag to enable access to Javascript from your Flash object, that should do the trick.</p> <p>See this for an official Adobe guide to ExternalInterface: <a href="http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf626ae-7fe8.html#WS2db454920e96a9e51e63e3d11c0bf69084-7f31" rel="nofollow">http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf626ae-7fe8.html#WS2db454920e96a9e51e63e3d11c0bf69084-7f31</a></p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload