dynapi-dev — List related to the current DynAPI Core development

Re: [Dynapi-Dev] TCanvas vs. DynLayer

[Doug M. <do...@cr...>]

I'm not working on mem leak at the moment.
Nor am I working on 'cool' stuff.
I'm trying to pay the rent, and if I'm lucky, maybe even afford some
groceries.

----- Original Message -----
From: "Lasse Lindgård" <la...@li...>
To: <dyn...@li...>
Sent: Friday, February 16, 2001 5:59 AM
Subject: RE: [Dynapi-Dev] TCanvas vs. DynLayer


> More importantly than upfront performance:
> Does it reduce the memory leak ?
>
> If not then performance will be on a freight train to swap-land in no time
> anyways.
>
> My current DynAPI pages eat a meg or more pr. reload. It is not a big
> problem at my 256mb machine.  But just the thoughts of my clients 32mb
> machines makes me shiver.
>
> Any news on the memoryleak front ?
> Is anybody working on it at all or are everybody busy doing "cool" stuff
> instead ?
>
> For DynAPI ever to be useful. We really need to get that memory problem
> fixed.
>
> /Lasse
>
>
> --__--__--
>
> Message: 6
> From: "Eytan Heidingsfeld" <ey...@tr...>
> To: "Dynapi-Dev" <dyn...@li...>
> Date: Fri, 16 Feb 2001 14:18:56 +0200
> Subject: [Dynapi-Dev] TCanvas vs. DynLayer
> Reply-To: dyn...@li...
>
> This is a multi-part message in MIME format.
>
> ------=_NextPart_000_0002_01C09823.65DE2AF0
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: 7bit
>
> I'd love to test performance one against the other. The only test I did
was
> create 100 layers and check the times. In IE TCanvas was 200 ms faster and
> in NS it was 1300(canvas) to 10000(dynlayer).
>
> I'd love you guys to start tearing my canvas to shreds.
>
> Included in the zip are:
> tcanvas.js
> browser.js
>
> they need to be included in the document(working on adding .include)
>
> 8an
>
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev


---
Outgoing mail is certified Virus Free by AVG Free Edition
http://www.grisoft.com/html/us_index.cfm
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.231 / Virus Database: 112 - Release Date: 2/12/01

Re: [Dynapi-Dev] DynAPI new event

[Doug M. <do...@cr...>]

I would not recommend modifiying events.js
You COULD extend events.js (the same way events.js extends Dynlayer.js)
and put your code in IE_events.js or some such.

----- Original Message -----
From: "Gilles Bayon" <gil...@la...>
To: <dyn...@li...>; <dyn...@li...>
Sent: Friday, February 16, 2001 5:40 AM
Subject: [Dynapi-Dev] DynAPI new event


