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

RE: [Dynapi-Dev] TCanvas vs. DynLayer

[Pascal B. <pa...@dy...>]

Note that I'm only splitting browser specific code, not complete functions
into seperate files (something I'm strongly against)
You shouldn't split up source code that is created to make split-up-browsers
to work as one.. doesn't make sense, and will most likely cause problems
when supporting cross-browser code.

What other optimisations are you thinking about?   I've noticed alot of
email from people saying they have done this, or done that.. but they never
show any code, so please people.. if you did some optimising or other
ingenious code show us, and don't be so vague

Pascal Bestebroer
pa...@dy...
http://www.dynamic-core.net

> -----Oorspronkelijk bericht-----
> Van: dyn...@li...
> [mailto:dyn...@li...]Namens Bart Bizon
> Verzonden: zaterdag 17 februari 2001 13:10
> Aan: dyn...@li...
> Onderwerp: SV: [Dynapi-Dev] TCanvas vs. DynLayer
>
>
> Yes... and now we are again getting into the discussion of a
> split browser API.
> What you are proposing is taking a step in that direction..
>  I would take it on step further... and split up the code in
> different files alltogether (to minimize downloaded code and add clarity)
> ... but let's not dwell upon that... ;)
> I have been developing my SuperClass for some time now... and
> recently I have been doing a LOT of optimizing...
> so I'm getting to be very profitient in this area. And there is
> room for tons of optimization in DynAPI.
> But your suggestion is a very good start.
>
> >this is not how it should be done. Alot of methods in DynAPI contain if
> >statements for ie/ns checking.. you can optimize this by removing the IF
> >statements from the runtime loop, simple example of setX/setY:
> >
> >if (is.ns) {
> > DynLayer.prototype._setX=function(){ this.css.left=this.x;
> >this.pageX=this.getPageX() }
> > DynLayer.prototype._setY=function(){ this.css.top=this.y;
> >this.pageY=this.getPageY() }
> >} else {
> > DynLayer.prototype._setX=function(){ this.css.pixelLeft=this.x;
> >this.pageX=this.getPageX() }
> > DynLayer.prototype._setY=function(){ this.css.pixelTop=this.y;
> >this.pageY=this.getPageY() }
> >}
> >
> >
> >Your still assigning methods to the prototype, but at parse time, not run
> >time.. removing the IF statements, and speeding the execution of the code
> >(not by much, but it is an increase in speed)
> >
> >This can be done for multiple methods (setHTML, moveTo, setSizez, etc)
> >
> >
> >
> >
> >
> >Pascal Bestebroer
> >pa...@dy...
> >http://www.dynamic-core.net
> >
> >> -----Oorspronkelijk bericht-----
> >> Van: dyn...@li...
> >> [mailto:dyn...@li...]Namens Bart Bizon
> >> Verzonden: vrijdag 16 februari 2001 23:18
> >> Aan: dyn...@li...
> >> Onderwerp: SV: [Dynapi-Dev] TCanvas vs. DynLayer
> >>
> >>
> >> true ... but by that definition you would expect windows programs
> >> to release memory by default... and the OS should handle it .. right?
> >> Which it doesn't.... it's not just DynAPI pages that swallow
> >> memory, ordinary pages do to...
> >> and so do many windows programs.
> >> (But... this is assuming that windows is actually a good OS...
> >> which it is... NOT)
> >> Taking this into account... you have to work with the conditions
> >> at hand...
> >>
> >> -----Ursprungligt meddelande-----
> >> Från: Pascal Bestebroer <pa...@dy...>
> >> Till: dyn...@li...
> <dyn...@li...>
> >> Datum: den 16 februari 2001 20:15
> >> Ämne: RE: [Dynapi-Dev] TCanvas vs. DynLayer
> >>
> >>
> >> >to be even less helpful here, I truly believe it can't be
> fixed, and that
> >> >it's an browser issue..
> >> >I truly hope I'm wrong, but it seems to me that the javascript
> >> interpreters
> >> >should automatically unload any memory no matter what.
> >> >This is how all (good) environments work) they get space to
> work in, and
> >> >once it's done that single memory block is freed.
> >> >
> >> >Maybe I'm wrong (and I truly hope so) but I won't be searching for a
> >> >solution on this.
> >> >
> >> >Pascal Bestebroer
> >> >pa...@dy...
> >> >http://www.dynamic-core.net
> >> >
> >> >> -----Oorspronkelijk bericht-----
> >> >> Van: dyn...@li...
> >> >> [mailto:dyn...@li...]Namens Michael Ellis
> >> >> Verzonden: vrijdag 16 februari 2001 19:25
> >> >> Aan: 'dyn...@li...'
> >> >> Onderwerp: RE: [Dynapi-Dev] TCanvas vs. DynLayer
> >> >>
> >> >>
> >> >> I agree... this is a huge problem. Pretty much makes the
> >> software unusable
> >> >> unless you have a ton of ram.
> >> >>
> >> >> I currently have a level-3 defect on the memory leak generated by
> >> >> DynAPI for
> >> >> a software product that is supposed to be out the door in a
> >> week. We have
> >> >> not successfully had any impact whatsoever on this issue to date.
> >> >>
> >> >> Anyone had any luck with this? Anyone have any ideas?
> >> >>
> >> >> Mike Ellis
> >> >>
> >> >> -----Original Message-----
> >> >> From: Lasse Lindgård [mailto:la...@li...]
> >> >> Sent: Friday, February 16, 2001 07:00
> >> >> To: dyn...@li...
> >> >> 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
> >> >>
> >> >
> >> >
> >> >_______________________________________________
> >> >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
> >
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>

SV: [Dynapi-Dev] TCanvas vs. DynLayer

[Bart B. <ba...@ho...>]

Yes... and now we are again getting into the discussion of a split =
browser API.
What you are proposing is taking a step in that direction..
 I would take it on step further... and split up the code in different =
