Events.js has been updated to use ns6. No other dynapi files still
use is.ns5. Nothing was deleted, ns5 was changed to ns6 because that
is what it is, Netscape 6.
--
Robert Rainwater
On 3/7/2001, 7:45:31 PM EST, Richard wrote about "[Dynapi-Dev] NS6 support":
> Why on earth did ns5 have to
The following is a simple print method for dyndocuments. it forces the
focus to make sure that the sepecified document is the one that get's
printed.
DynDocument.prototype.print=function() {
this.elm.focus();
this.elm.print();
};
--
Michael Pemberton
[EMAIL PROTECTED]
ICQ: 12107010
uh, because we used to call ns6 ns5.
If we put if is.ns5 we will never get true even
though we are still talking about the same browser.
It's redundant code dude.
Just take a look as borwser.js (from
snapshot)
- Original Message -
From:
Richard
Bennett
To: [EMAIL PROTECT
>which version of the api are you using?
Using the current release of 2001-01-25 so it is possible that this has
already been fixed.
oops. is should have been
is.lang=(is.ns) ? navigator.language:navigator.browserLanguage;
Michael Pemberton wrote:
I believe we should add the following line to browser.js
to allow for language detection.
is.lang=(is.ns) navigator.language:navigator.browserLanguage;
--
Michael Pemberton
I believe we should add the following line to browser.js to allow for language
detection.
is.lang=(is.ns) navigator.language:navigator.browserLanguage;
--
Michael Pemberton
[EMAIL PROTECTED]
ICQ: 12107010
Why on earth did ns5 have to be deleted? add ns6
for ease of use, sure, but why delete ns5 and cause allot of confusion?
(Pascal?)
- Original Message -
From:
Doug Melvin
To: [EMAIL PROTECTED]
Sent: Thursday, March 08, 2001 3:50
AM
Subject: [Dynapi-Dev] NS6 suppor
I did a grep.. there was only one instance of
ns5
events.js: line 43
"if (is.ie || is.ns5){"
needs to be changed to:
"if (is.ie || is.ns6){"
---Outgoing mail is certified Virus Free by
AVG Free EditionDownload at: http://www.grisoft.com/html/us_index.cfmChecked
by AVG anti-virus system (htt
I do believe you may fix a whole bunch of your bugs
if you d a grep for ns5
and replace all instances with ns6.
is.ns5 is no longer set in browser.js, yet there
are places in the rest of the code that still use is.ns5
such as line 43 of events.js : "if (is.ie ||
is.ns5){"
---Outgoing mail
Hey Ruairi,
I loaded your revised code an examples and had a few
problems.
1 For some reason, I had to load the two files
individually instead of using the directory * method.
Not sure what caused this.
2 I had to change your opacity.js code to use (is.ns6)
instead of (is.ns5) as the current
Hey Leland,
I just checked the timed animation example under
win98 / ns6.0 and it loaded and ran. Possibly you hit
a glitch coming from my server? You could try it
again. What operating system are you running under?
To Dan, I am working with the bi-threaded and
tri-threaded examples. The or
Even though it's not supported, we need to catch
the vile users of these weak technologies and bounce them to a page of "utter
and total wisdom" so they can be properly assimilated.
- Original Message -
From:
Daniel
Holmen
To: [EMAIL PROTECTED]
Sent: Wednesday, Mar
Hi there,
I posted an opacity extension a while ago, at that time Richard mentioned
that it'd probably be more processor friendly if I'd used thread. So I got
at it and after a long session of looking at thread I finally found the
solution. Copy & Paste from the path animation extension and Tweak
I just tried this out in Mozilla 0.8, and it seems to work fine. In
Netscape 6.0, on the other hand, the page took forever to load, no dynlayer
showed up, and the javascript console showed this error:
DynLayer is not defined
Source file: http://www.merlinsworld.net/src/lib/dynapi/api/dyndocume
Hello.
I've done a page using DynAPI which contains several layers, labels and
DynImages.
If I put a label and try to change the colour when the mouse is over (using
and event listener for onmouseover and onmouseout), I've noticed that the
speed decreseases specially in IE5, and NS6 doesn't hand
No I did not...
I beleive that your suggestion belongs to "optimizations"...
so I 'll wait a little to see if find-out something relative (or someone
else do)...
I am very stressed right now...
Andreas
-Original Message-
From: Cameron Hart [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, M
did you try my suggestion?
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of
> GORTSILAS ANDREAS
> Sent: 07 March 2001 12:28
> To: '[EMAIL PROTECTED]'
> Subject: RE: [Dynapi-Dev] EventMethod fix...
>
>
> YES I know that this is bad for the performance
YES I know that this is bad for the performance!
but at this time it is the only I have... (or better we have)
with out this fix the problem exists (in NS the events of html elements does
NOT forward to the container DynLayer!!!)
Until we find something better it is the only solution (instead o
that redirection
would be done after everything (dynapi code) has already
loaded..
better idea would be
to use a real browser sniffer on your start page, that could then
redirect.
I'm not saying I
WILL rip it out, but it's of no use to the DynAPI code, seeing that Opera can't
be supporte
Isn't it handy to be able to detect Opera, and
redirect to another version?
- Original Message -
From:
Pascal
To: [EMAIL PROTECTED]
Sent: Wednesday, March 07, 2001 11:48
AM
Subject: RE: [Dynapi-Dev] Opera
recognition in browser.js
if I remember I'll
fix
if I remember I'll
fix it tonight, but this is VERY LOW on any priority list (not that there is a
real list though)
I might actually
take out opera code, because it's not being used (browser object is not a real
browser sniffer)
Pascal Bestebroer ([EMAIL PROTECTED])Software
ontwikkelaarObe
Darryl
Cousins "unofficial" help file is now on the official dynapi site, under
documentation.
Darryl
if you're out there, let me know if you have any updates you want to make
(couldn't find your email address).
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROT
yes, now we need a macintosh developer :-)
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Raymond
> Smith
> Sent: 07 March 2001 02:36
> To: [EMAIL PROTECTED]
> Subject: Re: [Dynapi-Dev] [ dynapi-Bugs-226673 ] IE 4 & 5 Macintosh
>
>
> God praise, a
which
version of the api are you using? this may have been fixed already in the
development version.
-Original Message-From:
[EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of
[EMAIL PROTECTED]Sent: 07 March 2001 00:13To:
[EMAIL PROTECTED]Subject: [Dynapi-Dev] Bug
in which case this code may be specific to how you code but not necessary
for the rest of the api users...
i think running this in event method might slow things down a tad, it's
possible that you could put something similar in dynlayer.js that does this
when the layer is created and when you set
As I've said before, DynAPI does't recognize Opera
if Opera identifies as anything other than IE. This bug is REALLY simple to fix;
just replace line 10 in browser.js with this one:
if ((b=="Opera") ||
(navigator.userAgent.indexOf("Opera")>0)) this.b = "opera";
Voila, it recognizes Opera
26 matches
Mail list logo