> Hello
>
> IE accept more events than those declared in DynAPI (for exemple
> onmouseenter , onresizestart ...) how could I modify the file events.js so
> that DynAPI could work with this new event. I want to make listener on a
> Dynlayer with this new event.
>
> In events.js, I have modify the fct
> DynLayer.prototype.captureMouseEvents
> with this line
>  elm.onmouseenter
>
=elm.onmousedown=elm.onmouseup=elm.onmouseover=elm.onmouseout=elm.onclick=el
> m.ondblclick=DynLayer.prototype.EventMethod;
>
> and the fct
> DynDocument.prototype.captureMouseEvents
> with this line
>  this.doc.onmouseenter
>
=this.doc.onmousemove=this.doc.onmousedown=this.doc.onmouseup=this.doc.oncli
> ck=this.doc.ondblclick=DynDocument.prototype.EventMethod;
>
> and the fct
> DynDocument.prototype.releaseMouseEvents
> with this line
>  this.doc.onmouseenter =this.doc.onmousemove = this.doc.onmousedown =
> this.doc.onmouseup = this.doc.onclick = this.doc.ondblclick = function(e)
> { return false };
>
> I have try to make a dynlayer and an eventlistener like this
>
> mylayer=new DynLayer(null,400,100,50,50);
> mylayer.setBgColor('red')
> mylayer.setVisible(true)
>
> var l = new EventListener(mylayer);
> l.onmouseenter = function(e) {
>  var o = e.getTarget();
>  alert('EventListener onmouseenter )
> }
>
> mylayer.addEventListener(mylayer);
>
> but nothing happens, if someone could help me, I will apreciate.
>
> Thanks.
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev


---
Outgoing mail is certified Virus Free by AVG Free Edition
http://www.grisoft.com/html/us_index.cfm
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.231 / Virus Database: 112 - Release Date: 2/12/01

Re: [Dynapi-Dev] new DynDocument

[Michael P. <mp...@ph...>]

I found the attched code as part of an old dynacore release (2000.11.12).  It may need
a bit or tweaking to make it work with the latest dynapi release. (just check the
method names etc.)

If you have any problems, I can look into it further for you.

Richard Emberson wrote:

> Michael Pemberton wrote:
>
> > Frames.
>
> Any examples?
>
> >
> >
> > Richard Emberson wrote:
> >
> > > In the file dynapi.js a DynDocument is created:
> > >
> > >                 DynAPI.document=new DynDocument(self);
> > >
> > > As far as I can tell this is the only place in the code base or examples where
> > > a DynDocument is created. In the file dyndocument.js the DynDocument object has
> > > the attributes:
> > >
> > > DynDocument.dyndocs = [];
> > > DynDocument.dyndocsID = [];
> > >
> > > which seems to imply that there can be more than one DynDocument. Is there any
> > > example of such an occurance?
> > >
> > > Thanks.
> > >
> > > Richard Emberson
> > >
> > > _______________________________________________
> > > Dynapi-Dev mailing list
> > > Dyn...@li...
> > > http://lists.sourceforge.net/lists/listinfo/dynapi-dev
> >
> > --
> > Michael Pemberton
> > mp...@ph...
> > ICQ: 12107010
> >
> > _______________________________________________
> > 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

--
Michael Pemberton
mp...@ph...
ICQ: 12107010

Re: [Dynapi-Dev] new DynDocument

[Richard E. <emb...@co...>]

Michael Pemberton wrote:

> Frames.

Any examples?

>
>
> Richard Emberson wrote:
>
> > In the file dynapi.js a DynDocument is created:
> >
> >                 DynAPI.document=new DynDocument(self);
> >
> > As far as I can tell this is the only place in the code base or examples where
> > a DynDocument is created. In the file dyndocument.js the DynDocument object has
> > the attributes:
> >
> > DynDocument.dyndocs = [];
> > DynDocument.dyndocsID = [];
> >
> > which seems to imply that there can be more than one DynDocument. Is there any
> > example of such an occurance?
> >
> > Thanks.
> >
> > Richard Emberson
> >
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> > http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>
> --
> Michael Pemberton
> mp...@ph...
> ICQ: 12107010
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev

Re: [Dynapi-Dev] new DynDocument

[Michael P. <mp...@ph...>]

Frames.

Richard Emberson wrote:

> In the file dynapi.js a DynDocument is created:
>
>                 DynAPI.document=new DynDocument(self);
>
> As far as I can tell this is the only place in the code base or examples where
> a DynDocument is created. In the file dyndocument.js the DynDocument object has
> the attributes:
>
> DynDocument.dyndocs = [];
> DynDocument.dyndocsID = [];
>
> which seems to imply that there can be more than one DynDocument. Is there any
> example of such an occurance?
>
> Thanks.
>
> Richard Emberson
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev

--
Michael Pemberton
mp...@ph...
ICQ: 12107010

[Dynapi-Dev] new DynDocument

[Richard E. <emb...@co...>]

In the file dynapi.js a DynDocument is created:

                DynAPI.document=new DynDocument(self);

As far as I can tell this is the only place in the code base or examples where
a DynDocument is created. In the file dyndocument.js the DynDocument object has
the attributes:

DynDocument.dyndocs = [];
DynDocument.dyndocsID = [];

which seems to imply that there can be more than one DynDocument. Is there any
example of such an occurance?

Thanks.


Richard Emberson

RE: [Dynapi-Dev] mousedown in ns4 /mac

[Pascal <pb...@oi...>]

Mac people test !

I'll add it to the cvs tonight or this weekend.

Pascal Bestebroer (pb...@oi...)
Software ontwikkelaar
Oberon Informatiesystemen b.v.
http://www.oibv.com 

> -----Oorspronkelijk bericht-----
> Van: dyn...@li...
> [mailto:dyn...@li...]Namens Michael Buerge
> Verzonden: vrijdag 16 februari 2001 15:30
> Aan: dyn...@li...
> Onderwerp: [Dynapi-Dev] mousedown in ns4 /mac
> 
> 
> something from the mac front:
> 
> the mousedown-event couldn't be used in ns4  on the mac, 
> because when the
> mouse is held down,  ns4 shows the context-menu.
> by canceling the browserevent this can be supressed.
> the following line in DynLayer.prototype.EventMethod does that:
> 
>    // prevents ns4 on the mac from displaying the 
> context-menu when holding
> the mouse pressed
>    if (is.ns4 && (e.type=="mousedown") && is.platform == 'mac')
> evt.cancelBrowserEvent();
> 
> please test this!
> this should make it into CVS, as it fixes an important 
> mac-bug. (if it works
> as expected in all situations, of course)
> 
> --
> Michael Buerge 
> 
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
> 

[Dynapi-Dev] mousedown in ns4 /mac

[Michael B. <mb...@st...>]

something from the mac front:

the mousedown-event couldn't be used in ns4  on the mac, because when the
mouse is held down,  ns4 shows the context-menu.
by canceling the browserevent this can be supressed.
the following line in DynLayer.prototype.EventMethod does that:

   // prevents ns4 on the mac from displaying the context-menu when holding
the mouse pressed
   if (is.ns4 && (e.type=="mousedown") && is.platform == 'mac')
evt.cancelBrowserEvent();

please test this!
this should make it into CVS, as it fixes an important mac-bug. (if it works
as expected in all situations, of course)

--
Michael Buerge 

RE: [Dynapi-Dev] TCanvas vs. DynLayer

[Pascal <pb...@oi...>]

Yes, Dynlayer and dyndocument use the same base class to inherit from.
dynobject contains all parent-child relations (adding,removing,deleting,
etc)

Also events are extending the dynobject, so dynlayer and dyndocument also
share that same extension (no differences between the code).. should make
developing things easier (having one object that contains the code, others
simply use it)

it looks like its working great (the release has been out for a while now,
haven't heard of big problems or found myself.. all Dynapi examples work
correctly with dynacore)



Pascal Bestebroer (pb...@oi...)
Software ontwikkelaar
Oberon Informatiesystemen b.v.
http://www.oibv.com

> -----Oorspronkelijk bericht-----
> Van: dyn...@li...
> [mailto:dyn...@li...]Namens Michael
> Pemberton
> Verzonden: vrijdag 16 februari 2001 14:43
> Aan: dyn...@li...
> Onderwerp: Re: [Dynapi-Dev] TCanvas vs. DynLayer
>
>
> do you mean dynlayer+dyndocument both inheriting from dynobject?
>
> Pascal wrote:
>
> > I already did some of these split ups in dynacore.. and it
> works ok, but is
> > not such a big speed increase (maybe a small increase when
> creating many
> > layers at initialisation)
> >
> > I split up things like sethtml, setx+sety, so you might
> want to look at that
> > before having to code it yourself :)
> >
> > I want to introduce all those changes to DynAPI aswell, but
> I think we
> > should first make sure NS6 works correctl aswell (not sure
> how many problems
> > there still are though).
> >
> > If you and Robert find it ok (main developers)  I will try
> to include these
> > optimisations, and also add the dyndocument idea
> (dynlayer+dyndocument both
> > inheriting from dyndocument)
> >
> > cya,
> >
> > Pascal Bestebroer (pb...@oi...)
> > Software ontwikkelaar
> > Oberon Informatiesystemen b.v.
> > http://www.oibv.com
> >
> > > -----Oorspronkelijk bericht-----
> > > Van: dyn...@li...
> > > [mailto:dyn...@li...]Namens Jordi -
> > > IlMaestro
> > > - Ministral
> > > Verzonden: vrijdag 16 februari 2001 14:21
> > > Aan: dyn...@li...
> > > Onderwerp: Re: [Dynapi-Dev] TCanvas vs. DynLayer
> > >
> > >
> > > Speed optimization can always be introduced. In fact, the
> > > latest precreation
> > > code that caused some old bugs to reappear and some people to
> > > complain about the
> > > API going backwards was introduced in order to speed up layer
> > > creation,
> > > something that was not a problem until people started wanting
> > > hundreds, even
> > > thousands of layers onscreen.
> > >
> > > I've been tempted to suggest this many times but I didn't
> > > want to spawn another
> > > "code split-up" argument. Some critical methods like, say,
> > > moveTo or setSize
> > > might speed up by doing.:
> > >
> > > if(is.ns) DynLayer.prototype.moveTo = function A
> > > else DynLayer.prototype.moveTo = function B
> > >
> > > I'll try myself in see what happens
> > >
> > > Pascal wrote:
> > >
> > > > me again :)
> > > >
> > > > I don't think this test is really useable.
> > > > Your current Tcanvas code misses ALOT of things DynLayer
> > > takes care of.
> > > >
> > > > DynLayer sets sizes, z-index,clipping,bgimages in
> > > initialisation (and also a
> > > > few other style properties.. note that setting a style
> > > property is what
> > > > slows everything down)  I once did some optimization tricks
> > > to the dynlayer,
> > > > by removing sizes/clipping etc.. this speeds up things BIG
> > > TIME, but also
> > > > brakes useability for a large amount of widgets, and is
> > > less flexible.
> > > >
> > > > DynLayer has code included for fast child-creation.. even
> > > though there are
> > > > no child layers in your test, this code is still called
> > > (function calls).
> > > > This could be made faster in dynlayer, but for now is more
> > > readable for
> > > > developers.  Do another test with layers containing a large
> > > amount child
> > > > layers.. Dynlayer's precreation will probably be faster.
> > > >
> > > > shreded enough? ;)
> > > >
> > > > Pascal Bestebroer (pb...@oi...)
> > > > Software ontwikkelaar
> > > > Oberon Informatiesystemen b.v.
> > > > http://www.oibv.com
> > > >
> > > > > -----Oorspronkelijk bericht-----
> > > > > Van: dyn...@li...
> > > > > [mailto:dyn...@li...]Namens Eytan
> > > > > Heidingsfeld
> > > > > Verzonden: vrijdag 16 februari 2001 13:19
> > > > > Aan: Dynapi-Dev
> > > > > Onderwerp: [Dynapi-Dev] TCanvas vs. DynLayer
> > > > >
> > > > >
> > > > > I'd love to test performance one against the other. The only
> > > > > test I did was
> > > > > create 100 layers and check the times. In IE TCanvas was 200
> > > > > ms faster and
> > > > > in NS it was 1300(canvas) to 10000(dynlayer).
> > > > >
> > > > > I'd love you guys to start tearing my canvas to shreds.
> > > > >
> > > > > Included in the zip are:
> > > > > tcanvas.js
> > > > > browser.js
> > > > >
> > > > > they need to be included in the document(working on
> > > adding .include)
> > > > >
> > > > > 8an
> > > > >
> > > >
> > > > _______________________________________________
> > > > 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-Dev mailing list
> > Dyn...@li...
> > http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>
> --
> Michael Pemberton
> mp...@ph...
> ICQ: 12107010
>
>
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>