files alltogether (to minimize downloaded code and add clarity)
... but let's not dwell upon that... ;)
I have been developing my SuperClass for some time now... and recently I =
have been doing a LOT of optimizing...
so I'm getting to be very profitient in this area. And there is room for =
tons of optimization in DynAPI.
But your suggestion is a very good start.

>this is not how it should be done. Alot of methods in DynAPI contain if
>statements for ie/ns checking.. you can optimize this by removing the =
IF
>statements from the runtime loop, simple example of setX/setY:
>
>if (is.ns) {
> DynLayer.prototype._setX=3Dfunction(){ this.css.left=3Dthis.x;
>this.pageX=3Dthis.getPageX() }
> DynLayer.prototype._setY=3Dfunction(){ this.css.top=3Dthis.y;
>this.pageY=3Dthis.getPageY() }
>} else {
> DynLayer.prototype._setX=3Dfunction(){ this.css.pixelLeft=3Dthis.x;
>this.pageX=3Dthis.getPageX() }
> DynLayer.prototype._setY=3Dfunction(){ this.css.pixelTop=3Dthis.y;
>this.pageY=3Dthis.getPageY() }
>}
>
>
>Your still assigning methods to the prototype, but at parse time, not =
run
>time.. removing the IF statements, and speeding the execution of the =
code
>(not by much, but it is an increase in speed)
>
>This can be done for multiple methods (setHTML, moveTo, setSizez, etc)
>
>
>
>
>
>Pascal Bestebroer
>pa...@dy...
>http://www.dynamic-core.net
>
>> -----Oorspronkelijk bericht-----
>> Van: dyn...@li...
>> [mailto:dyn...@li...]Namens Bart Bizon
>> Verzonden: vrijdag 16 februari 2001 23:18
>> Aan: dyn...@li...
>> Onderwerp: SV: [Dynapi-Dev] TCanvas vs. DynLayer
>>
>>
>> true ... but by that definition you would expect windows programs
>> to release memory by default... and the OS should handle it .. right?
>> Which it doesn't.... it's not just DynAPI pages that swallow
>> memory, ordinary pages do to...
>> and so do many windows programs.
>> (But... this is assuming that windows is actually a good OS...
>> which it is... NOT)
>> Taking this into account... you have to work with the conditions
>> at hand...
>>
>> -----Ursprungligt meddelande-----
>> Fr=E5n: Pascal Bestebroer <pa...@dy...>
>> Till: dyn...@li... =
<dyn...@li...>
>> Datum: den 16 februari 2001 20:15
>> =C4mne: RE: [Dynapi-Dev] TCanvas vs. DynLayer
>>
>>
>> >to be even less helpful here, I truly believe it can't be fixed, and =
that
>> >it's an browser issue..
>> >I truly hope I'm wrong, but it seems to me that the javascript
>> interpreters
>> >should automatically unload any memory no matter what.
>> >This is how all (good) environments work) they get space to work in, =
and
>> >once it's done that single memory block is freed.
>> >
>> >Maybe I'm wrong (and I truly hope so) but I won't be searching for a
>> >solution on this.
>> >
>> >Pascal Bestebroer
>> >pa...@dy...
>> >http://www.dynamic-core.net
>> >
>> >> -----Oorspronkelijk bericht-----
>> >> Van: dyn...@li...
>> >> [mailto:dyn...@li...]Namens Michael =
Ellis
>> >> Verzonden: vrijdag 16 februari 2001 19:25
>> >> Aan: 'dyn...@li...'
>> >> Onderwerp: RE: [Dynapi-Dev] TCanvas vs. DynLayer
>> >>
>> >>
>> >> I agree... this is a huge problem. Pretty much makes the
>> software unusable
>> >> unless you have a ton of ram.
>> >>
>> >> I currently have a level-3 defect on the memory leak generated by
>> >> DynAPI for
>> >> a software product that is supposed to be out the door in a
>> week. We have
>> >> not successfully had any impact whatsoever on this issue to date.
>> >>
>> >> Anyone had any luck with this? Anyone have any ideas?
>> >>
>> >> Mike Ellis
>> >>
>> >> -----Original Message-----
>> >> From: Lasse Lindg=E5rd [mailto:la...@li...]
>> >> Sent: Friday, February 16, 2001 07:00
>> >> To: dyn...@li...
>> >> 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.
>> >>
>> >> ------=3D_NextPart_000_0002_01C09823.65DE2AF0
>> >> Content-Type: text/plain;
>> >> charset=3D"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
>> >>
>> >
>> >
>> >_______________________________________________
>> >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
>

RE: [Dynapi-Dev] TCanvas vs. DynLayer

[Pascal B. <pa...@dy...>]

I'm not saying the OS should take care of it, I'm saying the parser (or
other compiler) should have taken care of inserting memory-freeing.
Borland compilers make sure that when the program is closed the used memory
is freed (pointers, objects, etc..)

This is something the browser should also do, it's creating a workspace
(dom+javascript model) and it should simply destroy everything in its
contents when closing or reloading a new page (i.e.: a new dom + javascript
space)

And not starting an OS discussion here, but there is NO good OS, they all
have flaws and annoying aspects (much like developers :) so work with what
you like. (damn how I want my C64 back)


In reply to your other mail:

"No , this will not speed up things at all...
doing:

Class.prototype.method=function(){ }
 OR
function method(){ }
Class.prototype.method=method
  OR
Class.prototype.method=function method() { }"

this is not how it should be done. Alot of methods in DynAPI contain if
statements for ie/ns checking.. you can optimize this by removing the IF
statements from the runtime loop, simple example of setX/setY:

if (is.ns) {
	DynLayer.prototype._setX=function(){ this.css.left=this.x;
this.pageX=this.getPageX() }
	DynLayer.prototype._setY=function(){ this.css.top=this.y;
this.pageY=this.getPageY() }
} else {
	DynLayer.prototype._setX=function(){ this.css.pixelLeft=this.x;
this.pageX=this.getPageX() }
	DynLayer.prototype._setY=function(){ this.css.pixelTop=this.y;
this.pageY=this.getPageY() }
}


