Hmm, what does everybody think about just extending the core JavaScript
language so that it is ECMA compliant vs. creating a set of new objects? The
code I provided mods the array object so that it complies. Either way, the
code ends up on the client, so wouldn't make further sense to keep it
organ
How about creating a new set of function called
functions.array.js? This way we could include the
missing array functions and add some customized ones.
for exmaple:
dynapi.library.include('dynapi.functions.Array');
var ar = dynapi.functions.popArray(array);
var ar = dynapi.functions.spliceArray
How about porting these to DynAPI 3.0?
--
Raymond Irving
--- Stephen Carroll <[EMAIL PROTECTED]> wrote:
> OK, here it is, my old DynAPI stuff. It was built
> on 2.5 and I haven't
> touched it since. I held on to it for too long and
> shouldn't kept it from
> all of you! There are examples in
--- Stephen Carroll <[EMAIL PROTECTED]> wrote:
> Is there a chance that we can correct for other
> cross platform issues?
Sure. If you have any such suggestions we can include
it as library in the API.
> Perhaps this is beyond the scope of this realm, but
> in my version of dynapi
> 2.5, I've ad
See Below:
--- Stephen Carroll <[EMAIL PROTECTED]> wrote:
> OK, here it is, my old DynAPI stuff. It was built
> on 2.5 and I haven't
> touched it since. I held on to it for too long and
> shouldn't kept it from
> all of you! There are examples in the examples
> folder, some of which are
> qui
