Hugh, Derrell,
that helped. I got it working now.
Thanks a lot,
Rüdiger
Rüdiger Herrmann wrote:
> Hi Hugh,
>
> maybe you know what's wrong with my next step, too...
>
> I back-ported the qx.Class.patch function (appeared to be the only
> change between 0.7.3 and latest from the 0.7.x legacy
Rüdiger
I'm guessing that it didn't work.
Take a look at the example code in
frontend/application/testrunner/source/class/testrunner/test/Mixin.js to
see it in action and work backwards from there. Check structures in a
debugger.
It's possible also that you can't apply the patch at the "defer" p
On Wed, Sep 10, 2008 at 8:10 AM, Rüdiger Herrmann
<[EMAIL PROTECTED]>wrote:
>
> maybe you know what's wrong with my next step, too...
>
> I back-ported the qx.Class.patch function (appeared to be the only
> change between 0.7.3 and latest from the 0.7.x legacy branch).
>
> Then I created a class (
Hi Hugh,
maybe you know what's wrong with my next step, too...
I back-ported the qx.Class.patch function (appeared to be the only
change between 0.7.3 and latest from the 0.7.x legacy branch).
Then I created a class (see code below) that contains one function
(_idealKeyHandler) that should 'ov
Hugh,
thanks for your explanation. As I am not familiar with the
Javascript prototype thing, I will try to backport the changes in
__addMember to our 0.7.3 code base.
Cheers,
Rüdiger
Hugh Gibson wrote:
> Rüdiger,
>
>> That would be exactly what I need. Only that I am working with the
>> 0.7.
Rüdiger,
> That would be exactly what I need. Only that I am working with the
> 0.7.3 release and can't switch to anything newer in short time.
> The bug doesn't state a target milestone yet, but from the revision
> it looks like the fix was applied after 0.7.3.
> Can you confirm that?
Yes, it
That would be exactly what I need. Only that I am working with the
0.7.3 release and can't switch to anything newer in short time.
The bug doesn't state a target milestone yet, but from the revision
it looks like the fix was applied after 0.7.3.
Can you confirm that? And if so, is there maybe an
> I need to replace a qooxdoo (0.7.x) function from 'outside' (i.e.
> without modifying the qooxdoo source itself.
> In addition, I want to be able to call the original function from
> within the replacement and, of course, keep the this variable
> intact.
Use qx.class.patch. Use this.base(argu
Hi all,
I need to replace a qooxdoo (0.7.x) function from 'outside' (i.e.
without modifying the qooxdoo source itself.
In addition, I want to be able to call the original function from
within the replacement and, of course, keep the this variable intact.
My (very naive) approach was to place th
