s there any advantage to using
> DynAPI.include
> over
>
> ?
>
> - Original Message -
> From: "Robert Rainwater" <[EMAIL PROTECTED]>
> To: "DynAPI Help List" <[EMAIL PROTECTED]>
> Sent: Monday, January 29, 2001 1:26 PM
> Subje
If you build your own package set or your want to include a whole
package, then the DynAPI.include is best.
DynAPI.include("dyanpi.api.*")
is easier than:
...etc.
--
// Robert Rainwater
On 1/29/2001, 7:50:57 PM EST, Doug wrote about "[Dynapi-Help] another thing..":
I see.
Is there any advantage to using
DynAPI.include
over
?
- Original Message -
From: "Robert Rainwater" <[EMAIL PROTECTED]>
To: "DynAPI Help List" <[EMAIL PROTECTED]>
Sent: Monday, January 29, 2001 1:26 PM
Subject: Re: [Dynapi-Help] another thing..
We aren't loading every file. addPackage just sets up the package, so
when you say:
DynAPI.include("dynapi.gui.*")
then it knows what files to include.
--
// Robert Rainwater
On 1/29/2001, 5:59:01 PM EST, Doug wrote about "[Dynapi-Help] another thing..":
> I noti
I notice the following is STILL in
dynapi.js.
Why are we loading EVERY damned .js
file?
No wonder we have a footprint bigger than my
own..
can someone please explain the following to
me?
DynAPI.document=false;DynAPI.addPackage('dynapi');DynAPI.addLibrary('dynapi.api',["browser","dynlay
