RE: Re[2]: [Dynapi-Dev] buttons bug??

[Pascal <pb...@oi...>]

> Right-mouse click menu disablement can be cross-browser.

sure about IE4 ?

> Anyway,
>
> I have a question about events/our EventMethod...
> (some of the below has been a reference from Scott Andrew's
> web site -- scottandrew.com -- in the Netscape 6 Events article)
>
> So, I beleive (and I could be wrong, so please correct me if
> I am) the model that we are wanting to use is the IE's target
> to document to window. You might think that events are
> working in NS6 with the current release, but they are not.
> Upon closer examination and testing with very extensive
> examples, the events to not trigger correctly. Well, I have
> fixed the event's in NS6 (the reason everything was happening
> more than once is the fact that there is more than one event
> phase -- 3 actually).

As far as I'm aware someone had already posted a fix for this aswell.. and I
noticed
some code in the event code to try and catch it.

> But the problem is NS4's window to
> document to target. If we want the events to behave in the
> same way cross-browser in very complex examples/widgets that
> uses bubbling, than we need to reverse the way that NS4
> captures events (like IE's), and then use our own event
> bubbling method for the bubble (like in IE).

In my memory, this has always been our target.. and I thought the
Eventlistener was
build to make NS work the same as IE.

I'm actually not sure if the bubbling thing is actually working in the
current releases.

> Part of my reorganization consisted of breaking away mouse
> events form the events.js file, and making it a sperate
> "mouse.js" file.
> This way, you can still have create/delete/resize/etc...
> events get triggered, but not have to worry about the
> weighing down the code/processor with mouse events, if they
> are unecessary. (Plus, I saw this as being consistant with
> some if the file structure now, ie. keyevets.js).

Good idea

> Also, because it they are required by the DynAPI (dynapi.js),
> I have made certain files (document.js, object.js, events.js)
> be automatically included when you set the library path.

Not sure if that's the way to go.. there might eventually be lite versions
(again :)
or some other versions of the document/object/event files. In that case you
would
need to be able to switch.. making people get used to including files will
then be
easier for them.

Also, why so "secretive" about your things.. if you fix something try
posting information
or better post a patch.. this could help speed the DynAPI development. If
you fix things
in your code great! but you can also fix it in the DynAPI code aswell (even
better!)


Pascal Bestebroer (pb...@oi...)
Software ontwikkelaar
Oberon Informatiesystemen b.v.
http://www.oibv.com