Your still assigning methods to the prototype, but at parse time, not run
time.. removing the IF statements, and speeding the execution of the code
(not by much, but it is an increase in speed)

This can be done for multiple methods (setHTML, moveTo, setSizez, etc)





Pascal Bestebroer
pa...@dy...
http://www.dynamic-core.net

> -----Oorspronkelijk bericht-----
> Van: dyn...@li...
> [mailto:dyn...@li...]Namens Bart Bizon
> Verzonden: vrijdag 16 februari 2001 23:18
> Aan: dyn...@li...
> Onderwerp: SV: [Dynapi-Dev] TCanvas vs. DynLayer
>
>
> true ... but by that definition you would expect windows programs
> to release memory by default... and the OS should handle it .. right?
> Which it doesn't.... it's not just DynAPI pages that swallow
> memory, ordinary pages do to...
> and so do many windows programs.
> (But... this is assuming that windows is actually a good OS...
> which it is... NOT)
> Taking this into account... you have to work with the conditions
> at hand...
>
> -----Ursprungligt meddelande-----
> Från: Pascal Bestebroer <pa...@dy...>
> Till: dyn...@li... <dyn...@li...>
> Datum: den 16 februari 2001 20:15
> Ämne: RE: [Dynapi-Dev] TCanvas vs. DynLayer
>
>
> >to be even less helpful here, I truly believe it can't be fixed, and that
> >it's an browser issue..
> >I truly hope I'm wrong, but it seems to me that the javascript
> interpreters
> >should automatically unload any memory no matter what.
> >This is how all (good) environments work) they get space to work in, and
> >once it's done that single memory block is freed.
> >
> >Maybe I'm wrong (and I truly hope so) but I won't be searching for a
> >solution on this.
> >
> >Pascal Bestebroer
> >pa...@dy...
> >http://www.dynamic-core.net
> >
> >> -----Oorspronkelijk bericht-----
> >> Van: dyn...@li...
> >> [mailto:dyn...@li...]Namens Michael Ellis
> >> Verzonden: vrijdag 16 februari 2001 19:25
> >> Aan: 'dyn...@li...'
> >> Onderwerp: RE: [Dynapi-Dev] TCanvas vs. DynLayer
> >>
> >>
> >> I agree... this is a huge problem. Pretty much makes the
> software unusable
> >> unless you have a ton of ram.
> >>
> >> I currently have a level-3 defect on the memory leak generated by
> >> DynAPI for
> >> a software product that is supposed to be out the door in a
> week. We have
> >> not successfully had any impact whatsoever on this issue to date.
> >>
> >> Anyone had any luck with this? Anyone have any ideas?
> >>
> >> Mike Ellis
> >>
> >> -----Original Message-----
> >> From: Lasse Lindgård [mailto:la...@li...]
> >> Sent: Friday, February 16, 2001 07:00
> >> To: dyn...@li...
> >> 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
> >>
> >
> >
> >_______________________________________________
> >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[2]: [Dynapi-Dev] Interactive FAQ

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

Another idea is that we can make dynapi.sourceforge.net a slashdot
type site, so that we can post articles and allow people to comment
and such.  There are a few php version of slashdot available.  I've
used http://atthat.com in the past and it works pretty good.  I tested
it out on the sourceforge server and it seemed to be working.

Just another idea we can try if anyone is interested.

-- 
// Robert Rainwater

On 2/16/2001, 5:05:01 PM EST, Pascal wrote about "[Dynapi-Dev] Interactive FAQ":

> oh my god.. it's not even my birthday! (30th october people... I said 30th
> october..WRITE IT DOWN!)

> then the only thing I have to worry about is the fact that people should
> actually use it (maybe I can make a faq for it?)

> Pascal Bestebroer
> pa...@dy...
> http://www.dynamic-core.net

>> -----Oorspronkelijk bericht-----
>> Van: dyn...@li...
>> [mailto:dyn...@li...]Namens Robert Rainwater
>> Verzonden: vrijdag 16 februari 2001 21:01
>> Aan: DynAPI Development List
>> Onderwerp: [Dynapi-Dev] Interactive FAQ
>>
>>
>>
>> If anyone is interested enough, I thought about setting up an
>> interactive FAQ at http://dynapi.sourceforge.net.  This would allow
>> users to add there own answers to FAQ questions and update them as
>> needed.  There is already a system built that we can use at
>> http://faqomatic.sourceforge.net.
>>
>> I thought this might be a good idea (and keep Pascal from having to
>> update it all the time). It would probaly help answer a lot of the
>> questions that are asked over and over on the list and let everyone
>> contribute to the project. What do you think?
>>
>> --
>> // 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/

RE: [Dynapi-Dev] Scrollpane and NS6.x???

[Michael E. <Mic...@il...>]

This works when I run my tests in a standalone, local mode, but our app is
JSP. When we refresh, we hit the web server again, so we end up back on
square one. I guess I can refresh the dynLayer after a timeout???

-----Original Message-----
From: Richard Bennett [mailto:ma...@ri...]
Sent: Friday, February 16, 2001 17:10
To: dyn...@li...
Subject: Re: [Dynapi-Dev] Scrollpane and NS6.x???


I'm having the same problem in both NS4 & IE5.5, a scrollpane as child of
another layer, doesn't always show up, after refreshing it's ok, and will
stay visible ok.
??

Richard Bennett

ma...@ri...
www.richardinfo.com
(Everything running on, and ported to the 19/12/2000 snapshot of DynAPI2)
Find the DynAPI faq here:
http://sourceforge.net/docman/display_doc.php?docid=656&group_id=5757
Browse the mailinglist here:
http://www.mail-archive.com/index.php3?hunt=dynapi


