Menu
▾
▴
dynapi-dev — List related to the current DynAPI Core development
You can subscribe to this list here.
| 2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(75) |
Nov
(252) |
Dec
(418) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(659) |
Feb
(1039) |
Mar
(870) |
Apr
(235) |
May
(329) |
Jun
(251) |
Jul
(123) |
Aug
(119) |
Sep
(67) |
Oct
(194) |
Nov
(535) |
Dec
(133) |
| 2002 |
Jan
(122) |
Feb
(24) |
Mar
(29) |
Apr
(28) |
May
(16) |
Jun
(20) |
Jul
(11) |
Aug
(12) |
Sep
(13) |
Oct
(14) |
Nov
(23) |
Dec
(19) |
| 2003 |
Jan
(28) |
Feb
(170) |
Mar
(288) |
Apr
(211) |
May
(126) |
Jun
(166) |
Jul
(131) |
Aug
(102) |
Sep
(211) |
Oct
(301) |
Nov
(22) |
Dec
(6) |
| 2004 |
Jan
(14) |
Feb
(16) |
Mar
(7) |
Apr
|
May
(8) |
Jun
(25) |
Jul
(21) |
Aug
(2) |
Sep
(7) |
Oct
|
Nov
(2) |
Dec
(1) |
| 2005 |
Jan
(4) |
Feb
(2) |
Mar
(14) |
Apr
(24) |
May
(3) |
Jun
(7) |
Jul
(30) |
Aug
(5) |
Sep
(1) |
Oct
(3) |
Nov
|
Dec
(1) |
| 2006 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
(4) |
Oct
|
Nov
|
Dec
|
|
From: Doug M. <do...@cr...> - 2001-02-17 20:20:12
|
I'd like to see your canvas.. and your test files, the whole she-bang. Later Doug ----- Original Message ----- From: "Eytan Heidingsfeld" <ey...@tr...> To: <dyn...@li...> Sent: Saturday, February 17, 2001 12:17 PM Subject: RE: [Dynapi-Dev] TCanvas vs. DynLayer > For the stress tests in DynLayer or with canvas? > > 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 |
|
From: Eytan H. <ey...@tr...> - 2001-02-17 20:19:05
|
No i'm just saying that ms supports it in ie5 for win16. check the msdn http://msdn.microsoft.com/workshop/author/dhtml/reference/methods/removenode .asp 8an |
|
From: Eytan H. <ey...@tr...> - 2001-02-17 20:16:16
|
For the stress tests in DynLayer or with canvas? 8an |
|
From: Eytan H. <ey...@tr...> - 2001-02-17 20:15:55
|
What I'm telling you is that you don't need all that. My code makes it so much faster with so little optimization (just passing the create responsibility). 8an |
|
From: Doug M. <do...@cr...> - 2001-02-17 20:15:03
|
[sounding quite shocked, and downright confused] Win 16?!?! Are we supporting Win 16? ----- Original Message ----- From: "Eytan Heidingsfeld" <ey...@tr...> To: "Dynapi-Dev" <dyn...@li...> Sent: Saturday, February 17, 2001 11:36 AM Subject: [Dynapi-Dev] remove Node > Why do we only use removeNode in the delete of a layer only on IE5 on win32 > it is supposedly supported unix and max and win16 too? > > 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 |
|
From: Doug M. <do...@cr...> - 2001-02-17 20:13:45
|
please send the file! ----- Original Message ----- From: "Eytan Heidingsfeld" <ey...@tr...> To: <dyn...@li...> Sent: Saturday, February 17, 2001 10:32 AM Subject: RE: [Dynapi-Dev] TCanvas vs. DynLayer > Did a stress test with nested layers created like this (will send file if > you want) > create 5 layers > in each layer create 5 more > repeat. This means that the whole thing creates > 3125 layers > DynAPI version = 59 seconds and change > Canvas version = 28 seconds and change > > this on a PII 700 with 256 RAM imagine the difference on a P1 or even PII? > > 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 |
|
From: Doug M. <do...@cr...> - 2001-02-17 20:12:38
|
How about over-writing the context menu, you can do that right? Use a timer, if the user holds the mouse down for 20 seconds, THEN fire the menu? Just a though (and a loose one at that) ----- Original Message ----- From: "Michael Bürge" <mb...@st...> To: <dyn...@li...> Sent: Saturday, February 17, 2001 9:10 AM Subject: Re: [Dynapi-Dev] mousedown in ns4 /mac > i just found out that this breaks something else. after adding the suggested > line to events.js, normal links ( <a href=...) don't work anymore. > so i'll have to have another look at the problem, hope i (or somebody else) > can find a fix for that soon. > > -- > Michael Buerge > > > From: Michael Buerge <mb...@st...> > > Reply-To: dyn...@li... > > Date: Fri, 16 Feb 2001 15:29:33 +0100 > > To: <dyn...@li...> > > Subject: [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 --- 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 |
|
From: Doug M. <do...@cr...> - 2001-02-17 20:11:27
|
----- Original Message -----=20
From: "Bart Bizon" <ba...@ho...>
To: <dyn...@li...>
Sent: Saturday, February 17, 2001 8:09 AM
Subject: SV: [Dynapi-Dev] TCanvas vs. DynLayer
It does make sense to split up browser specific code... the advantages =
are any...
but that has already been discussed to death... do let's not get into =
that...=20
Well, there are so many optimizations that can be done, so it's hard to =
mention them all at once...
but that's true for almost any large scale project , with a lot of =
people involved... (many cooks) ;)
Basically , there are two types of optimization that can be done:
1. initialization/creation (this is usually not an issue, before you =
start initializing/creating a large amount of instances.)
Such as say, a tree widget with 200+ nodes?
2. run-time, the most important.
Yes and no.. if it take 30 seconds for your site to load, then you are =
likely to lose more than 30-40 % of your visiters.
If, on the other hand, it takes less than 10 seconds, and the user see's =
feedback ("Loading Blah.....") then
It can be hard to loose them.
The problem with optimization is readability. The more optimized the =
code is , the more unreadable it is.
Though we have to remember that we are dealing with interpreted code, so =
any optimization is for the better.
Readability is not an issue with proper commenting and documentation.
2 good points to strive for in both cases:
1. As litte value assignments as possible
Every time you assign anything but a reference, you are in essence =
copying values. This takes time. A lot more time than conditionals for =
example.
This is true for just about any programming language (just confirming =
yer thought.. :-) )
2. Keeping object references to a minumum.
Goin through an object chain(i.e. obj.reference.value) , takes more =
time than simply accessing a variable, so try "caching" as much as =
possible, by storing object chains in temporary variables.=20
ex.) having DynAPI.prototype.whatever all over the place slows =
initalization down( and makes code more verbose =3D bigger in size) ... =
since the parser has to go through first DynAPI object and then the =
prototype object each time you assign a property.=20
>>> var DynProt =3D DynAPI.prototype ; DynProt.whatever=3Dfunction(){ =
etc.... >>> is faster as the parser only has to go through one object =
reference, DynProt.
This might not be such a big issue initialization wise... but this =
example is very applicable for run-time code. Especially for IE... since =
IE is the slower than Netscape at object traversal.. and is worse at GUI =
rendering ( code must stop executing for the GUI to be updated).
I made this point myself, and was shot down (no names).. certain =
functions can easily be made 'global' functions..
fer instance to make setHTML global you add a parameter.. I.E. =
setHTML(myLayer,"myhtml string"); < ------ no prototype chain.. no =
object chain.
---
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
|
|
From: Doug M. <do...@cr...> - 2001-02-17 20:04:49
|
> never seen a C128 upclose, It looked pretty much like a c64, but less 'rounded' more 'angular' > but I dare to say that nothing ever invented was better then the C64... I think the first amiga might challenge that. :-) > of a PC.. even the 16color (hardware limited and palette set) could be > fooled into more then 16 colors. Let's hear it for pallet rotation!!! <g> Doug --- 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 |
|
From: Doug M. <do...@cr...> - 2001-02-17 19:58:49
|
Seriously! Someone on this list said that they 'found a solution' to the mem-leak problem. But that they won't share without more testing. DUDE! this is an opensource project. The whole point of an Opensource project is that you get to have many minds helping you at once.. If you have found a solution SHARE!!!! Maybe someone else will even improve on it. Hell, this isn't about "well, I did this" It's about "WE DID THIS" Shit. Thanks for listening. Doug ----- Original Message ----- From: "Pascal Bestebroer" <pa...@dy...> To: <dyn...@li...> Sent: Saturday, February 17, 2001 4:44 AM Subject: RE: [Dynapi-Dev] TCanvas vs. DynLayer > 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 > > > > > _______________________________________________ > 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 |
|
From: Doug M. <do...@cr...> - 2001-02-17 19:46:54
|
Sounds to me like they put some text in an said text started blocking mouse events (think DynAPI 1 label object) ----- Original Message ----- From: <ni...@pr...> To: <dyn...@li...> Sent: Friday, February 16, 2001 7:46 PM Subject: Re: [Dynapi-Dev] setHTML and Events > 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 > > > > _______________________________________________ > 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 |
|
From: Eytan H. <ey...@tr...> - 2001-02-17 19:35:47
|
Why do we only use removeNode in the delete of a layer only on IE5 on win32 it is supposedly supported unix and max and win16 too? 8an |
|
From: Eytan H. <ey...@tr...> - 2001-02-17 18:58:06
|
Tried with running 3 times in a row. DynAPI - third time 140000 ms and change Canvas - third time 66000 ms and change 8an |
|
From: Eytan H. <ey...@tr...> - 2001-02-17 18:31:25
|
Did a stress test with nested layers created like this (will send file if you want) create 5 layers in each layer create 5 more repeat. This means that the whole thing creates 3125 layers DynAPI version = 59 seconds and change Canvas version = 28 seconds and change this on a PII 700 with 256 RAM imagine the difference on a P1 or even PII? 8an |
|
From: Eytan H. <ey...@tr...> - 2001-02-17 18:19:42
|
Pascal, added all of the set styles and still same time exactly. 8an |
|
From: Pascal B. <pa...@dy...> - 2001-02-17 17:43:45
|
please note that Dan agreed when we created this inheriting, because it's sufficient enough for our DynAPI needs. Also note that he stated they needed to do some more advanced dynamic-loading (seeing as it's trying to be an OS that needs more control over things then a dynapi) so they needed alot more control over components that are being run on the system, something DynAPI doesn't need. Pascal Bestebroer pa...@dy... http://www.dynamic-core.net > -----Oorspronkelijk bericht----- > Van: dyn...@li... > [mailto:dyn...@li...]Namens Eytan Heidingsfeld > Verzonden: zaterdag 17 februari 2001 18:01 > Aan: Dynapi-Dev > Onderwerp: [Dynapi-Dev] Inheriting > > > Just wanted to make sure you took notice that Dan Stienman the > guru decided > to add his own inheriting because how badly js did it's inheriting. > > 8an > > > _______________________________________________ > Dynapi-Dev mailing list > Dyn...@li... > http://lists.sourceforge.net/lists/listinfo/dynapi-dev > |
|
From: Michael Br. <mb...@st...> - 2001-02-17 17:07:35
|
i just found out that this breaks something else. after adding the suggested line to events.js, normal links ( <a href=...) don't work anymore. so i'll have to have another look at the problem, hope i (or somebody else) can find a fix for that soon. -- Michael Buerge > From: Michael Buerge <mb...@st...> > Reply-To: dyn...@li... > Date: Fri, 16 Feb 2001 15:29:33 +0100 > To: <dyn...@li...> > Subject: [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 > |
|
From: Eytan H. <ey...@tr...> - 2001-02-17 17:00:32
|
Just wanted to make sure you took notice that Dan Stienman the guru decided to add his own inheriting because how badly js did it's inheriting. 8an |
|
From: Bart B. <ba...@ho...> - 2001-02-17 16:10:58
|
It does make sense to split up browser specific code... the advantages =
are any...
but that has already been discussed to death... do let's not get into =
that...=20
Well, there are so many optimizations that can be done, so it's hard to =
mention them all at once...
but that's true for almost any large scale project , with a lot of =
people involved... (many cooks) ;)
Basically , there are two types of optimization that can be done:
1. initialization/creation (this is usually not an issue, before you =
start initializing/creating a large amount of instances.)
2. run-time, the most important.
The problem with optimization is readability. The more optimized the =
code is , the more unreadable it is.
Though we have to remember that we are dealing with interpreted code, so =
any optimization is for the better.
2 good points to strive for in both cases:
1. As litte value assignments as possible
Every time you assign anything but a reference, you are in essence =
copying values. This takes time. A lot more time than conditionals for =
example.
2. Keeping object references to a minumum.
Goin through an object chain(i.e. obj.reference.value) , takes more =
time than simply accessing a variable, so try "caching" as much as =
possible, by storing object chains in temporary variables.=20
ex.) having DynAPI.prototype.whatever all over the place slows =
initalization down( and makes code more verbose =3D bigger in size) ... =
since the parser has to go through first DynAPI object and then the =
prototype object each time you assign a property.=20
>>> var DynProt =3D DynAPI.prototype ; DynProt.whatever=3Dfunction(){ =
etc.... >>> is faster as the parser only has to go through one object =
reference, DynProt.
This might not be such a big issue initialization wise... but this =
example is very applicable for run-time code. Especially for IE... since =
IE is the slower than Netscape at object traversal.. and is worse at GUI =
rendering ( code must stop executing for the GUI to be updated).
-----Ursprungligt meddelande-----
Fr=E5n: Pascal Bestebroer <pa...@dy...>
Till: dyn...@li... =
<dyn...@li...>
Datum: den 17 februari 2001 13:44
=C4mne: RE: [Dynapi-Dev] TCanvas vs. DynLayer
>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=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
>> >
>>
>>
>> _______________________________________________
>> 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
>
|
|
From: Nuno F. <nun...@wi...> - 2001-02-17 15:28:44
|
Brilliant! And if the "faqomatic" can produce a dump list of the faq, so you guys can always include it in the release docs, then it's perfect! -----Original Message----- From: dyn...@li... [mailto:dyn...@li...]On Behalf Of Robert Rainwater Sent: sexta-feira, 16 de Fevereiro de 2001 20:01 To: DynAPI Development List 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/ |
|
From: Pascal B. <pa...@dy...> - 2001-02-17 14:52:31
|
man I feel sorry for you.. really do :) I actually still play some C64 games now and then (emulated) never seen a C128 upclose, but I dare to say that nothing ever invented was better then the C64... no pentium can even come close to the horse power squeezed into such a tiny machine, running on less then 1 mhz, yet being able to do all graphic tricks of a PC.. even the 16color (hardware limited and palette set) could be fooled into more then 16 colors. and don't even get me started on its musical powers... oh man, memories :) Pascal Bestebroer pa...@dy... http://www.dynamic-core.net > -----Oorspronkelijk bericht----- > Van: dyn...@li... > [mailto:dyn...@li...]Namens Michael Pemberton > Verzonden: zaterdag 17 februari 2001 15:42 > Aan: dyn...@li... > Onderwerp: Re: [Dynapi-Dev] TCanvas vs. DynLayer ( I have no life : ) ) > > > but what do you do if all you can do is get your hands on a c128 > and are forced > to "go 64"? > > I am quite angry with myself that I am even sending this. I > spent too much time > playing with my old Vic20 / C64 / C128. btw: do you know which > of the 8 colors > was lost when the vic twenty was upgraded to the 16 color C64? > > Pascal Bestebroer wrote: > > > 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 > > > > > > > _______________________________________________ > > 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 > |
|
From: Michael P. <mp...@ph...> - 2001-02-17 14:44:05
|
but what do you do if all you can do is get your hands on a c128 and are forced
to "go 64"?
I am quite angry with myself that I am even sending this. I spent too much time
playing with my old Vic20 / C64 / C128. btw: do you know which of the 8 colors
was lost when the vic twenty was upgraded to the 16 color C64?
Pascal Bestebroer wrote:
> 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
> >
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
--
Michael Pemberton
mp...@ph...
ICQ: 12107010
|
|
From: Michael P. <mp...@ph...> - 2001-02-17 14:12:37
|
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 |
|
From: <no...@so...> - 2001-02-17 14:09:04
|
Bug #131669, was updated on 2001-Feb-09 01:57 Here is a current snapshot of the bug. Project: DynAPI 2 Category: Browser-Specific Issue Status: Closed Resolution: Works For Me Bug Group: None Priority: 5 Submitted by: nobody Assigned to : nobody Summary: CreateLayer problem with Netscape 6 Details: Layer is not defined with netscape 6 Follow-Ups: Date: 2001-Feb-17 06:10 By: dcpascal Comment: I can create layers in NS6 without problems..so doesn't seem to be a valid bug ------------------------------------------------------- Date: 2001-Feb-14 15:09 By: wessto Comment: look at the post by wessto on 2000-02-14. Is this the same? ------------------------------------------------------- Date: 2001-Feb-09 07:44 By: dcpascal Comment: can you give more information? example of your code if possible ------------------------------------------------------- For detailed info, follow this link: http://sourceforge.net/bugs/?func=detailbug&bug_id=131669&group_id=5757 |
|
From: <no...@so...> - 2001-02-17 14:08:21
|
Bug #132422, was updated on 2001-Feb-14 15:08
Here is a current snapshot of the bug.
Project: DynAPI 2
Category: Browser-Specific Issue
Status: Closed
Resolution: Invalid
Bug Group: None
Priority: 5
Submitted by: wessto
Assigned to : nobody
Summary: Layers not showing up in netscape 6
Details: this works in ie and ns4, but layers and content don't show up in
netscape 6. The following is the code I'm using...
##############BEGIN CODE#######################
<html> <head> <title>title</title> <LINK href="style.css" rel="STYLESHEET"
type="text/css"> <script language="Javascript"
src="/javascript/dynapi/src/dynapi.js"></script> <script
language="Javascript" src="/javascript/dynLayerHelper.js"></script> <script
language="Javascript">
DynAPI.setLibraryPath('/javascript/dynapi/src/lib');
DynAPI.include('dynapi.api.browser.js');
DynAPI.include('dynapi.api.dynlayer.js');
DynAPI.include('dynapi.api.dyndocument.js');
var mainColor = '#333333';
var titleColor = '#333333';
var borderColor = '#ffffff';
var navColor = '#330000';
var borderWidth = 1;
var baseX = 5;
var baseY = 5;
var titleWidth = 750;
var titleHeight = 52;
var contentWidth = titleWidth - 200;
var contentHeight = 580;
var dbResult = 'text here';
var hNavHeight = 30;
var vNavWidth = titleWidth - contentWidth;
var vNavHeight = contentHeight - hNavHeight;
var hNavFillerX = contentWidth + baseX;
var vNavX = hNavFillerX;
var contentY = baseY + hNavHeight + titleHeight - borderWidth;
var hNavY = baseY + titleHeight - borderWidth;
var vNavFillerX = vNavX - borderWidth;
var vNavFillerY = contentY + vNavHeight;
DynAPI.onLoad=function() {
//border order = top,right,bottom,left
makeLayerWithBorders('title',baseX,baseY,titleWidth,titleHeight,titleColor,borderWidth,borderColor,true,true,false,true);
makeLayerWithBorders('hNav',baseX,hNavY,contentWidth,hNavHeight,navColor,borderWidth,borderColor,true,false,true,true);
makeLayerWithBorders('hNavFiller',hNavFillerX,hNavY,vNavWidth,hNavHeight,navColor,borderWidth,borderColor,true,true,false,false);
makeLayerWithBorders('vNav',vNavX,contentY,vNavWidth,vNavHeight,navColor,borderWidth,borderColor,false,true,true,false);
makeLayerWithBorders('mainContent',baseX,contentY,contentWidth,contentHeight,mainColor,borderWidth,borderColor,false,true,true,true);
makeLayerWithBorders('lastEdited',vNavFillerX,vNavFillerY,vNavWidth +
borderWidth,contentHeight -
vNavHeight,mainColor,borderWidth,borderColor,false,true,true,false);
content = '<span class=title><b>title</b></span>';
title.setHTML(content); content = '<span class=hnav><a
href="somesite">home</a> | <a href="?page=resume">resume</a> | <a
href="?page=services">services</a> | <a
href="?page=about">about</a></span>';
hNav.setHTML(content);
//PAGE SELECTION
mainContent.setHTML(dbResult);
content = '<span class=last><b>rev:</b>02.14.01 22:58:06</span>';
lastEdited.setHTML(content);
}
</script> </head> <body> <!--- REQUIRED FOR NETSCAPE ---> <SCRIPT
language="JavaScript"> height = contentHeight + hNavHeight + titleHeight;
document.write('<img src="images/pixel.gif" width=1 height=' + height + '
border=0>');
</script> </body> </html>
#############END CODE#################
Follow-Ups:
Date: 2001-Feb-17 06:09
By: dcpascal
Comment:
seems to be a browser bug
NS6 is tripping over the eval() calls in your code. The variables are not
created because NS the parameter is also called NAME... change those lines
to something like this:
eval( 'l'+name + ...... );
eval( "DynAPI.document.addChild(l" + name + ");");
And again, next time make the easiest example code you can, because again
this bug was not in DynAPI, but in your own code which could have been
figured out if you took a few seconds to remove as much code as not needed
to produce the error.. something I have now been doing just to fix your
code (not dynapi code)..
rant is ment for everyone and not personal.
-------------------------------------------------------
Date: 2001-Feb-15 13:41
By: wessto
Comment:
I use dynlayerhelper.js to add borders to my layers. Nothing special is
done. Here is the complete code for dynlayerhelper.js:
#######BEGIN#############
function
makeLayerWithBorders(name,xpos,ypos,width,height,color,borderWidth,borderColor,tBorder,rBorder,bBorder,lBorder)
{
eval( name + " = new DynLayer(null," + xpos + "," + ypos + "," + width +
"," + height + ",'" + color + "');");
eval( "DynAPI.document.addChild(" + name + ");");
if(tBorder) {
eval( name + "_tBorder = new DynLayer(null," + xpos + "," + ypos + "," +
width + "," + borderWidth + ",'" + borderColor + "');");
eval( "DynAPI.document.addChild(" + name + "_tBorder);");
}
if(rBorder) {
var newX = xpos + width - borderWidth;
eval( name + "_rBorder = new DynLayer(null," + newX + "," + ypos + "," +
borderWidth + "," + height + ",'" + borderColor + "');");
eval( "DynAPI.document.addChild(" + name + "_rBorder);");
}
if(bBorder) {
var newY = ypos + height - borderWidth;
eval( name + "_bBorder = new DynLayer(null," + xpos + "," + newY + "," +
width + "," + borderWidth + ",'" + borderColor + "');");
eval( "DynAPI.document.addChild(" + name + "_bBorder);");
}
if(lBorder) {
eval( name + "_lBorder = new DynLayer(null," + xpos + "," + ypos + "," +
borderWidth + "," + height + ",'" + borderColor + "');");
eval( "DynAPI.document.addChild(" + name + "_lBorder);");
}
}
#######END#######3
-------------------------------------------------------
Date: 2001-Feb-15 09:59
By: dcpascal
Comment:
Do you have an easier piece of code (without the extra stuff in your
dynlayerhelper file etc) that also goes wrong.
Code including personal add-ons can be hard to recreate.
-------------------------------------------------------
For detailed info, follow this link:
http://sourceforge.net/bugs/?func=detailbug&bug_id=132422&group_id=5757
|
175 messages has been excluded from this view by a project administrator.
