On Mon, Nov 23, 2009 at 06:15, Fritz Zaucker <[email protected]> wrote:
> The remaining question I have is:
>
> Why are callAsync() and addListener() doing this differently (except
> perhaps
> for historical reasons)?
>
> Wouldn't it be more consistent if both would have a scope parameter?
> Of course, this would be a backward-incompatible change ...
>
That's exactly the problem. It is a historical issue and the change would
not be backward-compatible. I would not be opposed to a change, even
non-backward-compatible, if the migration scripts handled it, I could make
the change to the method but I don't have the time right now to work on the
migration scripts.
Tobias, I would recommend creating a ticket for this. If someone is willing
to write the migration scripts, I'll do the code changes. This will also
need Andreas Ecker's approval, as it is a significant API change.
Derrell
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