RE: [Dynapi-Dev] TCanvas vs. DynLayer

[Eytan H. <ey...@tr...>]

I'm working on memory leak as we speak. I told the list that I found a
method in which after a refresh all the memory gets reduced. I'll tell you
when I have finished with my memory tests.
8an

RE: [Dynapi-Dev] TCanvas vs. DynLayer

[<la...@li...>]

More importantly than upfront performance:
Does it reduce the memory leak ?

If not then performance will be on a freight train to swap-land in no time
anyways.

My current DynAPI pages eat a meg or more pr. reload. It is not a big
problem at my 256mb machine.  But just the thoughts of my clients 32mb
machines makes me shiver.

Any news on the memoryleak front ?
Is anybody working on it at all or are everybody busy doing "cool" stuff
instead ?

For DynAPI ever to be useful. We really need to get that memory problem
fixed.

/Lasse


--__--__--

Message: 6
From: "Eytan Heidingsfeld" <ey...@tr...>
To: "Dynapi-Dev" <dyn...@li...>
Date: Fri, 16 Feb 2001 14:18:56 +0200
Subject: [Dynapi-Dev] TCanvas vs. DynLayer
Reply-To: dyn...@li...

This is a multi-part message in MIME format.

------=_NextPart_000_0002_01C09823.65DE2AF0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit

