>-> There will be callbacks for array access (also with opaque
references
>so the host can implement these any way they like and MC don't have to
>expose their precious hashing code).
Arrays would be good for passing multiple parameters to and from an
external.
> -> Callbacks that manipulate objects will also use opaque references
and
>there will be special callbacks to manipulate properties and user
>properties and to iterate through objects, properties and a field's
style
>information in a cross-platform manner.
I tend to think that manipulating the structure of an object should be
MetaCard's job. In my external I have the user pass the data of a field
instead of the field itself, because I've seen many SC externals which
break in MetaCard because the external made callbacks to a SC field or
graphic.
> -> About this one I'm not sure: Should we provide a new way to pass
around
>parameters? We will definitely have to stop passing parameters as C
strings
>and instead use long-counted strings to allow passing binary data with
NULL
>characters in it
Good idea.
>but should we also allow data types?
No, this only complicates matters. Strings can be converted to numbers
easily enough. As for raw data the the size of the parameters, should be
passed along with the parameters to the external.
regards,
Tuviah
