speed issues traversing the DOM.

[SAM]

Le 11/30/08 10:55 PM, David Mark a écrit :

That is ridiculous.

Not from my side.
If it is what I want, why to say 'ridiculous' ?

If you post it here, it should at least be competent.

Yes and no.
You're there to verify ;-)

The feature detection is the least of the worries at the moment.

We'll say so.
It's too hard for me fighting in english.

And you want it to crash in older browsers?

Yeap, that's of no interest here.
(I defended a long time NN4 ago not so far, today I do not more)

And why would you want to do that? It makes no sense.

I did explain it.
break;

Never mind all of this. Did you fix the leaks?

I tried
(even if I continue to do not well understand what it is)

Well, I suppose Spanish and French are roughly the same.

No, not so much.
As if you could say that Dutch and English are almost same.

And don't believe everything you see (I don't speak Spanish.)

Well, I confusing, perhaps?

So fix your code and forget it (or get a Windows machine.)

Certainly not !
To see all the memory melt like snow in the sun?



SYS

 

[SAM]

Le 11/30/08 10:59 PM, David Mark a écrit :

Again with the French.

Lovely !
And you got the simultaneous translation, happy guy.

That is what I meant (partly.) That fixes the memory leaks and stops
the creation of thousands of useless function objects.

OK.
But that was not my interest at this time.

Since, with Laurent's help, I've progressed (I hope !)
And now I have a single listener for all the body.
And ... it seems to work too with IE.6.

That even works very very well !
No more time to spend looping the divs to set with events, after loading.

I do not understand very well why you didn't give the solution when the
philosopher was running in circle around his divs to show and hide ?

 

[SAM]

Le 11/30/08 11:09 PM, David Mark a écrit :

On Nov 30, 3:57 pm, SAM <[email protected]>
wrote:

But, you attached the listeners with script, creating a closure and
leaking lots of memory in the process.

It was not in that test (I think, I did so much !)
But no importance, I'll try to remember this problem (trouble ?).

You could have used DOM0 as before.

Yes, perhaps, probably, certainly, surely, but it was not the purpose.

IE doesn't set "this" properly when using attachEvent.

IE est une bouse qui nous emmerde tous, tout le monde sait ça.
No, I will not say it in English.

IE has do to what it can, if it can.
Reverse bubbling, leaks of memory, Jscript and so on without end.
Sometimes, surely by chance, some features work with it as with other
browsers.

 

[David Mark]

Le 11/30/08 10:55 PM, David Mark a écrit :



Not from my side.
If it is what I want, why to say 'ridiculous' ?

It just is.

Yes and no.
You're there to verify ;-)


We'll say so.
It's too hard for me fighting in english.



Yeap, that's of no interest here.
(I defended a long time NN4 ago not so far, today I do not more)

Who is talking about NN4?

I did explain it.

Not really.

  break;



I tried
(even if I continue to do not well understand what it is)
Okay.



No, not so much.
As if you could say that Dutch and English are almost same.

I was being facetious.

Well, I confusing, perhaps?
Yes.


Certainly not !
To see all the memory melt like snow in the sun?
 

No, to test your leaky code.

[snip]

 

[David Mark]

Le 11/30/08 10:59 PM, David Mark a écrit :



Lovely !
And you got the simultaneous translation, happy guy.

And how would I know it is a translation?

OK.
But that was not my interest at this time.

Whether it is your interest or not is irrelevant. You posted a very
faulty example.

Since, with Laurent's help, I've progressed (I hope !)
And now I have a single listener for all the body.

The body seems an odd choice.

And ... it seems to work too with IE.6.

That even works very very well !

Glad you approve.

No more time to spend looping the divs to set with events, after loading.

There you go.

I do not understand very well why you didn't give the solution when the
philosopher was running in circle around his divs to show and hide ?

The "philosopher" is constantly going around in circles as he refuses
to learn anything.

[snip]

 

[SAM]

Le 11/30/08 11:29 PM, Jorge a écrit :

See "Objects and this" in: http://javascript.crockford.com/survey.html

Outch ! My god ! to read Crockford in the text ?

I use 'object' and 'this' sometimes, but there it was a little went out
from usual context.

You can get a copy and use it freely if you want to.

Don't worry it was made, and I show it from time to time.
(I'm not yet ready to imagine all those mathematical functions with
gravity and so funny abstractions)
(with my poor last neurone you know)
(tremendous where is it ?)

Chiao

 

[SAM]

Le 12/1/08 12:32 AM, David Mark a écrit :

On Nov 30, 5:48 pm, SAM <[email protected]>
wrote:

Who is talking about NN4?

Là tu commences à m'énerver grave !
You begin to put me out of my nerves.

 

[SAM]

Le 12/1/08 12:37 AM, David Mark a écrit :

And how would I know it is a translation?


Whether it is your interest or not is irrelevant. You posted a very
faulty example.

So sorry.

The "philosopher" is constantly going around in circles as he refuses
to learn anything.

