Re: [Dynapi-Dev] Next Generation

[Raymond S. <dst...@or...>]

Carefull if your using the "sample stats" from there.  They date back to
1999 and reflect an older reality.  Most recent browser stats I have found
are at www.thecounter.com.  From October 2000.

----- Original Message -----
From: "Michael Ellis" <Mic...@il...>
To: <dyn...@li...>
Sent: Monday, January 29, 2001 2:53 PM
Subject: RE: [Dynapi-Dev] Next Generation


> Amen brother!
>
> No argument here... Although we can be educated to, we cannot expect nor
> demand which platform/browser our end-users choose. If our software is to
be
> taken seriously, and serve a broad community we must be reasonable about
> which platforms/browsers we support. If you think I'm full of it, check
the
> browser/platform statistics at www.statmarket.com (don't rely on
statistics
> gathered by developer forums, they attract developers like us and are
> typically not representative of our products end-users).
>
> Mike Ellis
>
> -----Original Message-----
> From: .:: OCB ::. [mailto:oc...@ho...]
> Sent: Monday, January 29, 2001 10:15
> To: dyn...@li...
> Subject: Re: [Dynapi-Dev] Next Generation
>
>
> Next generation ???
>
> Would it not be a good idea to get the DynApi2 working in all browsers
> (basic methods, moveTo, event handlers etc; not wigits, IMO they take a
> backseat to basic functionality) before even discussing another generation
> of the API.
>
> I haven't contributed anything in months (which is beyond my control) so
> feel quite apprehensive about posting this but again, IMO, it makes common
> sense to get the basic's of this project crossbrowser (NN6 included) and
bug
>
> free before launching into another generation of the API.
>
> Flame away !!!!
>
>
> >From: "Jared Nuzzolillo" <ja...@aa...>
> >Reply-To: dyn...@li...
> >To: <dyn...@li...>
> >Subject: [Dynapi-Dev] Next Generation
> >Date: Mon, 29 Jan 2001 11:46:41 -0500
> >
> >I have a feeling that certain people are wanting to implement class-like
> >inheritance because it is more familiar/comfortable to them.
> >
> >I strongly agree with Pascal. Prototype-based inheritance works
> >beautifully,
> >and is native to javascript, so why would we want to enforce a different
> >type of inheritance to use the API? Most dynapi users will at least be
> >familiar with javascript, and may be expecting Prototype-like behavior.
> >
> >It's kind of like creating a number class instead of using built in
number
> >objects and primitive types. It's pointeless.
> >
> >As far as the class/prototype argument as to what Netscape says, the
first
> >line of this article:
> >
>
>http://developer.netscape.com/docs/manuals/communicator/jsobj/contents.htm
> >
> >reads as follows:
> >
> >"JavaScript is an object-oriented language based on prototypes, rather
> >than,
> >as is common, being class-based."
> >
> >-jaredn
> >
> >
> >
> >
> >_______________________________________________
> >Dynapi-Dev mailing list
> >Dyn...@li...
> >http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>
> _________________________________________________________________________
> Get Your Private, Free E-mail from MSN Hotmail at http://www.hotmail.com.
>
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/lists/listinfo/dynapi-dev
>