There is one major problem with splitting the files and having
different people working on them. The separate versions for each
browser will become inconsistent with each other when people make
changes to one and not the other. People will add "features" to some
versions and not to others. Then, you don't have a cross-browser
library, but a useless waste of files.
By the way has anybody looked at the compresses files that are now
apart of the DynAPI?
--
// Robert Rainwater
On 12/7/2000, 12:13:07 PM EST, SReindl wrote about "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
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
