dFrameAPI is built on DynAPI 2.5.7.
The dynAPI libraries used by dFrameAPI are:
§
dynapi.js
dynapiLib.js:
This file is the concatenation of the following files:
§
api.* (browser.js,
dyndocument.js, dynlayer.js)
§
event.*
§
gui/dynimage.js
§
gui/label.js
dynapiLib-Scroll.js
: for NS4, in order to manage windows scrolls the dynapiLib-Scroll.js file is
loaded and includes:
§
util/thread.js
§
util/pathanim.js
§
gui/button.js
§
gui/buttonimage.js
§
gui/viewport.js
§
gui/pushpanel.js
§
gui/scrollbar.js
Those 3
files, dynapi.js, dynapiLib.js and dynapiLib-Scroll.js are stored in the dFrameAPI/lib
directory.
In
addition the complete DynAPI library is included in the dFrameAPI.zip file and
the original tree structure can be found in the dFrameAPI/dynapi directory. Those
libraries can be included in applications as shown in the example of the DynAPI
examples pages.
As all
objects of dFrame are dynlayers methods of dynlayers are also methods of
dFrameAPI objects.
But
results of those methods may not correspond to what is required.
Example: If you use the show(false) method of a Button the Button is hidden and the Bar that contains it is reorganized. If you use the setVisible method (dynlayer method) of a Button you will be able to hide the Button but not to reorganize the Bar.
However
some DynAPI methods can be useful:
Example: DynAPIObject.getWidth(): Returns the width in pixels of an object. Useful if you created a DFrame indicating percentages as dimensions or if the object was created by dFrameAPI (Bars, Buttons and Menus)
Some
widgets (objects built with DynAPI objects) can also be very useful. We used
the List widget in the followinf samples:
file: exemple.billing.html
file: advanced.XML.html