AbstractTagImpl.fireEvent() argument order

[James Margaris <jm...@nexaweb.com>]

The most common use for this method is to pass in an event name and a
client event, which means you have to call it like:

fireEvent("myEvent",null,null,event);

I would like to swap the argument order so that the client event comes
second. I think this is a LOT more intuitive as the last two arguments
are barely ever used.

Opinions?

James Margaris

RE: AbstractTagImpl.fireEvent() argument order

[Michael Turyn <MT...@nexaweb.com>]

That seems o.k., except that I'd rather not encourage the JS-oid tendency to
leave off arguments, especially as null != <undefined>.  
  
I personally don't mind putting in two null arguments, regardless of where
they are; why not keep "fireEvent" for a two-argument method, and something
better (I don't feel like suggesting something right now, given that I just
remembered that Icame up with "AbstractBlackBoxWidgetBridge") for the full-
argument version?