dynapi-dev

[Dynapi-Dev] Widget Initializers

[Robert R. <rra...@ya...>]

I was wondering if it would be better on memory to use the same object
for the prototype initializers in the widgets.

Like:
List.prototype = new DynLayer()

could be changed to
List.prototype = DynLayer.static

where
DynLayer.static = new DynLayer();

If you initialized DynLayer.static in the DynLayer, would it be
possible to use this same object for initializing all of the
prototypes that subclass the dynlayer(the widgets)?

-- 
// Robert Rainwater
----------------------
DynAPI Snapshots: http://dynapi.sourceforge.net/snapshot/
DynAPI Homepage: http://dynapi.sourceforge.net/

Re: [Dynapi-Dev] Widget Initializers

[Dan S. <dy...@fu...>]

That's a no-no.  Every instance of any of the widgets would be using the same JavaScript object and wreck havoc, try it and you'll see there's no better way than using standard prototyping.

Dan


On Wed, Feb 07, 2001 at 02:59:24AM -0500, Robert Rainwater wrote:
> 
> I was wondering if it would be better on memory to use the same object
> for the prototype initializers in the widgets.
> 
> Like:
> List.prototype = new DynLayer()
> 
> could be changed to
> List.prototype = DynLayer.static
> 
> where
> DynLayer.static = new DynLayer();
> 
> If you initialized DynLayer.static in the DynLayer, would it be
> possible to use this same object for initializing all of the
> prototypes that subclass the dynlayer(the widgets)?
> 
> -- 
> // Robert Rainwater
> ----------------------
> DynAPI Snapshots: http://dynapi.sourceforge.net/snapshot/
> DynAPI Homepage: http://dynapi.sourceforge.net/
> 
> 
> 
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev

[Dynapi-Dev] NS 4.0 bugfixing

[Jordi \ilMaestro\ M. <jmi...@or...>]

I have updated CVS with new versions of dynapi.js, dynlayer.js and events.js. Now all methods always return a value, so those older NS's don't complain. Besides, the inline.js extension was not
working because NS 4.0 does not allow to reassign a parameter to another value. I fixed that by using a temp variable.

Cya.

Re[2]: [Dynapi-Dev] Widget Initializers

[Robert R. <rra...@ya...>]

But wouldn't they be sharing the same methods, but not the same
properties, because those are reassigned in the widget constructor.

-- 
// Robert Rainwater

On 2/7/2001, 4:13:04 PM EST, Dan wrote about "[Dynapi-Dev] Widget Initializers":

> That's a no-no.  Every instance of any of the widgets would be using the same JavaScript object and wreck havoc, try it and you'll see there's no better way than using standard prototyping.

> Dan


> On Wed, Feb 07, 2001 at 02:59:24AM -0500, Robert Rainwater wrote:
>> 
>> I was wondering if it would be better on memory to use the same object
>> for the prototype initializers in the widgets.
>> 
>> Like:
>> List.prototype = new DynLayer()
>> 
>> could be changed to
>> List.prototype = DynLayer.static
>> 
>> where
>> DynLayer.static = new DynLayer();
>> 
>> If you initialized DynLayer.static in the DynLayer, would it be
>> possible to use this same object for initializing all of the
>> prototypes that subclass the dynlayer(the widgets)?
>> 
>> -- 
>> // Robert Rainwater
>> ----------------------
>> DynAPI Snapshots: http://dynapi.sourceforge.net/snapshot/
>> DynAPI Homepage: http://dynapi.sourceforge.net/
>> 
>> 
>> 
>> _______________________________________________
>> Dynapi-Dev mailing list
>> Dyn...@li...
>> http://lists.sourceforge.net/lists/listinfo/dynapi-dev

> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev


----------------------
DynAPI Snapshots: http://dynapi.sourceforge.net/snapshot/
DynAPI Homepage: http://dynapi.sourceforge.net/