RE: [Dynapi-Dev] Splitting the API?

[Cameron H. <ca...@bi...>]

I posted a suggestion to Dan's message about using a Makefile system for
building a final version of the code, I thought it would be worth suggesting
it to this thread of the discussion.

I think it would be a good idea to have a C style #define in the src
javascript to allow building final versions for different browsers. I think
the advantage of doing this is the cross-browser API remains in one set of
source, and users people can then build either seperate versions for each
browser, or build them all into one library. From a development point of
view, to me it makes more sense to keep all the code in a canonical form,
rather than split for every major browser/platform that comes into
existence.

Cam.

> -----Original Message-----
> From: dyn...@li...
> [mailto:dyn...@li...]On Behalf Of Eytan
> Heidingsfeld
> Sent: 05 December 2000 09:24
> To: dyn...@li...
> Subject: Re: [Dynapi-Dev] Splitting the API?
>
>
> Although I am not so sure why thing would run so much better with the API
> split I also have 2c. Basically everything that is browser based are the
> actual low-level components (DynLayer, events....) why don't we
> split those
> components in to one for each version. Then when a higher level
> component (a
> decendent) is created in the constructor you add the following code
> if (browser == IE){inherit from IEDynLayer;}
> if (browser == NS){inherit from NSDynLayer;}
> ..
> ..
> ..
> You get the picture. Then although it might be a hassle to orginize the
> low-level comps the higher level one will be relitivly easy.
>
> 8an
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev