Re: [Dynapi-Dev] Separating library packages from dynapi.js (file attached)

[Raymond I. <xw...@ya...>]

--- Dan Willemsen <da...@wi...> wrote:
> On Wed, 2003-04-16 at 08:50, Raymond Irving wrote:
> > --- Dan Willemsen <da...@wi...> wrote:
> > > On Tue, 2003-04-15 at 22:59, Raymond Irving
> wrote:
> > > > It also makes upgrading dynapi a lot more
> easier.
> > > How? Wouldn't the user still have to update the
> new
> > > packages.js file? Or
> > > even, between upgrades, a change in one of the
> > > widgets, or an additional
> > > one, all these examples would need a new
> packages.js
> > > i would think.
> > 
> > With this method the user now controls the
> packages
> > separately from the dynapi.js file. This will be
> very
> > useful in production environments were customized
> > packages are needed. The user can now freely
> update
> > the dynapi.js file without having to worry about
> > packages been overwritten.   
> Except they would still have to worry about the
> packages.js file being
> overwritten, right?

Yes, but even if they do, it's easier for them to just
simply restore their packages.js and not worry about
any code changes, as oppose to them restoring or
modifying the dynapi.js, which might have some
critical changes.

Besides that it makes the dynapi.js looks smaller :)

Agree? Should we implement this package feature? Or is
it six-of-one and half-dozen of the other?

--
Raymond Irving


> -- 
> Dan Willemsen <da...@wi...>
> 


__________________________________________________
Do you Yahoo!?
The New Yahoo! Search - Faster. Easier. Bingo
http://search.yahoo.com