I'm glad to hear that it resembles DynAPI. I was thinking about all the
different libraries. They all have the same basic methods and objects (a
document, a canvas and events).
As I mentioned before the most important part of the library is the
development of widgets and development tools. Which is why I offer a type of
specification (very official w3c type looking) with a minimum object which
will support events and the basic properties(X,Y, bgColor and others). That
way all widgets developed can be used with any core. The code would be ultra
light. If you want to run your app only in DOM browsers with pascals code
just include DOMLib core. If you prefer bloated code include DynAPI core.
The difference between all DHTML libraries are mainly technical. They all
have the same purpose they all have the same style code, different
variables, syntax and that's all.
I personally think that DynAPI's biggest achievement except for stability is
Richards site with the huge collection of widgets. It shows how much you can
do if you have the guts. (3d animation and all other crazy quests).
This together with a few working development environments (hopefully DynPRD
amongst them) and with a few good tutorials we can get a community up with a
whole lot of DHTML developers that write widgets thus making developing
DHTML applications a lot easier.
Sorry for the long rambling, flame on ppl
8an
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dynapi-dev