I'd love to test performance one against the other. The only test I did was
create 100 layers and check the times. In IE TCanvas was 200 ms faster and
in NS it was 1300(canvas) to 10000(dynlayer).

I'd love you guys to start tearing my canvas to shreds.

Included in the zip are:
tcanvas.js
browser.js

they need to be included in the document(working on adding .include)

8an

RE: [Dynapi-Dev] TCanvas vs. DynLayer

[Eytan H. <ey...@tr...>]

I'm not talking about that. I'm talking about changing the way of creating
objects. Instead of using
a = new DynLayer()
aparent.addChild(a)
and in those lines of code the following happening
creation of element
assignElement
precreate stuff
...

just adding a create method and calling it.
I have just proven that it works a lot faster (in NS about a ninth in 100
layers).

8an

Re: [Dynapi-Dev] TCanvas vs. DynLayer

[Michael P. <mp...@ph...>]

do you mean dynlayer+dyndocument both inheriting from dynobject?

Pascal wrote:

> I already did some of these split ups in dynacore.. and it works ok, but is
> not such a big speed increase (maybe a small increase when creating many
> layers at initialisation)
>
> I split up things like sethtml, setx+sety, so you might want to look at that
> before having to code it yourself :)
>
> I want to introduce all those changes to DynAPI aswell, but I think we
> should first make sure NS6 works correctl aswell (not sure how many problems
> there still are though).
>
> If you and Robert find it ok (main developers)  I will try to include these
> optimisations, and also add the dyndocument idea (dynlayer+dyndocument both
> inheriting from dyndocument)
>
> cya,
>
> Pascal Bestebroer (pb...@oi...)
> Software ontwikkelaar
> Oberon Informatiesystemen b.v.
> http://www.oibv.com
>
> > -----Oorspronkelijk bericht-----
> > Van: dyn...@li...
> > [mailto:dyn...@li...]Namens Jordi -
> > IlMaestro
> > - Ministral
> > Verzonden: vrijdag 16 februari 2001 14:21
> > Aan: dyn...@li...
> > Onderwerp: Re: [Dynapi-Dev] TCanvas vs. DynLayer
> >
> >
> > Speed optimization can always be introduced. In fact, the
> > latest precreation
> > code that caused some old bugs to reappear and some people to
> > complain about the
> > API going backwards was introduced in order to speed up layer
> > creation,
> > something that was not a problem until people started wanting
> > hundreds, even
> > thousands of layers onscreen.
> >
> > I've been tempted to suggest this many times but I didn't
> > want to spawn another
> > "code split-up" argument. Some critical methods like, say,
> > moveTo or setSize
> > might speed up by doing.:
> >
> > if(is.ns) DynLayer.prototype.moveTo = function A
> > else DynLayer.prototype.moveTo = function B
> >
> > I'll try myself in see what happens
> >
> > Pascal wrote:
> >
> > > me again :)
> > >
> > > I don't think this test is really useable.
> > > Your current Tcanvas code misses ALOT of things DynLayer
> > takes care of.
> > >
> > > DynLayer sets sizes, z-index,clipping,bgimages in
> > initialisation (and also a
> > > few other style properties.. note that setting a style
> > property is what
> > > slows everything down)  I once did some optimization tricks
> > to the dynlayer,
> > > by removing sizes/clipping etc.. this speeds up things BIG
> > TIME, but also
> > > brakes useability for a large amount of widgets, and is
> > less flexible.
> > >
> > > DynLayer has code included for fast child-creation.. even
> > though there are
> > > no child layers in your test, this code is still called
> > (function calls).
> > > This could be made faster in dynlayer, but for now is more
> > readable for
> > > developers.  Do another test with layers containing a large
> > amount child
> > > layers.. Dynlayer's precreation will probably be faster.
> > >
> > > shreded enough? ;)
> > >
> > > Pascal Bestebroer (pb...@oi...)
> > > Software ontwikkelaar
> > > Oberon Informatiesystemen b.v.
> > > http://www.oibv.com
> > >
> > > > -----Oorspronkelijk bericht-----
> > > > Van: dyn...@li...
> > > > [mailto:dyn...@li...]Namens Eytan
> > > > Heidingsfeld
> > > > Verzonden: vrijdag 16 februari 2001 13:19
> > > > Aan: Dynapi-Dev
> > > > Onderwerp: [Dynapi-Dev] TCanvas vs. DynLayer
> > > >
> > > >
> > > > I'd love to test performance one against the other. The only
> > > > test I did was
> > > > create 100 layers and check the times. In IE TCanvas was 200
> > > > ms faster and
> > > > in NS it was 1300(canvas) to 10000(dynlayer).
> > > >
> > > > I'd love you guys to start tearing my canvas to shreds.
> > > >
> > > > Included in the zip are:
> > > > tcanvas.js
> > > > browser.js
> > > >
> > > > they need to be included in the document(working on
> > adding .include)
> > > >
> > > > 8an
> > > >
> > >
> > > _______________________________________________
> > > 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-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev

