passing vectors,maps from javascript to c++ shared library

[athilka001]

• Is it possible to pass vectors or maps from javascript to c++ shared library?
• I went through the Extendscript Toolkit SDK which contains sample programs which shows how to pass data from c++ and javascript
• I am able to pass basic data types such as integer and character etc to c++ shared library through the structure called TaggedData
• Iam not able to send vector or maps to c++ shared library
• If i alter the TaggedData structure(datas that are communicated between javascript and c++) then the code will fail
• Is there any possible way to send vector and maps to c++ shared library?

[Bruce Bullis · Accepted solution]

I know of no such method.

As you point out, 'flat' basic data types work fine. Vectors and maps are in-memory structures, preventing them from being easily passed across the JavaScript <--> C++ boundary.

What is it you're trying to create?

[athilka001]

Is it possible to change the taggedData structure in the samples provided in the ExtendScript toolkit SDK?

[Bruce Bullis]

I doubt it; JavaScript doesn't have any concept like a C 'union'. Also, notice that I mentioned 'flat' data structures? The 'string' and 'hObject' members of that union variable point outside the actual tagged data structure, to external memory. That's 'un-flat', and will never successfully get passed across a C / ExtendScript boundary.

Still, PPro's ExtendScript API allows for full control over the XMP associated with any given media.

So, again; what is it you're trying to create?

[athilka001]

I'am creating an extension for  PPro and some major operations are done in c++,so i need to pass vectors and maps from javascript to c++

Example

var cars=["bmw","benz"];

i need to pass cars object to c++ shared library, but TaggedData structure does'nt support this, so i was wondering if there is some other way i can pass this cars object

[Bruce Bullis]

Let's leave aside the implementation details for a moment...

Could you provide an overview of the workflow(s) you'd like to support, from the user's perspective? That will help me give better guidance. [write me at b b b at adobe dot com, if you'd rather not discuss those workflows in public.]