so let's say, DynAPI 2.01 ?
- Original Message -
From: "Jordi - IlMaestro - Ministral" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, February 21, 2001 1:24 AM
Subject: Re: [Dynapi-Dev] Freeing Memory
> Amen. However Pascal I don't think
e over the top :o)
R.
- Original Message -
From: "Raymond Smith" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, February 21, 2001 12:33 PM
Subject: Re: [Dynapi-Dev] Freeing Memory
___
Dynapi-
ED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, February 21, 2001 3:04 AM
Subject: RE: [Dynapi-Dev] Freeing Memory
> Ok, it then seems I misunderstood the complete discussion.. but I don't
> think everyone was on the same thinking-plane as Robert is, and some other
> people (the few
k bericht-
> Van: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]Namens Jordi -
> IlMaestro
> - Ministral
> Verzonden: woensdag 21 februari 2001 10:25
> Aan: [EMAIL PROTECTED]
> Onderwerp: Re: [Dynapi-Dev] Freeing Memory
>
>
> Amen. However Pascal I don't thin
The audience is listening.
Try not to let these not-so-enthusiastic responses get into you. It happens to
everybody: posting the results of many hours of work, expecting at least not to
be ignored, and then receiving nothing but silence.
I believe you're going the right way. Usually people post
A voice of reason !
There's no flames from this camp.
>From: "Pascal" <[EMAIL PROTECTED]>
>Reply-To: [EMAIL PROTECTED]
>To: <[EMAIL PROTECTED]>
>Subject: RE: [Dynapi-Dev] Freeing Memory
>Date: Wed, 21 Feb 2001 08:54:48 +0100
>
>Well to get this s
Amen. However Pascal I don't think anyone pretends to redo the API. We should
blame Raymond ( as usual :) ) because he introduced the 3 in the name and made
it all look scary.
When we're saying DynAPI3 I understand we're meaning DynAPI2 with better and
cleaner code, not a new API.
Pascal wrote:
pulls out blow torch, flick and ignites a cold blue flame
First off, I can understand your passion, and if you go all the way back to
the very first "lets stop and think about it first, then act" post you will
see that above alpha-next-generation-anything was finish up DynAPI2.
Secondly, be
Well to get this said in time:
I think that any moves towards a DynAPI3 should be on a seperate sourceforge
project (or atleast other location).
I have absolutely no interest in doing everything all over again or even
participating in a venture like that.
The DynAPI2 has been in development for
>I'm 99% sure of this... but this would lead to the question of why they
bothered putting in bit >calculation in the first place...>
That's easy, Javascript was supposed to be as functionally similar to Java
as possible
---
Outgoing mail is certified Virus Free by AVG Free Edition
Download a
Ämne: Re: [Dynapi-Dev] Freeing Memory
>This kind of thing becomes troublesome in javascript.
>
>For instance, bit shifting for multiples of 2 is great except that all my
>tests show that it offers no advantages, and, in fact, is sometimes slower in
>javascript than just multiplyi
Which is what I ment..
:-)
- Original Message -
From: "Raymond Smith" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, February 20, 2001 2:21 PM
Subject: Re: [Dynapi-Dev] Freeing Memory
> That or what Robert eluded to. Someway of remote notat
That or what Robert eluded to. Someway of remote notation of a single
central document.
- Original Message -
From: "Doug Melvin" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, February 20, 2001 5:14 PM
Subject: Re: [Dynapi-Dev] Freeing Memory
&g
How about a multi-user collaborative 'whiteboard' app?
If I see enough interest I could build one fairly quikly..
- Original Message -
From: "Raymond Smith" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, February 20, 2001 2:10 PM
Subject:
; <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, February 20, 2001 1:36 PM
Subject: RE: [Dynapi-Dev] Freeing Memory
> All those tips are great for optimizing performance in compiled code
running
> on Pentium machines. Small problem we here are interpreted code. All cod
All those tips are great for optimizing performance in compiled code running
on Pentium machines. Small problem we here are interpreted code. All code is
evaluated at run time. Anyway that kind of optimization is to try and snip
off milliseconds. Here we are talking about seconds going to waste no
This kind of thing becomes troublesome in javascript.
For instance, bit shifting for multiples of 2 is great except that all my
tests show that it offers no advantages, and, in fact, is sometimes slower in
javascript than just multiplying by 2. (If anyone wants to see a demo of this I
will po
I was gonna say that, but I knew you would and my thread was to long
already...
;O)
From: "Pascal Bestebroer" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, February 20, 2001 1:11 PM
Subject: RE: [Dynapi-Dev] Freeing Memory
> ke.. some thoughts.
>
>
n turn speeds up the site and resduces the mem-footprint.
Doug
- Original Message -
From: "Raymond Smith" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Tuesday, February 20, 2001 12:51 PM
Subject: Re: [Dynapi-Dev] Freeing Memory
> I'm really beginning
den: dinsdag 20 februari 2001 21:51
> Aan: [EMAIL PROTECTED]
> Onderwerp: Re: [Dynapi-Dev] Freeing Memory
>
>
> I'm really beginning to think there are two sides to this issue.
>
> 1) Design Methodology.
> 2) Code Optimization.
>
> 1) Eytan eluded to this here, &q
I'm really beginning to think there are two sides to this issue.
1) Design Methodology.
2) Code Optimization.
1) Eytan eluded to this here, "and then nullify them nothing happens but
when you recreate them still the memory stays stable". Today most sites are
page based, and I think within a c
You could possibly load the same url with a unique paramater passed in the
url. I have yet to try this though.
--
// Robert Rainwater
On 2/20/2001, 2:27:22 PM EST, Pascal wrote about "[Dynapi-Dev] Freeing Memory":
> so on a url change everything is freed?
> couldn't w
ww.dynamic-core.net
> -Oorspronkelijk bericht-
> Van: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]Namens Eytan Heidingsfeld
> Verzonden: dinsdag 20 februari 2001 20:18
> Aan: Dynapi-Dev
> Onderwerp: [Dynapi-Dev] Freeing Memory
>
>
> Since IE is way more popular I
Since IE is way more popular I started with it. I was wrong with my
assumption that nullifying objects (not even talking about html
elements(layers)) does the whole thing. Let me tell you what I discovered:
if you create 1 small object and then nullify them nothing happens but
when you recreat
t;
Till: '[EMAIL PROTECTED]' <[EMAIL PROTECTED]>
Datum: den 12 februari 2001 21:48
Ämne: RE: [Dynapi-Dev] Freeing Memory in IE
>I can confirm this behavior on IE 4.x and NN 4.x. We also noted where the IE
>leak was about 1 - 2Meg, the NN leak was only 20 - 40K. Our applicat
: Monday, February 12, 2001 09:44
To: Dynapi-Dev
Subject: [Dynapi-Dev] Freeing Memory in IE
I have recently found very interesting behavior in IE 5. I used proprietary
code so I don't know about IE4 and NN4 but I will check soon. I used code to
create many DynLayers (520) inside another dyn
I will most certainly have to look into this.
- Original Message -
From: "Eytan Heidingsfeld" <[EMAIL PROTECTED]>
To: "Dynapi-Dev" <[EMAIL PROTECTED]>
Sent: Monday, February 12, 2001 8:43 AM
Subject: [Dynapi-Dev] Freeing Memory in IE
> I have recently
I have recently found very interesting behavior in IE 5. I used proprietary
code so I don't know about IE4 and NN4 but I will check soon. I used code to
create many DynLayers (520) inside another dynlayer(myLayer). Then I called
document.body.removeChild(myLayer) the memory didn't budge. Then I mi
28 matches
Mail list logo