--
Michael Pemberton
mp...@ph...
ICQ: 12107010

[Dynapi-Dev] DynAPI new event

[Gilles B. <gil...@la...>]

Hello

IE accept more events than those declared in DynAPI (for exemple
onmouseenter , onresizestart ...) how could I modify the file events.js so
that DynAPI could work with this new event. I want to make listener on a
Dynlayer with this new event.

In events.js, I have modify the fct
DynLayer.prototype.captureMouseEvents
with this line
 elm.onmouseenter
=elm.onmousedown=elm.onmouseup=elm.onmouseover=elm.onmouseout=elm.onclick=el
m.ondblclick=DynLayer.prototype.EventMethod;

and the fct
DynDocument.prototype.captureMouseEvents
with this line
 this.doc.onmouseenter
=this.doc.onmousemove=this.doc.onmousedown=this.doc.onmouseup=this.doc.oncli
ck=this.doc.ondblclick=DynDocument.prototype.EventMethod;

and the fct
DynDocument.prototype.releaseMouseEvents
with this line
 this.doc.onmouseenter =this.doc.onmousemove = this.doc.onmousedown =
this.doc.onmouseup = this.doc.onclick = this.doc.ondblclick = function(e)
{ return false };

I have try to make a dynlayer and an eventlistener like this

