From: "Hallvord Reiar Michaelsen Steen" <[EMAIL PROTECTED]>
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
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Dynapi-Help mailing list
Dynapi-Help@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dynapi-help
