I would not say DynAPI (2.5.7) is not up to the task..
It's the DHTML technology itself.. It's just not that fast.
Hell, My app has gotten so big it blows up Netscpae 4.x quite regularly.
This is not a problem with DynAPI tho,
AS we have done benchmarking with pure html, and DHTML (non DynAPI)
And found there is still a problem..
As for IE, I have found that large scale apps CAN be fast and slick,
but rarely are. It really depends on how large scale your app is,
and what optimizaztions you have added..
One optimization I have added is an extra parameter to setHTML
that can tell DynAPI not to store the given HTML in an extra variable..
DynAPI stores the HTML do that it can be gotten faster (or gotten at all in
NS)
I have found this reduces memory usage considerably..
There are many other things you can do,
-> such as event capping (ensure that not too many ondragmove events are
fired in a row.. for instance)
Or using the noevent option of sethtml, or setsize, ect. to block events
from being fired that you will never use.
(myLayer.setHTML('some text',false))
->Using more than one Layer where possible - instead of re-rendering hte
HTML in the same layer..
as rendering html does take resources
ie; if I am not going to be changing a set of HTML then I put it in a
persistant layer,
and simply show/hide it.
->Reduce the number of layers where possible..
I had several buttons around the paremiter of my app which where each in a
seperate layer.
I occured to me that I can put ALL of the buttons into a table in a single
layer and
place that layer behind my viewspace. (setZIndex(-1))
This reduced memory usage and decreased loadtime by a few seconds..
-> Don't preload every-damned-thing at loadtime.. Use a IOElement or a
hidden frame to load content when needed (or just before it's needed)
While the user does have to wait a second for the content to load, they
DON'T have to wait that extra minute or so for the app to load.
-> take full advantage of image commpression and reduction technology.
Saving only 0.5k on an image may not seem like much, but 0.5k (as an
example) over 50 images does add up, especcially for modem users.
----- Original Message -----
From: "Matt Fair" <[EMAIL PROTECTED]>
To: "DynAPI Help" <[EMAIL PROTECTED]>
Sent: Thursday, February 21, 2002 4:33 PM
Subject: [Dynapi-Help] dynapi vs shockwave
> Hello,
> I have been using DynAPI for about a year now and have developed a
> website that uses DynAPI as a graphical editor at Uprint.com. I am
> worried about the scalability and stability of DHTML.
> I am thinking about switching our site over to use Shockwave with Lingo
> to increase stability and speed of the editor.
> Has anyone else created a DynAPI project that uses a lot of layers like
> my editor?
> The compatibility of my site I have limited to just Windows with
> Internet Explorer becuase of the compatibility conflicts.
> What are some peoples sugestion? Have outgrown the usefulness of
> DynAPI, is it not meant for something this big? Would Shockwave with
> Lingo be a better fit for my needs?
> Thanks,
> --
> Matt Fair
> Uprint.com Staff
>
> Gartner Studios, Inc.
> 124 South Second Street
> Stillwater, MN 55082
>
> Phone: 651-351-7700, 888-522-9722
> Fax: 651-351-1408
>
>
> _______________________________________________
> Dynapi-Help mailing list
> [EMAIL PROTECTED]
> https://lists.sourceforge.net/lists/listinfo/dynapi-help
>
_______________________________________________
Dynapi-Help mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dynapi-help
