Hi DL,
I and the rest of the team would prefer to be using SWFObject - we
certainly don't want a situation that prevents _any_ users from seeing
Laszlo apps. There are a few things that are stopping us from using it:
a) SWFObject ExpressInstall uses an actionscript stub to do player
version detection, which has to be compiled into each application. This
can probably be added to the LFC, but it won't run as early as the
current Javascript/VBScript scheme used today - no big deal really.
b) We have an elaborate scheme that doesn't use the ActiveX/Java bridge
for Flash/browser communication, which allow _setCanvasAttribute to work
in many more browsers, including Safari. This also prevents the long
'Starting Java...' messages in Firefox. That said, we do want
_setCanvasAttribute to use the ActiveX/Java bridge where available, and
fall back when it's not.
If you're interested, we'd love to have your help with this. Let me
know if you have questions or comments!
Regards,
Max Carlson
OpenLaszlo.org
DL wrote:
On 16 Oct 2006 at 15:42, Max Carlson wrote:
This is a long standing bug - after several conversations with d~1 I was
never able to reproduce. I tried many different versions of IE. It
sounds like it comes down to localization or something else that makes
his version of IE different from ours - QA hasn't been able to reproduce
this issue either
Max
That thread was started by another user with similar (albeit rare)
symptoms of lzx.swf rendering blank in IE (some versions). Encouraging
that I am no more in a minority of one.
Although in the minority, a few other users of IE have since reported
similar problems in laszlosystems forum. EOLAS was another issue.
LaszloSystems QA may not have reproduced the same symptoms in IE .. but
that does not mean they are not still there (for some IE users)!
..
Problem (in my IE browser) first arose /post lps-3.1/ .. when you
dropped using nested <object><embed> (Satay method) in embed.js.
See line 158/159 in embed.js ..
"// write out a hidden div with an object tag to force an upgrade in IE
only"
To test this theory I tried using an earlier version (3.0.2) of embed.js
and this cured my IE rendering problem.
But I decided to switch permanently to SWFObject.js.
The symptoms were reported here ..
_http://www.laszlosystems.com/developers/community/forums/showthread.php?s=a7e618da5be0f8cf82d8d319e669d32f&threadid=5850_
<http://www.laszlosystems.com/developers/community/forums/showthread.php?s=a7e618da5be0f8cf82d8d319e669d32f&threadid=5850>
..
Also the question was raised in initial thread .. is there a case for
dropping embed.js and relacing with SWFObject.js?
Adobe.com has endorsed the SWFObject code .. see reference to 3rd party
software at Adobe site.
_http://www.adobe.com/devnet/flash/articles/swfobject.html_
Added SWFObject features include ExternalInterface (Flash 8) and Java
Integration Kit (pre Flash 8).
..
In this thread ..
_http://www.laszlosystems.com/developers/community/forums/showthread.php?s=a7e618da5be0f8cf82d8d319e669d32f&threadid=7311_
<http://www.laszlosystems.com/developers/community/forums/showthread.php?s=a7e618da5be0f8cf82d8d319e669d32f&threadid=7311>
for backwards compatibility I considered using a "hybrid" solution -
i.e. cutting out the <object></object> block of code in embed.js and
replacing with a call to SWFObject.js.
But this seems to be a retrograde step and duplication of code. So
abandoned.
Better in my view to switch to using SWFObject.js entirely, and add any
additional backwards compable functions like _lzSetCanvasAttribute (but
using SWFObject API to implement set canvas attribute ). It is easy to
pass vars via SWFObject.
d~l
