Re: [Dynapi-Dev] Freeing Memory

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

Amen. However Pascal I don't think anyone pretends to redo the API. We should
blame Raymond ( as usual :) ) because he introduced the 3 in the name and made
it all look scary.

When we're saying DynAPI3 I understand we're meaning DynAPI2 with better and
cleaner code, not a new API.

Pascal wrote:

> Well to get this said in time:
>
> I think that any moves towards a DynAPI3 should be on a seperate sourceforge
> project (or atleast other location).
>
> I have absolutely no interest in doing everything all over again or even
> participating in a venture like that.
>
> The DynAPI2 has been in development for little more then a year  now, and we
> "made" everyone drop the dynapi1 in favour of DynAPI2 saying "dynapi1 is
> discontinued, dynapi2 will support ie55 and ns6 and other new browsers, it's
> better more flexible and you should just use it"
>
> Now you guys are thinking about doing it all over again.. this means you'r
> saying to all the users (and there are ALOT)  sorry people, now you'll have
> to use this unfinished-slightly-not-100%-working version of a crossbrowser
> library  because we're going to redo everything.
>
> Most people here haven't been involved with the full developing of the
> DynAPI, I can think of only 3 persons at this moment that have been
> participating in the development for this long period (and still only about
> 3-5 persons doing all the stuff: documentation, bug fixing, patches,
> administrating, etc).
>
> In one more year, alot of you will have abonded the API3 completely, leaving
> only a few guys on board.. the API will work crossbrowser partially, and not
> fully supporting the latest browsers (by that time something like versions
> 110 of those browsers and DOM20)... Seen it happen already with this code,
> don't want to redo it just to end up with the same thing.
>
> In the beginning we had clean code, it was backwards compatible and was nice
> to look at, but didn't had the powerfull functionality it has now.. There's
> not much wrong with the current API, the only thing is that no body ever
> took the time to go thru the code and optimise it. I for one will keep
> working on THIS version of the API and know it can be cleaned up, and make
> it work on any other future browsers coming our way.
>
> let the flaming begin.
>
> Pascal Bestebroer (pb...@oi...)
> Software ontwikkelaar
> Oberon Informatiesystemen b.v.
> http://www.oibv.com
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev