I started with DynAPI1, say, two years ago, and got used to crossbrowser issues.
I was there in the very beggining of DynAPI2 and I've participated in almost
all discussions since that day. Normally my involvement in any issue being
discussed depends on the amount of free time I have in that particular moment
and, whereas sometimes It seems I've got nothing to say, I've always been up to
date with the project.
There's no really wisdom source here. All event knowledge is achieved throught
the study of the existing code. Once you know what's in the books ( Nestcape's
events go from window to target, IE's bubble up, DOM goes back and forth ) and
manage to find a half-decent reference, then it is no longer a DHTML issue but a
software engineering issue.
Want to know how do events work in NS6 ? Create an example, pick up your
browser, place several alerts around the code and start loosing lots of hours
trying to understand "why e.target is null when I move the mouse out of this
layer". No magical recipes. I did not sell my soul to Satan.
Last week I had to teach another employee about something DHTML related. I had a
lot of trouble trying to put together all my knowledge in order to make it look
logical. I guess the years, the battles, somehow leave a lot of knowledge hidden
in your brain. You don't know it's there but it pops out when you're in trouble.
90% of my value comes from my experience. If you could see the scars ...
Cya
www.cantir.com/dynapi
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
