Re: [Dynapi-Dev] DynAPI build, Splitting files

[Dan S. <dy...@fu...>]

I would much sooner do Pascals earlier suggestion of creating different methods and adding them based on the browser:

if (is.ns4) DynLayer.prototype.moveTo = DynLayer_moveToNS4;
if (is.ie4) ...
function DynLayer_moveToNS4() {}

But keep all the code in the same file.  After compressing the DynAPI the difference in file size is almost a non-issue (like 1 or 2Kb difference).  It's not out of the question to have a script that splits the files for build releases though, but it by no means has to be done right away.

Dan

On Thu, Dec 07, 2000 at 07:09:10PM +0100, Pascal Bestebroer wrote:
> An API is a middle-layer between the code and the "environment"  seeing as
> you want to have cross-browser code it sounds better to see one single api
> file that takes care of all browsers.. not having seperate files for every
> browser (that would create a DHTML library, not an API.. simple solution
> change the name to DynLib :)
> 
> Developing in seperate files for seperate browsers WILL create seperate
> things, even though there is talk about setting "rules" for the development,
> we have to face it that streaming this whole project is not something any of
> us is good at.. so sticking to the development rules (even when you could do
> cool things like using behaviours in IE5 for filter effects and stuff) will
> be, in my opinion, impossible to maintain.  Almost the same as asking
> Netscape and Microsoft to stick to the W3C standard.. (and then making sure
> that the W3C doesn't change everything every year :-)
> 
> Someone debugging NN code should just skip the part that says  if (is.ie) ..
> that's not a hard thing to do.
> 
> Also I don't see where you could make the speed advantages? the slowness of
> it all is within the browsers.. try changing a single stylesheet property,
> in IE it looks like it's rerendering everything on screen and I believe
> that's the main problem, so how can you increase speed when splitting things
> up?
> 
> "I mean, I want to develop mainly for IE and am not interested in the nn
> specifics at all. I am satisfied when it works."
> 
> Then why use a cross-browser API (or library for that matter)?
> 
> 
> Pascal Bestebroer
> pa...@dy...
> http://www.dynamic-core.net
> 
> > -----Oorspronkelijk bericht-----
> > Van: dyn...@li...
> > [mailto:dyn...@li...]Namens SReindl
> > Verzonden: donderdag 7 december 2000 18:13
> > Aan: dyn...@li...
> > Onderwerp: AW: [Dynapi-Dev] DynAPI build, Splitting files
> >
> >
> > Can someone pls explain me the mneaning of this whole discussion?
> > An API is a set of uniquely defined functions to perform a given
> > task, isn't
> > it?
> > What do the widgets have to do with the API?
> > Why should it be so difficult to develop the API in separate files?
> > The discussion would be which function of the API should be added
> > / removed
> > / corrected / ...
> > The rest will be done by the respective browser gurus.
> > The charme of the split file version is that a nn specialist
> > doesn't have to
> > analyze a bulk of ie code in order to do his task.
> > The increase in speed an code transparency should overweigh the
> > difficulties
> > of a split version by far.
> > If a solution fullfills the defined function, who cares about the details?
> > I mean, I want to develop mainly for IE and am not interested in the nn
> > specifics at all. I am satisfied when it works.
> >
> > Stephan
> >
> >
> >
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
> >
> 
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev