[temhawk]

Yeah, let me congratulate you as well. It's very nice, I might be getting back to you about this some day if that's ok!

[haku]

No worries! I'll post the code I used here so that you can refer back whenever you want:

First, here is the xhtml I used in the body of my document:

<div id="flashcontent"></div>

Which I styled with this CSS to simulate a basic menu item:

#flashcontent
{
	background: url(no_flash_up.png) no-repeat 0 0;
	width: 463px;
	height: 102px;
}
#flashcontent:hover
{
	background: url(no_flash_down.png) no-repeat 0 0;
}

In the head of the document, I linked to SWFObject.js:

<script type="text/javascript" src="SWFObject.js"></script>

And at the very bottom of swfobject.js, I added this java script:

window.onload = function()
{
	var so = new SWFObject("with_flash.swf", "flashcontent", "463", "103", "8", "#FFFFFF");
	so.write("flashcontent");
}

As far as I can tell, any elements can be set inside the div that I named flashcontent. It is replaced using innerHTML, which is a javascript command that basically overwrites anything that is between the div tags. So you can code your whole menu into there if you want.

[graham08]

I think what we're all waiting for is flash that can be read by search engines so we can got absolutely nuts with it. So that means either Adobe sorting something out with flash (not too likely) or google refining the way it reads flash or object elements (possible). Lets hope it happens sometime soon

[haku]

Someone earlier in this thread said that google can index the text in flash now (if its done right). That will definitely be a big change once people start doing it more.

[temhawk]

Great...

And I thank you for explaining the work you did. I did take a quick look at it before but the JavaScript file was too big!

But it turns out it's not that much, I had thought that you wrote the SWFObject.js thing

[haku]

No no, I can't take credit for that!!!

[dyamni]

and what they regard most important is:

a) quality of content

ease of navigation, and

c) speed.