----- Original Message -----
From: "Michael Ellis" <Mic...@il...>
To: <dyn...@li...>
Sent: Friday, February 16, 2001 9:04 PM
Subject: [Dynapi-Dev] Scrollpane and NS6.x???


> I have Scrollpane working on the PC/Mac NS 4.7x+ and IE 5.0+ working
great,
> but PC/Mac NS 6.x fails to paint (others work fine, dynlayer, dyndocument,
> events, label...) has anyone looked into scrollpane.js yet? Any
> thoughts/suggestions? We tested using the latest CVS we downloaded at noon
> today.
>
> Mike Ellis
>
> -----Original Message-----
> From: dyn...@li...
> [mailto:dyn...@li...]
> Sent: Friday, February 16, 2001 09:27
> To: dyn...@li...
> Subject: Dynapi-Dev digest, Vol 1 #233 - 12 msgs
>
>
> Send Dynapi-Dev mailing list submissions to
> dyn...@li...
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
> or, via email, send a message with subject or body 'help' to
> dyn...@li...
>
> You can reach the person managing the list at
> dyn...@li...
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Dynapi-Dev digest..."
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
> ____________________________________________________________
> Get your free domain name and domain-based e-mail from
> Namezero.com. New!  Namezero Plus domains now available.
> Find out more at: http://www.namezero.com
>

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

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

The debugger is specifically for debugging WebOS, it was crucial for the development of it. It keeps track of the files being loaded, and makes testing things easy.  The built-in JS debugger in Netscape is just plain awful, so we grab the window.onerror messages and route them to our debugger, and there's also an evaluate field with simply allows you to type in commands and evaluate them in the scope of the webos window so you can test things on the fly.

The library loader is a pretty complex piece of work.  A series of buffers controls when objects get inherited and methods are added - but for this to work we couldn't make use of the easy standard JS prototyping.  So we have our own inheriting and method adding system.  For the Netscape version js files are loaded into layers just like with LoadPanel, and then from there the library loader handles the rest, ensures that all the dependent files are loaded before doing the prototyping.

But trust me, this is not something you'd want for DynAPI.  It took a considerable amount of time to get it working 100% effectively.

Dan


On Fri, Feb 16, 2001 at 08:49:24AM +0100, Pascal wrote:
> 
> Question, that debugger is Javascript based!? (interested for obvious
> reasons)
> 
> 
> Also wondering, I know your ofcourse limited on your work for DynAPI2 and
> sharing info.. but can we find any info somewhere on how dynamic loading is
> done? is it done using the loadpanel ideas? If you can't, or don't want to
> mention this I totally understand.. but just wondering :)  any tech paper
> about it openly available
> 
> 
> Pascal Bestebroer (pb...@oi...)
> Software ontwikkelaar
> Oberon Informatiesystemen b.v.
> http://www.oibv.com
> 
> > -----Oorspronkelijk bericht-----
> > Van: dyn...@li...
> > [mailto:dyn...@li...]Namens Dan Steinman
> > Verzonden: vrijdag 16 februari 2001 12:08
> > Aan: dyn...@li...
> > Onderwerp: [Dynapi-Dev] Screenshot of the new WebOS API
> >
> >
> > A lot of you have probably been wondering what the hell I've
> > been up to.  Obviously I haven't been doing as much work on
> > the DynAPI as I used to, but that doesn't mean I haven't been
> > busy with DHTML.  Most of the original group of
> > "DynDevelopers" are aware I work at WebOS.com, but since
> > there's a lot of new people around these days this may be new
> > information.
> >
> > I've been working on the Netscape version of the next WebOS
> > API - this is a commerical quality DHTML/JavaScript API.  It
> > goes far beyond the capabilities of DynAPI2, offering a
> > complete fully functioning platform for web based
> > applications.  This version is unlike the original MyWebOS
> > product, this has been rebuilt from the ground up in pure JavaScript.
> >
> > We're gearing this toward companies.  It's a commercial
> > product, with a price tag.  I'm not in charge of selling it,
> > but the talk is it'll be around $1000 for a full license.
> >
> > I've posted a screenshot of what the final version will be
> > like.  This was taken in Linux, running Netscape 4.75:
> >
> > http://fury161.dyndns.org/webos/webos-screenshot.jpg
> >
> > Everything you see there is a fully working toolkit.  You got
> > dynamic library and application loading, layout managers, and
> > enough widgets to build just about anything you'd like, and a
> > handy debugger.  All written in JavaScript, crossplatform,
> > works in Netscape 4.5 (Win32/Linux/Mac), IE 4.0, 5.0, 5.5
> > probably IE 6.0, and Mozilla in a future version.
> >
> > There will be a trial version of the API released in a month
> > or so.  You'll be able to download it, play with it, but you
> > can't use it on your site or redistribute it unless you buy
> > it.  The API is open though, you can make applications for
> > WebOS and distribute them as you please.
> >
> > If you've done anything at all in DynAPI2 you'll understand
> > almost immediately how to build apps in WebOS.  Instead of
> > DynLayer, you have webos.ui.Component, instead of DynDocument
> > you have webos.getContentPane(), and the event system works
> > similarly.  The differences lie mainly in the amount of
> > different widgets (although we call them "components" in
> > WebOS), and the manner in which you build applications.
> > DynAPI was built as sort of an add-on to existing pages.
> > WebOS is designed to dynamically load up new apps on the fly.
> >  You insert WebOS into a page, and then load up your
> > applications into WebOS.
> >
> > If any of you are seriously interested in this for your
> > development and looking for something more robust than
> > DynAPI, give me an email (to: fa...@hy... or
> > da...@da...) and I'll forward you to the marketing
> > department and you can likely be on the list of the first
> > people to recieve an evaluation copy.
> >
> > Cheers,
> > Dan
> >
> > BTW - I'm still working on my java-based editor for DynAPI,
> > you'll see a first version of that released pretty soon.
> >
> > _______________________________________________
> > 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] setHTML and Events