Do you think ? He says he's a good programmer, no ?

 

[Laurent vilday]

David Mark :

Laurent vilday :

It is not a bug, nor is it specific to Safari (e.g. NN6.2 does this.)

Well, that is just a comment in a not tested code after all. At least I
knew the behavior (target is the text node and not the element node as
expected) is exposed by Safari so I though with this little comment I
could help readers to not spend hours to find out why this undesirable
behavior is happening.

You don't need a strict comparison for this. But at least you didn't
sniff for Safari (like jQuery.)

I *never* sniff. However I agree with the ===, but it looks like micro
optimisation to me, not really important.

 

[David Mark]

Le 12/1/08 12:32 AM, David Mark a écrit :



Là tu commences à m'énerver grave !
You begin to put me out of my nerves.

The fact remains that NN4 has no bearing here.

[snip]

 

[David Mark]

Le 12/1/08 12:37 AM, David Mark a écrit :




So sorry.



Do you think ? He says he's a good programmer, no ?

No. He can say he's the Queen of Sheba, but that doesn't make it so.

 

[David Mark]

David Mark :



Well, that is just a comment in a not tested code after all. At least I
knew the behavior (target is the text node and not the element node as
expected) is exposed by Safari so I though with this little comment I
could help readers to not spend hours to find out why this undesirable
behavior is happening.

And if you adjust it slightly, it won't be misleading.

[snip]

 

[SAM]

Le 12/1/08 1:44 AM, David Mark a écrit :

The fact remains that NN4 has no bearing here.

Yes, and then ?

Why couldn't I speak about NN4 ?
That you juge the code of other, is a point.
That you juge of what others are speaking is another point.

I can try to believe you know something about JS (I don't realy know,
did I see a line of code from you ?)
but I can't admit you are alone to say of what we have to talk.

 

[Laurent vilday]

Conrad Lender :

SAM :

It would be lost in translation anyway, there's no equivalent for
emmerder in English. "It encraps us all", perhaps? ... nah, doesn't
have the same ring to it

I would translate it to :
IE is crap screwing us all, everybody knows it.

or perhaps something like :
IE is a fucking horse, everybody knows it.

So many way to say it anyway

 

[SAM]

Le 12/1/08 1:53 AM, Conrad Lender a écrit :

Yeah well, all this isn't exactly news.

No, surely.
Mais ça fait du bien.

You're the one who wanted to write a script *only* for IE.

It was to see what it does with certain routine.
A kind of exercise.

Probably what could cause trouble is that in my test I've also dDBI
(but only where I'ven't to test IE)

David Mark seems to pose himself in defender of "good coding" (without
never showing a simple bit of code) and without any consideration of the
context. And it begins to be tiring.

 

[Laurent vilday]

David Mark :

Laurent vilday :

And if you adjust it slightly, it won't be misleading.

Do you mean adjusting a little comment line in a code *not* copy/pasted,
*not* tested, *not* intended to be executed ? I added this comment
because I though I would not have to argue over and over for the line
below the comment, if I know I would have refrain from posting at all.

All right, you win, you dick is way bigger than mine.

 

[David Mark]

Le 12/1/08 1:53 AM, Conrad Lender a écrit :



No, surely.
Mais ça fait du bien.


It was to see what it does with certain routine.
A kind of exercise.

Probably what could cause trouble is that in my test I've also dDBI
(but only where I'ven't to test IE)

David Mark seems to pose himself in defender of "good coding" (without
never showing a simple bit of code) and without any consideration of the

Never showing a simple bit of code? A quick search of the archives
(or Google) will indicate otherwise.

context. And it begins to be tiring.

You are lucky I mentioned those memory leaks, seeing as you were
completely unaware of the problem (or how to fix it.) Tiring or not,
looks like you might have learned something at this point.

 

[David Mark]

David Mark :
[snip]


All right, you win, you dick is way bigger than mine.

Now you are being sensible. But seriously, just adjust the comment
and/or your memory.

[snip]

 

[SAM]

Le 12/1/08 2:09 AM, Laurent vilday a écrit :

Conrad Lender :

Encraping, a real French specialty ! isn't it ?

I would translate it to :
IE is crap screwing us all, everybody knows it.

not too bad.
(I wouldn't find it)

 

[SAM]

Le 12/1/08 2:47 AM, David Mark a écrit :

On Nov 30, 8:12 pm, SAM <[email protected]>
wrote:

Never showing a simple bit of code? A quick search of the archives
(or Google) will indicate otherwise.

We'll say to me ?
And we'll stop here our incomprehension

OK ?

You are lucky I mentioned those memory leaks,

I thank you for that. And, certainly you'll have to do it again.
But your are tiring to do not explain what about you think or refer.

I meet in some NG another body who did as you do, it was also tiring
(a french NG, no wall of language).

Tiring or not,
looks like you might have learned something at this point.

Not yet, not yet. Just a drop of oil.