mylayer=new DynLayer(null,400,100,50,50);
mylayer.setBgColor('red')
mylayer.setVisible(true)

var l = new EventListener(mylayer);
l.onmouseenter = function(e) {
 var o = e.getTarget();
 alert('EventListener onmouseenter )
}

mylayer.addEventListener(mylayer);

but nothing happens, if someone could help me, I will apreciate.

Thanks.

RE: [Dynapi-Dev] TCanvas vs. DynLayer

[Pascal <pb...@oi...>]

I already did some of these split ups in dynacore.. and it works ok, but is
not such a big speed increase (maybe a small increase when creating many
layers at initialisation)

I split up things like sethtml, setx+sety, so you might want to look at that
before having to code it yourself :)

I want to introduce all those changes to DynAPI aswell, but I think we
should first make sure NS6 works correctl aswell (not sure how many problems
there still are though).

If you and Robert find it ok (main developers)  I will try to include these
optimisations, and also add the dyndocument idea (dynlayer+dyndocument both
inheriting from dyndocument)

cya,

Pascal Bestebroer (pb...@oi...)
Software ontwikkelaar
Oberon Informatiesystemen b.v.
http://www.oibv.com

> -----Oorspronkelijk bericht-----
> Van: dyn...@li...
> [mailto:dyn...@li...]Namens Jordi -
> IlMaestro
> - Ministral
> Verzonden: vrijdag 16 februari 2001 14:21
> Aan: dyn...@li...
> Onderwerp: Re: [Dynapi-Dev] TCanvas vs. DynLayer
>
>
> Speed optimization can always be introduced. In fact, the
> latest precreation
> code that caused some old bugs to reappear and some people to
> complain about the
> API going backwards was introduced in order to speed up layer
> creation,
> something that was not a problem until people started wanting
> hundreds, even
> thousands of layers onscreen.
>
> I've been tempted to suggest this many times but I didn't
> want to spawn another
> "code split-up" argument. Some critical methods like, say,
> moveTo or setSize
> might speed up by doing.:
>
> if(is.ns) DynLayer.prototype.moveTo = function A
> else DynLayer.prototype.moveTo = function B
>
> I'll try myself in see what happens
>
> Pascal wrote:
>
> > me again :)
> >
> > I don't think this test is really useable.
> > Your current Tcanvas code misses ALOT of things DynLayer
> takes care of.
> >
> > DynLayer sets sizes, z-index,clipping,bgimages in
> initialisation (and also a
> > few other style properties.. note that setting a style
> property is what
> > slows everything down)  I once did some optimization tricks
> to the dynlayer,
> > by removing sizes/clipping etc.. this speeds up things BIG
> TIME, but also
> > brakes useability for a large amount of widgets, and is
> less flexible.
> >
> > DynLayer has code included for fast child-creation.. even
> though there are
> > no child layers in your test, this code is still called
> (function calls).
> > This could be made faster in dynlayer, but for now is more
> readable for
> > developers.  Do another test with layers containing a large
> amount child
> > layers.. Dynlayer's precreation will probably be faster.
> >
> > shreded enough? ;)
> >
> > Pascal Bestebroer (pb...@oi...)
> > Software ontwikkelaar
> > Oberon Informatiesystemen b.v.
> > http://www.oibv.com
> >
> > > -----Oorspronkelijk bericht-----
> > > Van: dyn...@li...
> > > [mailto:dyn...@li...]Namens Eytan
> > > Heidingsfeld
> > > Verzonden: vrijdag 16 februari 2001 13:19
> > > Aan: Dynapi-Dev
> > > Onderwerp: [Dynapi-Dev] TCanvas vs. DynLayer
> > >
> > >
> > > I'd love to test performance one against the other. The only
> > > test I did was
> > > create 100 layers and check the times. In IE TCanvas was 200
> > > ms faster and
> > > in NS it was 1300(canvas) to 10000(dynlayer).
> > >
> > > I'd love you guys to start tearing my canvas to shreds.
> > >
> > > Included in the zip are:
> > > tcanvas.js
> > > browser.js
> > >
> > > they need to be included in the document(working on
> adding .include)
> > >
> > > 8an
> > >
> >
> > _______________________________________________
> > 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
>