[<ni...@pr...>]

how did you make that happen ?
it sounds impossible to me !

ciao
Y 
> 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

Re: [Dynapi-Dev] ViewPort

[<ro...@gm...>]

Am Freitag, 16. Februar 2001 03:00 schrieben Sie:
> Am Freitag, 16. Februar 2001 00:41 schrieben Sie:
> > It will work, just don't expect it to be the most speedy
> > experience. =3D) Even if it does turn out slow for you it still beats
> > having multiple partitions on one machine or having a dozen test
> > boxes cluttering up a room.
> > For instance you don't have to leave your current OS.  You just
> > start it up and it runs on top of your current OS, networking and
> > all.
>
> I think RAM is more important than processor speed - I use it to run
> win95c on my linux-box, an AMD 350 with 256MB and it's OK for
> browser-testing

oops, I forgot the second part:

=2E..but on my laptop (Celeron 500, 64MB) it's unacceptable slow


>
> - and it's also a great tool for making screenshots of bluescreens
> :-))
>
> Roland
>
> > M.
> >
> > -----Original Message-----
> > From: Doug Melvin [mailto:do...@cr...]
> > Sent: Thursday, February 15, 2001 6:44 PM
> > To: dyn...@li...
> > Subject: Re: [Dynapi-Dev] ViewPort
> >
> >
> > does that mean I shouldn't bother with my 128meg and Duron 600mhz?
> >
> > :-)
> >
> > ----- Original Message -----
> > From: "Matthew A. Shirey" <ms...@sh...>
> > To: <dyn...@li...>
> > Sent: Thursday, February 15, 2001 3:33 PM
> > Subject: RE: [Dynapi-Dev] ViewPort
> >
> >
> > Work really well.  We run it on win2000.  You need a good amount of
> > ram, I suggest 256Megs+, as well as a pretty sturdy processor.  I
> > am using a PIII 850 here.  We use it to test all of our web
> > applications on before deployment.  Anyway, definitely worth the
> > bucks.  Don't take my word for it though, download their eval
> > version.
> >
> > M.
> >
> > -----Original Message-----
> > From: Bart Bizon [mailto:ba...@ho...]
> > Sent: Thursday, February 15, 2001 3:00 PM
> > To: dyn...@li...
> > Subject: SV: [Dynapi-Dev] ViewPort
> >
> >
> > I was thinking of using it... does it work well?
> > What is the "backend" OS?
> >
> > -----Ursprungligt meddelande-----
> > Fr=E5n: Matthew A. Shirey <ms...@sh...>
> > Till: dyn...@li...
> > <dyn...@li...>
> > Datum: den 15 februari 2001 20:48
> > =C4mne: RE: [Dynapi-Dev] ViewPort
> >
> >
> > Actually I have a series of Virtual Machines using VMWare.
> > www.vmware.com
> >
> > M.
> >
> > -----Original Message-----
> > From: Doug Melvin [mailto:do...@cr...]
> > Sent: Thursday, February 15, 2001 2:10 PM
> > To: dyn...@li...
> > Subject: Re: [Dynapi-Dev] ViewPort
> >
> >
> > ICK! I'm not too sure about adding a partition for each version of
> > IE..
> >
> > :-)
> >
> > ----- Original Message -----
> > From: "Darin Kadrioski" <dka...@ef...>
> > To: <dyn...@li...>
> > Sent: Thursday, February 15, 2001 10:50 AM
> > Subject: RE: [Dynapi-Dev] ViewPort
> >
> > > You can install a separate one on each partition
> > >
> > > -----Original Message-----
> > > From: Eytan Heidingsfeld [mailto:ey...@tr...]
> > > Sent: Thursday, February 15, 2001 10:41 AM
> > > To: dyn...@li...
> > > Subject: RE: [Dynapi-Dev] ViewPort
> > >
> > >
> > > How did you install them on one machine. I have a different
> > > machine
> >
> > for
> > each
> >
> > > one (at work we have a lab).
> > > 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
> >
> > ---
> > 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
> >
> >
> > _______________________________________________
> > 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
> >
> > _______________________________________________
> > 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
> >
> >
> > _______________________________________________
> > 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

Re: [Dynapi-Dev] Updated Website

[Richard B. <ma...@ri...>]

It's looking good, I can't seem to find an error anywhere ;o)

BTW, do you have a home-page?
If you have, I would imagine it might be a bit like
http://www.scottandrew.com/index.php ??

Cheers,
Richard Bennett

ma...@ri...
www.richardinfo.com
(Everything running on, and ported to the 19/12/2000 snapshot of DynAPI2)
Find the DynAPI faq here:
http://sourceforge.net/docman/display_doc.php?docid=656&group_id=5757
Browse the mailinglist here:
http://www.mail-archive.com/index.php3?hunt=dynapi

----- Original Message -----
From: "Robert Rainwater" <rra...@ya...>
To: "DynAPI Development List" <dyn...@li...>
Sent: Friday, February 16, 2001 2:16 AM
Subject: [Dynapi-Dev] Updated Website


>
> I've updated the website with a few new things.  The mailing lists now
> have links to the archives.  The FAQ is now available under the
> tutorials.  And, there is a new snapshot system.  The snapshot page is
> now built dynamically with a perl script (no longer using a cron job).
>
> The snapshots no longer include the jspacked files or the docs.  This
> will cut down on the snapshot size by a lot.  Until the jspack is
> fixed, I don't see a need to include it in the snapshots.
>
> --
> // 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
> ____________________________________________________________
> Get your free domain name and domain-based e-mail from
> Namezero.com. New!  Namezero Plus domains now available.
> Find out more at: http://www.namezero.com
>

Re: [Dynapi-Dev] Scrollpane and NS6.x???

[Richard B. <ma...@ri...>]

