Re: [Dynapi-Dev] loading *.js files

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

> From: Ji=F8=ED Bla=BEek / comcare <jir...@co...>
> Received: Sat, 15 Oct 2005 05:40:44 PM EDT
> =

> I am updating an old site done in dynAPI 2.54 to work with dynapi3.

Hopefully you've noticed it's not a drop-in replacement.  Some things are=
 a
bit different... widgets, function names, arguments (type or order)... ge=
neral
API differences.

> Due to my lack of knowledge of both Javascript and dynAPI, I don't know=
 how
> to include my .js files.

Old JS files can't be dropped in and expected to automatically work... bu=
t to
include files, check the stuff in "examples".  View the source.

> It used to be like this:
> =

> DynAPI.include('data.js','./scripts/')

If you need to create new widgets, you probably want to put them under sr=
c,
maybe make your own folder, but otherwise follow the tips for creating
widgets.

dynapi/docs/docs/tip.createwidget.html
 =

> How do i do this with the new library syst=E9m? I have the DynAPI 2.9

The current release is dynapi-3.0.0-beta2.  It is a dump of the CVS as of=

early August 2005.  Several bugs had been fixed since the beta1 release.

> changelog, but I still don't understand. Is there anywhere else to find=

more
> information on this?

Most of the formal documentation is under the docs folder, and code is in=
 the
examples folder.

If you are converting, it may be easier to identify all the widgets you u=
se in
DynAPI2, then look through the examples, make some of your own modificati=
ons
as needed, and so determine which of the DynAPI3 widgets you can use, and=
 then
have an idea of what (if anything) you might need to create or port.

Without downloading anything, you can look at
http://dynapi.sourceforge.net/releases/ to find the most current version =
of
the API.  I try to update the CVS there when I add something to real CVS,=
 but
it is not an exact mirror and not automated so it can lag behind actual C=
VS.


Leif