dynapi-help

Re: [Dynapi-Help] Opera may change its handling of old (and current?) DynAPI versions

[Hallvord R. M. S. <hal...@on...>]

On 15 Aug 2005 at 14:59, Leif W wrote:

> > As you may or may not be aware, older versions of DynAPI do not run
> > well in Opera because they detect Opera as "Opera" and important
> > parts of the script branches for NN and IE only. 

> I believe that is the DynAPI 2 or older way.  Currently we're not doing 
> anything with DynAPI 2.  Ideally I'd like to update the older APIs, but 
> right now I'm spending my time trying to fix bugs for a DynAPI 3 
> release. 

The current versions of DynAPI work fine AFAIK and even if you make 
changes it is very unlikely that the affected websites will upgrade 
their scripts. This is why we want to use browser.js to work around 
it.

> But, it'd be nice if the user can turn the feature on 
> or off globally, as well as per-site, incase we do get something fixed 
> up.  

Browser.js can always be turned off globally either by editing the 
ini-file or by simply deleting the browser.js file from Opera's 
profile folder.

>  Currently DynAPI 3 has moved 
> the browser detect stuff into "dynapi/src/dynapi.js", though some may 
> choose to install just /src/ on the site under a different dirname like 
> /scripts/dynapi/dynapi.js or something.  So I don't think it would 
> affect current or future versions.

Thank you for your feedback!
Since I found an outdated version causing problems for Opera on 
toyota.com with a different directory structure and file name, I'm 
planning to extend the fix to affect all files called "dynlayer.js". 
I hope your conclusion still stands..

Do you have a "live" demonstration site that is guaranteed to always 
run the latest and greatest DynAPI version? If so I would like to add 
that site to our routine test run for browser.js so that we can try 
to look out for problems this causes for upcoming versions.
-- 
Hallvord Reiar Michaelsen Steen
http://www.hallvord.com/


-- 
Hallvord Reiar Michaelsen Steen
http://www.hallvord.com/

Re: [Dynapi-Help] Opera may change its handling of old (and current?) DynAPI versions

[Leif W <war...@us...>]

> From: "Hallvord Reiar Michaelsen Steen" <hal...@on...>
> Sent: 2005 September 03 Saturday 16:42
>
>> On 15 Aug 2005 at 14:59, Leif W wrote:

>> But, it'd be nice if the user can turn the feature on
>> or off globally, as well as per-site, incase we do get something 
>> fixed
>> up.
>
> Browser.js can always be turned off globally either by editing the
> ini-file or by simply deleting the browser.js file from Opera's
> profile folder.

It would be nice to have site by site as well, as it leaves us the 
option to fix DynAPI 2 and other users to upgrade without relearning 
DynAPI 3 and converting custom widgets.

> toyota.com with a different directory structure and file name, I'm
> planning to extend the fix to affect all files called "dynlayer.js".
> I hope your conclusion still stands..

In DynAPI 2, you're looking at two files from the folder 
dynapi/src/lib/dynapi/api/ , so you might want to check dyndocument.js 
as well.

> Do you have a "live" demonstration site that is guaranteed to always
> run the latest and greatest DynAPI version? If so I would like to add
> that site to our routine test run for browser.js so that we can try
> to look out for problems this causes for upcoming versions.

We've got releases up here: http://dynapi.sourceforge.net/releases/ . 
But only 2.5.7 at time of writing, and 3 beta 1 and 2, and CVS in 
dynapi3x.  I'll have to put the other versions.  There should be some 
examples in a sub directory of the same name under each release.

Leif