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
[EMAIL PROTECTED]
http://www.dynamic-core.net
> -----Oorspronkelijk bericht-----
> Van: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]Namens Michael Pemberton
> Verzonden: zaterdag 17 februari 2001 15:42
> Aan: [EMAIL PROTECTED]
> 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
> > [EMAIL PROTECTED]
> > http://www.dynamic-core.net
> >
> > > -----Oorspronkelijk bericht-----
> > > Van: [EMAIL PROTECTED]
> > > [mailto:[EMAIL PROTECTED]]Namens Bart Bizon
> > > Verzonden: vrijdag 16 februari 2001 23:18
> > > Aan: [EMAIL PROTECTED]
> > > 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 <[EMAIL PROTECTED]>
> > > Till: [EMAIL PROTECTED]
> <[EMAIL PROTECTED]>
> > > 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
> > > >[EMAIL PROTECTED]
> > > >http://www.dynamic-core.net
> > > >
> > > >> -----Oorspronkelijk bericht-----
> > > >> Van: [EMAIL PROTECTED]
> > > >> [mailto:[EMAIL PROTECTED]]Namens Michael Ellis
> > > >> Verzonden: vrijdag 16 februari 2001 19:25
> > > >> Aan: '[EMAIL PROTECTED]'
> > > >> 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:[EMAIL PROTECTED]]
> > > >> Sent: Friday, February 16, 2001 07:00
> > > >> To: [EMAIL PROTECTED]
> > > >> 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" <[EMAIL PROTECTED]>
> > > >> To: "Dynapi-Dev" <[EMAIL PROTECTED]>
> > > >> Date: Fri, 16 Feb 2001 14:18:56 +0200
> > > >> Subject: [Dynapi-Dev] TCanvas vs. DynLayer
> > > >> Reply-To: [EMAIL PROTECTED]
> > > >>
> > > >> 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
> > > >> [EMAIL PROTECTED]
> > > >> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
> > > >>
> > > >
> > > >
> > > >_______________________________________________
> > > >Dynapi-Dev mailing list
> > > >[EMAIL PROTECTED]
> > > >http://lists.sourceforge.net/lists/listinfo/dynapi-dev
> > > >
> > >
> > >
> > > _______________________________________________
> > > Dynapi-Dev mailing list
> > > [EMAIL PROTECTED]
> > > http://lists.sourceforge.net/lists/listinfo/dynapi-dev
> > >
> >
> > _______________________________________________
> > Dynapi-Dev mailing list
> > [EMAIL PROTECTED]
> > http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>
> --
> Michael Pemberton
> [EMAIL PROTECTED]
> ICQ: 12107010
>
>
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