I'm having the same problem in both NS4 & IE5.5, a scrollpane as child of
another layer, doesn't always show up, after refreshing it's ok, and will
stay visible ok.
??

Richard Bennett

ma...@ri...
www.richardinfo.com
(Everything running on, and ported to the 19/12/2000 snapshot of DynAPI2)
Find the DynAPI faq here:
http://sourceforge.net/docman/display_doc.php?docid=656&group_id=5757
Browse the mailinglist here:
http://www.mail-archive.com/index.php3?hunt=dynapi


----- Original Message -----
From: "Michael Ellis" <Mic...@il...>
To: <dyn...@li...>
Sent: Friday, February 16, 2001 9:04 PM
Subject: [Dynapi-Dev] Scrollpane and NS6.x???


> I have Scrollpane working on the PC/Mac NS 4.7x+ and IE 5.0+ working
great,
> but PC/Mac NS 6.x fails to paint (others work fine, dynlayer, dyndocument,
> events, label...) has anyone looked into scrollpane.js yet? Any
> thoughts/suggestions? We tested using the latest CVS we downloaded at noon
> today.
>
> Mike Ellis
>
> -----Original Message-----
> From: dyn...@li...
> [mailto:dyn...@li...]
> Sent: Friday, February 16, 2001 09:27
> To: dyn...@li...
> Subject: Dynapi-Dev digest, Vol 1 #233 - 12 msgs
>
>
> Send Dynapi-Dev mailing list submissions to
> dyn...@li...
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
> or, via email, send a message with subject or body 'help' to
> dyn...@li...
>
> You can reach the person managing the list at
> dyn...@li...
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Dynapi-Dev digest..."
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
> ____________________________________________________________
> Get your free domain name and domain-based e-mail from
> Namezero.com. New!  Namezero Plus domains now available.
> Find out more at: http://www.namezero.com
>

Re: [Dynapi-Dev] TCanvas vs. DynLayer

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

hell.. Win98 uses ram even when it's not doign anything.
Just to test it, I de-fragged my ram leaving 97 megs free
(and no programs running either)
then I whent for my smoke break.
When I came back I had 61 megs free..
I did this over night and found that I hav 0.04 megs free come morning..

Just ranting.
Doug
----- Original Message -----
From: "Bart Bizon" <ba...@ho...>
To: <dyn...@li...>
Sent: Friday, February 16, 2001 2:17 PM
Subject: SV: [Dynapi-Dev] TCanvas vs. DynLayer


true ... but by that definition you would expect windows programs to release
memory by default... and the OS should handle it .. right?
Which it doesn't.... it's not just DynAPI pages that swallow memory,
ordinary pages do to...
and so do many windows programs.
(But... this is assuming that windows is actually a good OS... which it
is... NOT)
Taking this into account... you have to work with the conditions at hand...

-----Ursprungligt meddelande-----
Från: Pascal Bestebroer <pa...@dy...>
Till: dyn...@li... <dyn...@li...>
Datum: den 16 februari 2001 20:15
Ämne: RE: [Dynapi-Dev] TCanvas vs. DynLayer


>to be even less helpful here, I truly believe it can't be fixed, and that
>it's an browser issue..
>I truly hope I'm wrong, but it seems to me that the javascript interpreters
>should automatically unload any memory no matter what.
>This is how all (good) environments work) they get space to work in, and
>once it's done that single memory block is freed.
>
>Maybe I'm wrong (and I truly hope so) but I won't be searching for a
>solution on this.
>
>Pascal Bestebroer
>pa...@dy...
>http://www.dynamic-core.net
>
>> -----Oorspronkelijk bericht-----
>> Van: dyn...@li...
>> [mailto:dyn...@li...]Namens Michael Ellis
>> Verzonden: vrijdag 16 februari 2001 19:25
>> Aan: 'dyn...@li...'
>> Onderwerp: RE: [Dynapi-Dev] TCanvas vs. DynLayer
>>
>>
>> I agree... this is a huge problem. Pretty much makes the software
unusable
>> unless you have a ton of ram.
>>
>> I currently have a level-3 defect on the memory leak generated by
>> DynAPI for
>> a software product that is supposed to be out the door in a week. We have
>> not successfully had any impact whatsoever on this issue to date.
>>
>> Anyone had any luck with this? Anyone have any ideas?
>>
>> Mike Ellis
>>
>> -----Original Message-----
>> From: Lasse Lindgård [mailto:la...@li...]
>> Sent: Friday, February 16, 2001 07:00
>> To: dyn...@li...
>> 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
>>
>
>
>_______________________________________________
>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


---
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

SV: [Dynapi-Dev] TCanvas vs. DynLayer

[Bart B. <ba...@ho...>]

true ... but by that definition you would expect windows programs to =
release memory by default... and the OS should handle it .. right?
Which it doesn't.... it's not just DynAPI pages that swallow memory, =
ordinary pages do to...
and so do many windows programs.=20
(But... this is assuming that windows is actually a good OS... which it =
is... NOT)
Taking this into account... you have to work with the conditions at =
hand...=20

-----Ursprungligt meddelande-----
Fr=E5n: Pascal Bestebroer <pa...@dy...>
Till: dyn...@li... =
<dyn...@li...>
Datum: den 16 februari 2001 20:15
=C4mne: RE: [Dynapi-Dev] TCanvas vs. DynLayer


