Thanks - didn’t even think of that. Doh! :)
Guess I overthought that one. :)
Thanks!
Rob
From: Geoff Stearns <[EMAIL PROTECTED]>
Reply-To: Open Source Flash Mailing List <[email protected]>
Date: Tue, 19 Sep 2006 17:54:51 -0400
To: Open Source Flash Mailing List <[email protected]>
Subject: Re: [osflash] swfobject 2.0 prerelease testing
well if the movies don't invoke express install, then the detection will fail and the user will get the alternate content.
so just create alternate content that blends in with the page, and they may never even notice that there's missing movies... then after they update, they'll see all the movies.
On Sep 19, 2006, at 4:36 PM, Robert M. Hall wrote:
Hey Geoff,
Great simple enough - Thanks. I’ll let you know how it works. :)
I guess I have concerns that going that simple route, with the way this specific page and content is designed, is that the other .swfs on the page not invoking expressinstall will be a potential distraction to the user, which is why I was hoping to make them halt on the first frame while the main .swf that does invoke express install does its thing. Anyway – I’ll let you know how it works out. Thanks!
Rob
From: Geoff Stearns <[EMAIL PROTECTED]>
Reply-To: Open Source Flash Mailing List <[email protected]>
Date: Tue, 19 Sep 2006 11:49:56 -0400
To: Open Source Flash Mailing List <[email protected]>
Subject: Re: [osflash] swfobject 2.0 prerelease testing
i don't think you need a fancy system like that... just set your pages up so that only 1 swf on each page is configured to use expressinstall.
On Sep 19, 2006, at 2:02 AM, Robert M. Hall wrote:
Hey Geoff,
I’ve been using your swfObject on every project I’ve pumped out recently (thanks for making my life easier!)
I have an idea/question (and possibly a feature request) about something I’m going to try tackling later this week on a project.
I’ve got a new site I’m working on that has multiple .swf elements on each page of the site, all have at least 3 flash elements/ instances of .swfobject.
I havent tried it yet to see how it might work out – but is there a built in method in swfObject (current or 2.0) to allow the .swfs to communicate (either through swbObjectjavascript /externalinterface or localConnection) that would allow all the flash elements to “agree” upon which of them would present the Express Install window should a user happen upon the site that needs to upgrade?
I want to make sure that the experience of the site is very smooth.
Should I simply make sure that only one of of the .swfs on the page allows express install to be invoked by including the expressinstall.as and proper dialogs in the first frame, and let that one .swf do its magic, and use localconnection to communicate from that .swf to the others on the page to halt in the first frame as they are loaded if the main .swf needs to invoke the express install dialog?
If its not already in there – this might be a nice feature: a master .swf for pages with multiple pieces of flash, that can be designated as the one that will handle the express install – and a mini-framework to include in the others that uses localconnection to halt them on the first frame as the main .swf does its work for upgrades.
If this is already in there and I’ve missed it somehow or its a non-issue – my apologies. If not, let me know if you think this is something worthwhile to pursue – should be fairly simply to implement since localconnection was introduced in Flash player 6, and the code to register the other .swfs should be fairly simple and straightforward with just a few lines to register/listen and halt – just not sure about the timing and instantiation of the the .swf elements via swfobject, if that would have any impact at all.
Thanks!
Rob
From: Geoff Stearns <[EMAIL PROTECTED]>
Subject: [osflash] swfobject 2.0 prerelease testing
.....Also: If anyone has new feature requests for this next version, now is the time to get them out there, so if there is one killer feature that you would like to add in, let me know what it is and i'll see if it's cool enough to make it in the next build :) .......
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org
_______________________________________________
osflash mailing list
[email protected]
http://osflash.org/mailman/listinfo/osflash_osflash.org
_______________________________________________ osflash mailing list [email protected] http://osflash.org/mailman/listinfo/osflash_osflash.org
