> I'm a little confused. A user developer of DynAPI would want to pick and
> choose which modules he'd/she'd want to include. What modules whould
> jsextend include? And wouldn't people just modify to suite thier
> needs? In
> which case, wouldn't it be better as a suggestion opposed to a
> new file part
> of the DynAPI distribution?
The DynAPI is just an API.. this jsextend would provide the functions like
include() that will make it possible to include more then just the DynAPI,
but also extensions, other code, etc.. (thinking bigger picture here)
jsextend would not include modules.. it's one single file, that contains
functions that are needed but not available in javascript (removefromarray
is another example.. it has nothing to do with dynapi code)
So it's not a suggestion it's a replacement for our current loader. The
DynAPI.js file should not be handling all the extra's, just dynamic stuff
(hence the DYN in the name)
> On a slightly related topic <-- snip -->
let's stay on track for once.. this happens to much in discussion that
people start dragging in other topics :)
Pascal Bestebroer
[EMAIL PROTECTED]
http://www.dynamic-core.net
_______________________________________________
Dynapi-Dev mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-dev