>to be even less helpful here, I truly believe it can't be fixed, and =
that
>it's an browser issue..
>I truly hope I'm wrong, but it seems to me that the javascript =
interpreters
>should automatically unload any memory no matter what.
>This is how all (good) environments work) they get space to work in, =
and
>once it's done that single memory block is freed.
>
>Maybe I'm wrong (and I truly hope so) but I won't be searching for a
>solution on this.
>
>Pascal Bestebroer
>pa...@dy...
>http://www.dynamic-core.net
>
>> -----Oorspronkelijk bericht-----
>> Van: dyn...@li...
>> [mailto:dyn...@li...]Namens Michael Ellis
>> Verzonden: vrijdag 16 februari 2001 19:25
>> Aan: 'dyn...@li...'
>> Onderwerp: RE: [Dynapi-Dev] TCanvas vs. DynLayer
>>
>>
>> I agree... this is a huge problem. Pretty much makes the software =
unusable
>> unless you have a ton of ram.
>>
>> I currently have a level-3 defect on the memory leak generated by
>> DynAPI for
>> a software product that is supposed to be out the door in a week. We =
have
>> not successfully had any impact whatsoever on this issue to date.
>>
>> Anyone had any luck with this? Anyone have any ideas?
>>
>> Mike Ellis
>>
>> -----Original Message-----
>> From: Lasse Lindg=E5rd [mailto:la...@li...]
>> Sent: Friday, February 16, 2001 07:00
>> To: dyn...@li...
>> 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.
>>
>> ------=3D_NextPart_000_0002_01C09823.65DE2AF0
>> Content-Type: text/plain;
>> charset=3D"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
>>
>
>
>_______________________________________________
>Dynapi-Dev mailing list
>Dyn...@li...
>http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>

SV: [Dynapi-Dev] TCanvas vs. DynLayer

[Bart B. <ba...@ho...>]

No , this will not speed up things at all...
doing:

Class.prototype.method=3Dfunction(){ }
 OR
function method(){ }
Class.prototype.method=3Dmethod
  OR
Class.prototype.method=3Dfunction method() { }

is essentially the same speed wise.
What you are doing is assigning a reference to a function in either =
case.  Whether it has a name or exists previously or not is unimportant. =

It is still a reference.

(oh.. and I tested this just to be sure... did an avarage of about 10000 =
calls =3D=3D no noticable difference)

-----Ursprungligt meddelande-----
Fr=E5n: Jordi - IlMaestro - Ministral <jmi...@or...>
Till: dyn...@li... =
<dyn...@li...>
Datum: den 16 februari 2001 14:23
=C4mne: 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 =3D function A
>else DynLayer.prototype.moveTo =3D 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] Interactive FAQ

[Pascal B. <pa...@dy...>]

oh my god.. it's not even my birthday! (30th october people... I said 30th
october..WRITE IT DOWN!)

then the only thing I have to worry about is the fact that people should
actually use it (maybe I can make a faq for it?)

Pascal Bestebroer
pa...@dy...
http://www.dynamic-core.net

> -----Oorspronkelijk bericht-----
> Van: dyn...@li...
> [mailto:dyn...@li...]Namens Robert Rainwater
> Verzonden: vrijdag 16 februari 2001 21:01
> Aan: DynAPI Development List
> Onderwerp: [Dynapi-Dev] Interactive FAQ
>
>
>
> If anyone is interested enough, I thought about setting up an
> interactive FAQ at http://dynapi.sourceforge.net.  This would allow
> users to add there own answers to FAQ questions and update them as
> needed.  There is already a system built that we can use at
> http://faqomatic.sourceforge.net.
>
> I thought this might be a good idea (and keep Pascal from having to
> update it all the time). It would probaly help answer a lot of the
> questions that are asked over and over on the list and let everyone
> contribute to the project. What do you think?
>
> --
> // 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] Scrollpane and NS6.x???

[Michael E. <Mic...@il...>]

I have Scrollpane working on the PC/Mac NS 4.7x+ and IE 5.0+ working great,
but PC/Mac NS 6.x fails to paint (others work fine, dynlayer, dyndocument,
events, label...) has anyone looked into scrollpane.js yet? Any
thoughts/suggestions? We tested using the latest CVS we downloaded at noon
today.

Mike Ellis

-----Original Message-----
From: dyn...@li...
[mailto:dyn...@li...]
Sent: Friday, February 16, 2001 09:27
To: dyn...@li...
Subject: Dynapi-Dev digest, Vol 1 #233 - 12 msgs


Send Dynapi-Dev mailing list submissions to
	dyn...@li...

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.sourceforge.net/lists/listinfo/dynapi-dev
or, via email, send a message with subject or body 'help' to
	dyn...@li...

You can reach the person managing the list at
	dyn...@li...

When replying, please edit your Subject line so it is more specific
than "Re: Contents of Dynapi-Dev digest..."

Re: [Dynapi-Dev] Interactive FAQ

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

I second that notion.
I would be willing to go through my archive of -dev and -help messages
(every one since I joined the lists)
And update the FAQ..

Doug
----- Original Message ----- 
From: "Robert Rainwater" <rra...@ya...>
To: "DynAPI Development List" <dyn...@li...>
Sent: Friday, February 16, 2001 12:00 PM
Subject: [Dynapi-Dev] Interactive FAQ


> 
> If anyone is interested enough, I thought about setting up an
> interactive FAQ at http://dynapi.sourceforge.net.  This would allow
> users to add there own answers to FAQ questions and update them as
> needed.  There is already a system built that we can use at
> http://faqomatic.sourceforge.net.
> 
> I thought this might be a good idea (and keep Pascal from having to
> update it all the time). It would probaly help answer a lot of the
> questions that are asked over and over on the list and let everyone
> contribute to the project. What do you think?
> 
> -- 
> // 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


---
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

[Dynapi-Dev] Interactive FAQ

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

If anyone is interested enough, I thought about setting up an
interactive FAQ at http://dynapi.sourceforge.net.  This would allow
users to add there own answers to FAQ questions and update them as
needed.  There is already a system built that we can use at
http://faqomatic.sourceforge.net.

I thought this might be a good idea (and keep Pascal from having to
update it all the time). It would probaly help answer a lot of the
questions that are asked over and over on the list and let everyone
contribute to the project. What do you think?

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

RE: [Dynapi-Dev] TCanvas vs. DynLayer

[Pascal B. <pa...@dy...>]

