Re: [Re: [Dynapi-Dev] DynAPI Makefile/code compression almost complete]

[Doug M. <do...@cr...>]

I second the humble opinions stated in this preceeding message..
:-)
----- Original Message -----
From: "Cameron Hart" <ca...@bi...>
To: <dyn...@li...>
Sent: Wednesday, December 06, 2000 4:56 AM
Subject: RE: [Re: [Dynapi-Dev] DynAPI Makefile/code compression almost
complete]


> > What I meant (can't say about Cameron), was that it would be nice
> > to have all of the functionality of the API without even worrying if it
is
> > cross browser compatible.
> <snip>
> > If I could _only_ include IE code when I
> > knew it was the standard, then I could speed things up some.... maybe
even
> a lot.
> > maybe I'm dreaming
>
> It would be smaller and faster in all cases because the client would only
> load and run code specific to
> their browser. for example, if (is.ie) ... would only get executed once
when
> the client needed to select the ie specific version of the API to load at
> run time.
>
> That's pretty much the rational behind my suggestion. I'd seen a bit of
> discussion on the list about splitting the API source into different .js
> files for different browsers, the right one being imported when the user
> visits the page. IMHO splitting the API into browser specific .js files
> sounds like a bad idea, keeping the source together and letting a Makefile
> split it would be safer. Of course none of the developers have said they
> were going to split the API in this fashion. I imagine that doing this
would
> be a hell of a lot of work, and you probably all have more important
things
> to do :-)
>
> However if it ever did happen, I think a Makefile solution with #define
and
> #ifdef style macros would be a good way of acheiving this.
>
>