Hi,
Yes you're right, speed and memory is always an issue.
I have some tests here using different ways of building layers, that we were
trying out a while back:
http://www.dynapi.f2s.com/dynapi/tcanvas/
I haven't done any serious stress testing of the latest builds, since the
memory leak was solv
> I'm sorry Stephan, but you are wrong.
> Dynapi is not very optimized when it comes to creating layers. At all.
> I have an API which will be part of a cross-browser framework, which already
> is lightyears faster and more robust then DynAPI. Not to belittle DynAPI, as
As some now, I have develo
Well, do you have any suggestion for speed
improvements for DynAPI? Will your API be available to
the public?
You see, I really like the coding structure use by
DynAPI. It's very easy and fun to work with. Widgets
are very easy to create and understand. DOM-API looks
good but it's coding struct
> You see, I really like the coding structure use by
> DynAPI. It's very easy and fun to work with. Widgets
> are very easy to create and understand. DOM-API looks
> good but it's coding structure is different from
> DynAPI. I only wished that they had made to coding
> structure DynAPI compatible
La dirección de correo a la que ha escrito no existe o es incorrecta,
por favor compruebe que la dirección es correcta, y si el problema persiste
pongase en contacto con nosotros en el e-mail: [EMAIL PROTECTED]
___
Dynapi-Dev mailing list
[EMAIL PROTEC
hi,
< Creating 1000(!) layers with HTML and set properties
> 4000 ms - IE5
Sounds good, but we've had Dynapi experiments running at this speed too, but
you have to keep stuff a lot more basic than now.
Usually I optimize the DynAPI-based code I'm using for a certain
application, by stripping out
Hello Everyone,
I must salute the creators of DynAPI for creating such
a fascinating API. I really like the object structure
and it's easy-of-use. But there's something that I'm
concerned about, and that's speed!
What good is a pickup-minivan if it doesn't have
sufficient horse power?
After do
Hello Raymond,
> The long and short of it is that DynAPI really needs
> to do something about the speed at which layers are
> created and the amount of browser-resources to
> maintain a layer.
when you say something is "slow" (which is always a relative value)
you also have to give some referen
I'm sorry Stephan, but you are wrong.
Dynapi is not very optimized when it comes to creating layers. At all.
I have an API which will be part of a cross-browser framework, which already
is lightyears faster and more robust then DynAPI. Not to belittle DynAPI, as
it was what got my started on the J
You wrote:
>What good is a pickup-minivan if it doesn't have
>sufficient horse power?
The analogy is interesting considering the 200(Mhz) "horse power" engine
used for testing.
I would imagine the response on any dynamic graphic program (such as today's
more modern games or flash applications) is
You will find that there are actually a great number of speed
enhancements that have been made within the DynAPI. One notable one is
"precreation". This means that if you create a layer and all its
children, the children can be inserted into the parent before the parent
is added to the document.
11 matches
Mail list logo