to be even less helpful here, I truly believe it can't be fixed, and that
it's an browser issue..
I truly hope I'm wrong, but it seems to me that the javascript interpreters
should automatically unload any memory no matter what.
This is how all (good) environments work) they get space to work in, and
once it's done that single memory block is freed.

Maybe I'm wrong (and I truly hope so) but I won't be searching for a
solution on this.

Pascal Bestebroer
pa...@dy...
http://www.dynamic-core.net

> -----Oorspronkelijk bericht-----
> Van: dyn...@li...
> [mailto:dyn...@li...]Namens Michael Ellis
> Verzonden: vrijdag 16 februari 2001 19:25
> Aan: 'dyn...@li...'
> Onderwerp: RE: [Dynapi-Dev] TCanvas vs. DynLayer
>
>
> I agree... this is a huge problem. Pretty much makes the software unusable
> unless you have a ton of ram.
>
> I currently have a level-3 defect on the memory leak generated by
> DynAPI for
> a software product that is supposed to be out the door in a week. We have
> not successfully had any impact whatsoever on this issue to date.
>
> Anyone had any luck with this? Anyone have any ideas?
>
> Mike Ellis
>
> -----Original Message-----
> From: Lasse Lindgård [mailto:la...@li...]
> Sent: Friday, February 16, 2001 07:00
> To: dyn...@li...
> 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
>

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

[Pascal B. <pa...@dy...>]

it's in cvs

Pascal Bestebroer
pa...@dy...
http://www.dynamic-core.net 

> -----Oorspronkelijk bericht-----
> Van: dyn...@li...
> [mailto:dyn...@li...]Namens Michael Ellis
> Verzonden: vrijdag 16 februari 2001 19:33
> Aan: 'dyn...@li...'
> Onderwerp: RE: [Dynapi-Dev] mousedown in ns4 /mac
> 
> 
> I have a test team coming in Sunday/Monday for one of our projects... if
> it's in the CVS by then I'll include it in our tests.
> 
> Mike Ellis
> 
> -----Original Message-----
> From: Pascal [mailto:pb...@oi...]
> Sent: Friday, February 16, 2001 07:33
> To: dyn...@li...
> Subject: RE: [Dynapi-Dev] mousedown in ns4 /mac
> 
> 
> 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 mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
> 

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

[Michael E. <Mic...@il...>]

I have a test team coming in Sunday/Monday for one of our projects... if
it's in the CVS by then I'll include it in our tests.

Mike Ellis

-----Original Message-----
From: Pascal [mailto:pb...@oi...]
Sent: Friday, February 16, 2001 07:33
To: dyn...@li...
Subject: RE: [Dynapi-Dev] mousedown in ns4 /mac


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
> 

RE: [Dynapi-Dev] TCanvas vs. DynLayer

[Michael E. <Mic...@il...>]

I agree... this is a huge problem. Pretty much makes the software =
unusable
unless you have a ton of ram.

I currently have a level-3 defect on the memory leak generated by =
DynAPI for
a software product that is supposed to be out the door in a week. We =
have
not successfully had any impact whatsoever on this issue to date.

Anyone had any luck with this? Anyone have any ideas?

Mike Ellis

-----Original Message-----
From: Lasse Lindg=E5rd [mailto:la...@li...]
Sent: Friday, February 16, 2001 07:00
To: dyn...@li...
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


-- __--__--=20

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.

------=3D_NextPart_000_0002_01C09823.65DE2AF0
Content-Type: text/plain;
	charset=3D"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

[Pascal B. <pa...@dy...>]

yes, WE need to get this thing fixed..



Pascal Bestebroer
pa...@dy...
http://www.dynamic-core.net

> -----Oorspronkelijk bericht-----
> Van: dyn...@li...
> [mailto:dyn...@li...]Namens Lasse Lindgård
> Verzonden: vrijdag 16 februari 2001 15:00
> Aan: dyn...@li...
> Onderwerp: 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
>

RE: [Dynapi-Dev] DynAPI new event

[Pascal B. <pa...@dy...>]

this would also be the way if would (not saying it will) be included: in a
seperate file, because it's not crossbrowser available.

Pascal Bestebroer
pa...@dy...
http://www.dynamic-core.net

> -----Oorspronkelijk bericht-----
> Van: dyn...@li...
> [mailto:dyn...@li...]Namens Doug Melvin
> Verzonden: vrijdag 16 februari 2001 20:24
> Aan: dyn...@li...
> Onderwerp: Re: [Dynapi-Dev] DynAPI new event
>
>
> 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
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>

RE: [Dynapi-Dev] new DynDocument

[Pascal B. <pa...@dy...>]

read the tutorial (part 5 or 6) which shows you how to do frame handling

Pascal Bestebroer
pa...@dy...
http://www.dynamic-core.net 

> -----Oorspronkelijk bericht-----
> Van: dyn...@li...
> [mailto:dyn...@li...]Namens Michael Pemberton
> Verzonden: vrijdag 16 februari 2001 16:43
> Aan: dyn...@li...
> Onderwerp: Re: [Dynapi-Dev] new DynDocument
> 
> 
> 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
> 
> 
> 
> 
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
> 

[Dynapi-Dev] (no subject)

[àÒÉÊ óÉÌØ×ÅÓÔÒÏ× <yur...@ma...>]

May be, will be useful to allow plugins starts before DynAPI.onLoad() procedure.
E.g. I wrote a tooltip widget with one tooltip DynLayer for all tooltips. That's why I need to create this DynLayer after DynAPI and my ToolTip module are initialised, but before running user code.

To do this, I offer add some code to DynAPI.js:

for (var i=0;i<DynAPI.plugins.length; i++) {
if (DynAPI.plugins[i].onBeforeLoad) DynAPI.plugins[i].onBeforeLoad();
}

directly before DynAPI.onLoad() call 
                                           Yurij Silvestrov