Re: [Dynapi-Dev] TCanvas vs. DynLayer

[Jordi - I. - M. <jmi...@or...>]

Speed optimization can always be introduced. In fact, the latest precreation
code that caused some old bugs to reappear and some people to complain about the
API going backwards was introduced in order to speed up layer creation,
something that was not a problem until people started wanting hundreds, even
thousands of layers onscreen.

I've been tempted to suggest this many times but I didn't want to spawn another
"code split-up" argument. Some critical methods like, say, moveTo or setSize
might speed up by doing.:

if(is.ns) DynLayer.prototype.moveTo = function A
else DynLayer.prototype.moveTo = function B

I'll try myself in see what happens

Pascal wrote:

> me again :)
>
> I don't think this test is really useable.
> Your current Tcanvas code misses ALOT of things DynLayer takes care of.
>
> DynLayer sets sizes, z-index,clipping,bgimages in initialisation (and also a
> few other style properties.. note that setting a style property is what
> slows everything down)  I once did some optimization tricks to the dynlayer,
> by removing sizes/clipping etc.. this speeds up things BIG TIME, but also
> brakes useability for a large amount of widgets, and is less flexible.
>
> DynLayer has code included for fast child-creation.. even though there are
> no child layers in your test, this code is still called (function calls).
> This could be made faster in dynlayer, but for now is more readable for
> developers.  Do another test with layers containing a large amount child
> layers.. Dynlayer's precreation will probably be faster.
>
> shreded enough? ;)
>
> Pascal Bestebroer (pb...@oi...)
> Software ontwikkelaar
> Oberon Informatiesystemen b.v.
> http://www.oibv.com
>
> > -----Oorspronkelijk bericht-----
> > Van: dyn...@li...
> > [mailto:dyn...@li...]Namens Eytan
> > Heidingsfeld
> > Verzonden: vrijdag 16 februari 2001 13:19
> > Aan: Dynapi-Dev
> > Onderwerp: [Dynapi-Dev] TCanvas vs. DynLayer
> >
> >
> > I'd love to test performance one against the other. The only
> > test I did was
> > create 100 layers and check the times. In IE TCanvas was 200
> > ms faster and
> > in NS it was 1300(canvas) to 10000(dynlayer).
> >
> > I'd love you guys to start tearing my canvas to shreds.
> >
> > Included in the zip are:
> > tcanvas.js
> > browser.js
> >
> > they need to be included in the document(working on adding .include)
> >
> > 8an
> >
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev

[Dynapi-Dev] TimeLine vs Thread

[Michael P. <mp...@ph...>]

I've completed the update of my TimeLine class.  It is quite useful for
sequential code execution.

It is my hope that eventually all animation will be done using a time
line.  This allows for a frame by frame ordering of code rather than a
pause and execute loop.

It is possible to alter the frame rate during execution without the need
to stop and start the code.

