Stuff I am building:
Ted Patrick - Events & Community @ Adobe Systems
Note: This is the personal blog of Ted Patrick. The opinions and statements voiced here are my own.
Eolas Workaround
DIGG IT!
0
Comments
Published
Thursday, October 09, 2003
at
1:57 PM
.
The Eolas issue has 2 distinct criteria: 1. The controls are created dynamically from script loaded from another location. 2.The controls do not reference remote data.Thus far I have only seen 1 recommended class of solution. Another option is potentially to modify object properties after object instantiation, thus working around the MS rules so to speak.
Initially object tags must not reference remote data in the declaration and thus do not warn the user about their use. Next a small bit of JavaScript modifies the object tag as the page loads. We then use a player external method to load data into the player via LoadMovie via JavaScript.
Here is a sample:
http://www.powersdk.com/eolas/index.html
I am unsure of a few specifics:
1. Can you edit object properties after the page loads and still not violate the rules
2. Can you modify object properties to point to external data
In the second item, the Macromedia .CAB URL and the violate this rule, but can be left out if there is a player 4+ supporting the JavaScript loadMovie. In this case the external data is being requested within the player, not from within the Object tag. This workaround also has some advantages as you can pass data to the url.
The JavaScript looks like this:
window.sample.classid="clsid:D27CDB6E-AE6D-11cf-96B8-444553540000"
window.sample.codebase="http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab#version=6,0,0,0"
window.sample.width=800
window.sample.height=600
window.sample.LoadMovie(0,"sample.swf")
Not sure if I broke the EOLAS rules, but it works with all current content. In the sample, I removed Netscape embed to isolate the IE only issue. I am not sure if the nested Embed will trigger a warning as is standard practice for Flash authors.
Personally, I wish they would just pay the bill and be done with it. Can you imagine Redmond actually licensing something legally?
Cheers,
ted ;)
Where to find me:
Ted on Twitter - @AdobeTed
Ted on Adobe Groups
Ted on LinkedIn
Ted on Facebook
Ted at Adobe
Latest
- __q_click >> Click Event Queue in FUI V2 Component...
- IE ActiveX Hole and impact to Flash
- No Work Today, Gone Diving! :)
- Using Targets with ASR Remoting
- hacking startDrag() to provide a solid _droptarget...
- Announcement :: PowerSDK Version 16 Released with ...
- A Procedural View > Visustin Review
- Strings as an array
- FCHS - Flash CrossDomain HTTP Server
- What is PowerSDK FLOW?
Lists
Links
Jobs
Flex JobsArchives
- May 2003
- June 2003
- July 2003
- August 2003
- September 2003
- October 2003
- November 2003
- December 2003
- January 2004
- February 2004
- March 2004
- April 2004
- May 2004
- June 2004
- July 2004
- August 2004
- September 2004
- October 2004
- November 2004
- December 2004
- January 2005
- February 2005
- March 2005
- April 2005
- May 2005
- June 2005
- July 2005
- August 2005
- September 2005
- October 2005
- November 2005
- December 2005
- January 2006
- February 2006
- March 2006
- April 2006
- May 2006
- June 2006
- July 2006
- August 2006
- September 2006
- October 2006
- November 2006
- December 2006
- January 2007
- February 2007
- March 2007
- April 2007
- May 2007
- June 2007
- July 2007
- August 2007
- September 2007
- October 2007
- November 2007
- December 2007
- January 2008
- February 2008
- March 2008
- April 2008
- May 2008
- June 2008
- July 2008
- August 2008
- September 2008
- October 2008
- November 2008
- December 2008
- January 2009
- February 2009
- March 2009
- April 2009
- May 2009
- June 2009
0 Responses to “Eolas Workaround”
Post a Comment