While opera 6 or less should use the _opera
library..
Opera 7 is fully DOM and should use the _dom
libary: it's pretty fast too.
I will tast and prove as many of the theories I've
posted today and post my results..
It'll be a long night.. but it's nice to finally be
back into the DynAPI
had a thought..
there are at least half a dozen 'flavours' or
branches of mozilla.. (not to mention versions)
Maybe it would be most logical to treat all mozilla
branhces as just that.. branches of mozilla..
so instead of ua.ns6 you would have
ua.mozilla..
You could then ad a single var (st
being as ns6 is really just mkozilla.. should we
treat mozilla as ns6?
I will go that way for now and see what
happens..
for now mozilla is
"other"..
It seems that nothing is working under mozilla
(1.2.1)
I guess this is where I will start my
efforts..
Note.. there are still mouse errors under opera
7
I've noticed that in the examples all of the files
are included..
this means that (for instance) the mouseevent files
are included in the create example.. which does not use the
mouseevents..
( do correct me if I am wrong)
Lines 290 - 293 dynapi.js
> // DynLayer
> if (dynapi.ua.ns4)
> this.add('dynapi.api.DynLayer','dynlayer_ns4.js','DynDocument');
> else if (dynapi.ua.ie)
> this.add('dynapi.api.DynLayer','dynlayer_ie.js','DynDocument');
> else if (dynapi.ua.opera)
> this.add('dynapi.a
If you are going to submit changes in this method rather than using the
patch board..
how about giving a line number?
:-)
- Original Message -
From: "Raymond Irving" <[EMAIL PROTECTED]>
To: "DynAPI-Dev" <[EMAIL PROTECTED]>
Sent: Thursday, February 13, 2003 5:49 PM
Subject: [Dynapi-Dev] C
Hello Everyone,
In an effort to make dynapi 3.0 more flexible with
newly released DOM browsers (that we've not added to
the dynapi.ua) the following changes are require:
Rename dynlayer_ns6 to dynlayer_dom.js
Note: Opera v7 can work with dynlayer_dom.js but the
current IE compatible codes found
Building n-tier Applications with DynAPI 3.0
Creating n-tier web applications with DynAPI 3.0 has never been easier. With the support for remote scripting and synchronous connections both client and server can send and receive data without the need to refresh the web page.
Figure 1.
With DynAPI 3.
Building n-tier Applications with DynAPI 3.0
Creating n-tier web applications with DynAPI 3.0 has never been easier. With the support for remote scripting and synchronous connections both client and server can send and receive data without the need to refresh the web page.
Figure 1.
With DynAPI 3
--- Leif W <[EMAIL PROTECTED]> wrote:
> Ok, so where do I start adding / modifying code to
> add some features like
> Drag & Snap. I'm thinking somewhere in the onmove
> event.
IMO I would recommend that the Snap functions be
placed in a file call dragsnap.js and be placed in the
api/ext directo
Typo correction:
Or maybe both target/source layers need the SNAPable boolean set?
- Original Message -
From: "Leif W" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, February 13, 2003 10:17 AM
Subject: [Dynapi-Dev] Drag & Snap
> Or maybe both target/source layers need the
Ok, so where do I start adding / modifying code to add some features like
Drag & Snap. I'm thinking somewhere in the onmove event.
I'll need to first make some decisions about functionality. Do I add
attributes like (boolean) doSnap and (+t,+r,+b,+l) snapBorder to the (either
static or dragged)
13 matches
Mail list logo
