The whole prototype code is THE way that Javascript does inheriting (read
the Netscape references) The problem we are facing is something we did our
selves, in the constructor we should only SET the properties, not create
properties or methods, that causes problems.
This also means that the oncre
Then when does it run, and is it able to be controlled... ie: can we force
it to run, such as in several other common languages?
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Jared
Nuzzolillo
Sent: Monday, December 11, 2000 10:00 AM
To: [EMAIL PROTECTED
It might be better to run the timer until you have successfully
created x number of layers, using their oncreate event.
--
// Robert Rainwater
On 12/11/2000, 11:44:23 PM EST, Michael wrote about "[Dynapi-Dev] Speed test":
> With all the talk of splitting the API and attempting to make it smal
With all the talk of splitting the API and attempting to make it smaller
/ faster, I thought it would be useful to be able to see how long it actually
take a page to download / render without the use of a stop watch.
Here's what I did:
I added the following line before "DynAPI = {"
var Start
hi,
In attached example the slideTo and slideBy used to
run if one parameter is set to null
can this be included in the new version again?
ie: if (!x) x = this.x;
in the same attachement the slideTo function calls
itself in it's own event listener, this no longer works,
is this by desig
On the face of it I don't think it's entirely necessary unless your goal is
to create a large hierarchy of objects, in which case you could just use the
SuperClass object as your base object and subclass everything from there.
The WidgetX model will create an extra instance of the DynLayer class
per page memory management was abandoned, as far as I know, in Netscape
version 2.0. IE3+ and NS4+ use a variation of the mark and sweep garbage
collection algorithm.
___
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/lis
At 2000-12-12 00:03 , you wrote:
>I think it's always better not to say MyObject.prototype=new DynObject
(That makes me understand SuperClass better...)
>Reasoning: We shouldn't want instance variables to be prototype variables.
>All variables initialized within the DynObject constructor will be
>> Wouldn't it be better to say:
>> MyObject.prototype = DynObject.prototype
>I guess this would only create a pointer, so that changes to
>MyObject.prototype would affect DynObject.prototype
Very good point.. so should we then loop through the prototypes?..
Assigning the individual functions, b
> I was wondering the point of this line when inheriting objects:
>
> MyObject.prototype = new DynObject();
It's so that any changes to DynObject.prototype at runtime will
be reflected in MyObject.prototype
> Wouldn't it be better to say:
> MyObject.prototype = DynObject.prototype
I guess this
> Wouldn't it be better to say:
> MyObject.prototype = DynObject.prototype
I think this would cause problems when more than one object inherits
from the DynObject.
Using "new" ensures that the widget prototype is unique and won't be
shared with other widgets that also use DynObject as their paren
I think it's always better not to say MyObject.prototype=new DynObject
Reasoning: We shouldn't want instance variables to be prototype variables.
All variables initialized within the DynObject constructor will become part
of the prototype.
Why do we want this? Variables should be initialized at t
Already done and working. I've actually got quite a large amount of fixes/changes
coming due to a lot of problems with widgets using the new inline creation system.
Currently there's only 1 very perplexing problem when using Button in another widget
(pushpanel/scrollpane in particular) that i
The main issue with DynImage is getting the images width and height
when it is done loading. Then the dynimage has to update itself and
invoke some kind of event saying its ready. So ideally, you don't
need to specify the w/h if you want to use the actual width/height.
Because in the Button wid
I was wondering the point of this line when inheriting objects:
MyObject.prototype = new DynObject();
Wouldn't it be better to say:
MyObject.prototype = DynObject.prototype
Because in your MyObject constructor you will be saying:
this.DynObject = DynObject;
this.DynObject();
so all of the
How about an updateText() function added to the label widget that
would call setText().
--
// Robert Rainwater
On 12/10/2000, 5:18:11 PM EST, Scott wrote about "[Dynapi-Dev] Label text selection":
> Yeah, that's something I overlooked. setText needs to be called in order to
> see an immediat
Thanks, I still have a few things i want to
implement in the keyevents, but as a preliminary release I think it works. Now
all I need is some feedback and compability reports. And by all means, go right ahead and include the keyboard events - the
more possability I get the feedback I need to
Hi!
I think I've found a bug in dynimage.js that shows up in NS4.7 but not in
IE4 (NS6 hangs on my Win NT 4.0 :-( ).
File: gui/dynapi.js
File date: 20:27, 8 Dec 2000; taken from the beta .zip in SourceForge
yesterday.
Line: 100
was: DynImage.timerId=setTimeout(DynImage+'.loadercheck()',25);
shou
The problem with this (dynapi) situation and your example is that in the
DynAPI not ALL code is browser independend, in your example all text would
be different for every language.
"..but it's important to see all the versions together in order to be sure
that any change is done simultaneoulsy"
I'm afraid you missed the point of this thread, but at the same time, you've
stumbled upon another feature that would be nice to have. Especially since
the purpose of this API is to provide functions for a user interface.
So, why not build in Internationalization functions? A single file can
cont
As long as you are sure the german writer, the english writer and the french
writer are writing exactly the same, and there is one person telling them what
do they have to write and what do they have to tell. Otherwise, you'll end up
with a site that depending on the language you choose, the infor
Oh come on. If you're supposed to write an international site for visitors
in 5 languages, would you really consider writing (and editing) all the
different texts, labels, figure captions, etc in ONE file only and
separating the languages by deeply nested if`s ?
Would you say, ok, I don't know ger
something I have done in my Dynacore distribution (see post from yesterday).
Pascal Bestebroer
[EMAIL PROTECTED]
http://www.oibv.com
-Oorspronkelijk bericht-
Van: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]Namens Robert Rainwater
Verzonden: maandag 11 december 2000 14:05
Aan: DynAPI De
If you mean doing something like this:
if (is.ns)
DynLayer.prototype.setHTML = function() {}
}
Then, it looks like you would only use it in the setX/Y, setBgImage,
and setHTML functions. However, this would also require moving
the BrowserDetection function into the dynapi.js or dynlayer.js,
be
hi all.
is this event-bug in ns6 (events are triggered multiple times) fixed already?
florian.
___
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
25 matches
Mail list logo
