Hi Jim,

R U sure to use swep.Pool.getInstance().aTest(), but getting an error??

Bye,

Andreas

On Thu, 2008-09-18 at 13:02 -0700, Jim Hunter wrote:
> OK, I trimmed everything down, changed the inheritance and I am still
> having an issue. With the code below, when I try and access the method
> aTest() I get an exception saying that it is not a function. So what
> is wrong with the code? It's pretty straight forward.
> 
> Thanks,
> Jim
> 
> qx.Class.define("swep.Pool", 
> {
>     type: "singleton",
>     extend: qx.util.ObjectPool,
> 
>     construct: function()
>     {
>         qx.util.ObjectPool.call(this);
>     },
> 
>     properties: 
>     {
>         poolSizes: 
>         {
>             _legacy: true,
>             type: "object"
>         }
>     },
>     
>     members:
>     {
>         aTest : function()
>         {
>            alert(2);
>         }
>     }    
> });
> 
> 
> 
> On Tue, Sep 16, 2008 at 6:52 PM, Derrell Lipman
> <[EMAIL PROTECTED]> wrote:
>         On Tue, Sep 16, 2008 at 9:15 PM, Jim Hunter
>         <[EMAIL PROTECTED]> wrote:
>                 I am porting my application classes by hand over to
>                 the new .8 and on my second class I ran into a bit of
>                 trouble. First, it is subclassed from a qooxdoo class
>                 that is not longer available, qx.util.manager.Object.
>                 Since this is a class that mostly just manages lists
>                 of objects I changed it to descend from
>                 qx.core.Object. That part was fine, but every method
>                 in my members: section are coming up as "is not a
>                 function" when I try and use them. Should I have
>                 subclassed it from another class? The methods all show
>                 up in the API viewer but just don't show up when I try
>                 and use them. Here is the class code (it is a
>                 modification of the pooling class that I think came
>                 from the contributions area):
>                 
>         
>         For object pooling, there's the class qx.util.ObjectPool.  As
>         with much of a port from 0.7 to 0.8, it's not just a matter of
>         changing class names.  The interface has changed.
>         qx.util.ObjectPool appears to be a much simpler and cleaner
>         class than qx.util.manager.Object was.
>         
>         Derrell
>         
>         
>         
>         
> 
> 
> 
> 
> 
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________ qooxdoo-devel mailing list 
> qooxdoo-devel@lists.sourceforge.net 
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel


-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to