Hi,
It looks like a good and clever approach. Nearly every day I learn a new
Javascript trick.
Fabian Jakobs wrote:
>
> I knew I've missed something ;-)
>
> Here it comes:
>
> http://truecode.blogspot.com/2006/08/object-oriented-super-class-method.html
>
> mfg Fabian
>
--
View this mess
Title: AW: [qooxdoo-devel] Inheritance and calling superclass methods
I knew I've missed something ;-)
Here it comes:
http://truecode.blogspot.com/2006/08/object-oriented-super-class-method.html
mfg Fabian
-Ursprüngliche Nachricht-
Hi!
welcome to the qooxdoo list :)
Hi!
welcome to the qooxdoo list :)
Could you provide a link to the article?
Maybe it also would be nice to explain the idea in some short sentences.
Thanks.
Sebastian
Fabian Jakobs schrieb:
> Hi,
>
>
>
> I just dicovered a blog entry on ajaxian, which proposes gives a good
> overview
Hi,
I just dicovered a blog entry on ajaxian, which proposes gives
a good overview over the „calling superclass methods“ problem. I
really like the solution he comes up with. What is especially nice ist hat he
doesn’t neet wrapper functions or any extra objects. Maybe this could be
a n
Hi, Hugh!
Hugh Gibson wrote:
>> Can anybody give us a hint please, why this ask for help is being
>> ignored? This fact is certainly not encouraging us to meet people's
>> expectations for providing even more articles (e.g. for qooxdoo
>> 0.6).
>
>
> We're focusing on our wxPython implementati
> Can anybody give us a hint please, why this ask for help is being
> ignored? This fact is certainly not encouraging us to meet people's
> expectations for providing even more articles (e.g. for qooxdoo 0.6).
We're focusing on our wxPython implementation of our product at the moment
(pre-exist
Andreas Ecker schrieb:
> Can anybody give us a hint please, why this ask for help is being
> ignored? This fact is certainly not encouraging us to meet people's
> expectations for providing even more articles (e.g. for qooxdoo 0.6).
>
> Sorry, just being sad, :-(
>
> Andreas
>
Hi Andreas, I ca
Howdy!
David Perez wrote:
> If the documentation were a wiki, I would have updated
> http://old.qooxdoo.org/documentation/inheritance
Directly from http://qooxdoo.org/documentation :
"We are currently switching from a typical CMS to a wiki engine for our
entire homepage. All community members
Hi Til,
You were right, I meant this.superclass and also it is dangerous.
The Dojo approach for managing inheritance seems smarter:
http://manual.dojotoolkit.org/WikiHome/DojoDotBook/Book20
They provide the "this.inherited" mechanism for this purpose.
Til Schneider schrieb:
proto.func = f
>>> proto.func = function() {
>>> // How can I call here BaseClass.func()?
>>> return 'In derived class';
>>> }
>>>
>> BaseClass.func.call(this, param1, param2);
> Or even better:
>
> proto.func = function() {
> superclass.func.call(this);
> return 'In derived class';
>
>
Thanks Til,
Or even better:
proto.func = function() {
superclass.func.call(this);
return 'In derived class';
}
In this way, we don't need to know the name of the superclass.
If the documentation were a wiki, I would have updated
http://old.qooxdoo.org/documentation/inheritance
Til
> proto.func = function() {
> // How can I call here BaseClass.func()?
> return 'In derived class';
> }
BaseClass.func.call(this, param1, param2);
-
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceFo
Hi,
I haven't found any example in the Qooxdoo source code about calling a
superclass method of a redefined method of a superclass.
Is this easily possible?
Sample source code:
function BaseClass() {
}
BaseClass.extend(Object, 'BaseClass');
proto.func = function() {
return 'In base class'
13 matches
Mail list logo