I have also altered the .sleep() method.  It is my belief that this
method is actually ment to cause the sequence to sleep for a given # of
secs not just alter the frame rate.  I suggest that this change alse be
made to the thread class.

As always, I've done almost no documentation and am open to all
suggestions / comments / questions. : )

--
Michael Pemberton
mp...@ph...
ICQ: 12107010

RE: [Dynapi-Dev] TCanvas vs. DynLayer

[Eytan H. <ey...@tr...>]

Now the glueing together.
For that reason exactly(setstyle) I added right after in my code:
setHTML
setVisible
setBgColor
setSize
moveTo

Next test will be nested.

Thanx for the shred,
8an

RE: [Dynapi-Dev] TCanvas vs. DynLayer

[Pascal <pb...@oi...>]

me again :)

I don't think this test is really useable.
Your current Tcanvas code misses ALOT of things DynLayer takes care of.

DynLayer sets sizes, z-index,clipping,bgimages in initialisation (and also a
few other style properties.. note that setting a style property is what
slows everything down)  I once did some optimization tricks to the dynlayer,
by removing sizes/clipping etc.. this speeds up things BIG TIME, but also
brakes useability for a large amount of widgets, and is less flexible.

DynLayer has code included for fast child-creation.. even though there are
no child layers in your test, this code is still called (function calls).
This could be made faster in dynlayer, but for now is more readable for
developers.  Do another test with layers containing a large amount child
layers.. Dynlayer's precreation will probably be faster.


shreded enough? ;)

Pascal Bestebroer (pb...@oi...)
Software ontwikkelaar
Oberon Informatiesystemen b.v.
http://www.oibv.com

> -----Oorspronkelijk bericht-----
> Van: dyn...@li...
> [mailto:dyn...@li...]Namens Eytan
> Heidingsfeld
> Verzonden: vrijdag 16 februari 2001 13:19
> Aan: Dynapi-Dev
> Onderwerp: [Dynapi-Dev] TCanvas vs. DynLayer
>
>
> I'd love to test performance one against the other. The only
> test I did was
> create 100 layers and check the times. In IE TCanvas was 200
> ms faster and
> in NS it was 1300(canvas) to 10000(dynlayer).
>
> I'd love you guys to start tearing my canvas to shreds.
>
> Included in the zip are:
> tcanvas.js
> browser.js
>
> they need to be included in the document(working on adding .include)
>
> 8an
>

[Dynapi-Dev] TCanvas vs. DynLayer

[Eytan H. <ey...@tr...>]

I'd love to test performance one against the other. The only test I did was
create 100 layers and check the times. In IE TCanvas was 200 ms faster and
in NS it was 1300(canvas) to 10000(dynlayer).

I'd love you guys to start tearing my canvas to shreds.

Included in the zip are:
tcanvas.js
browser.js

they need to be included in the document(working on adding .include)

8an

Re: [Dynapi-Dev] setHTML and Events

[Jordi - I. - M. <jmi...@or...>]

Closest think I can think of is in the button widget where in NS clicks do not
fire if you click over the text but they do fire when you click anywere else
in the layer. I've got it in my todo list ( I've had to buy another HD to
store the file ). I don't know if both things are related in any way

Eytan Heidingsfeld wrote:

> Sorry for the briefness. Happened to me that after a setHTML to a layer in
> Netscape the click event didn't work. Very strange I wanted to know if it
> was a bug or if there is some kind of precedent?
>
> 8an
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev

RE: [Dynapi-Dev] setHTML and Events

[Eytan H. <ey...@tr...>]

Sorry for the briefness. Happened to me that after a setHTML to a layer in
Netscape the click event didn't work. Very strange I wanted to know if it
was a bug or if there is some kind of precedent?

8an

Re: [Dynapi-Dev] setHTML and Events

[Jordi - I. - M. <jmi...@or...>]

What ? Where ? Settting HTML to a layer causes layer's to loose any
previous event capturing ?

Eytan Heidingsfeld wrote:

> Why is it that when I call setHTML in netscape the mouse events stop
> working?
>
> 8an
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev

[Dynapi-Dev] setHTML and Events

[Eytan H. <ey...@tr...>]

Why is it that when I call setHTML in netscape the mouse events stop
working?

8an

RE: [Dynapi-Dev] Screenshot of the new WebOS API

[Eytan H. <ey...@tr...>]

How many ppl have been working on this. Amazing stuff!!!