>> qx.ui.table.TablePaneScroller.prototype._updateContent = function()
>> {
>> //
>> // Is the table disposed?
>> //
>> if (this.isDisposed())
>> {
>> return; // bomb out
>> };
>> //
>> // Otherwise call normal _updateContent
>> //
>> this._unsafe_updateContent();
>> };
>>
>>
>>
> What we could do is to save a reference to the overwritten method in the
> patch phase. We could either rename it as you did or store the
> overwritten function in the function object of the new method. It could
> then be called like this:
>
> arguments.callee.original.call(this, ...);
>
Sebastian just pointed me to one problem with this solution. The method
from the mixin may be included into several classes and since only
refernces to the function of the mixin are copied to the classes, it is
not possible to use the function object to store the overwritten method.
The solutions I see are:
1. rename the original function. Problem: may cause name conflicts
2. generate a wrapper around the included function: Problem may cause a
runtime overhead on function calls
3. document a way to solve this with the current infrastructure in the Wiki
This feature will not be available in the 0.7 pre release since the time
frame for it is too short but I think that the final release will have
such a feature in one way or another. In the mean time you can take a
look at the 0.7 pre release and we can discuss the best solution for all
of us.
Best Fabian
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
