Hi,
The next drop of playmaker will offer some critical improvement in Actions properties GUI which will give ArrayMaker a new facelift: basically, the actions will come down into a bear minimum amount of visible properties, and it will be a lot less scary and messy to understand, so expect a real progress on that front for a more comfortable and effective use of ArrayMaker actions.
As for built in support for array, I think too that the amount of work would be colossal and would likely imply a complete rewrite of most of the variable interfaces and create so many problems down the road, just by thinking of it... my head is spinning. I think the great thing about arrayMaker is that the data is encapsulated into ArrayMaker proxies like Kiriri explained which makes it easier to manage because it's completly open to Unity Editor GUI which means raw power and dedicated interface without compromising any PlayMaker features. It also means direct access by other standard behaviors and scripts, so it's very verstalie and I think inline with how Unity intend developers to use gameobject's components.
If arrays where implemented from scratch, then it would be a different story I suppose, but if you look at Unity default management of arrays in the inspector... it's very poor, and I actually think that ArrayMaker is very useful even outside PlayMaker environment. When you start dealing with arrays and lists in general, you open a very broad range of needs that can only be answered with a generic approach, which means a lot more work for the developer to implement an actual feature or function using arrays.
As for an easier way to include ArrayMaker in PlayMaker, I am planning on the following for next year (hopefully): I want to hit the asset store with a general data manager for PlayMaker, with the following trick: actions and updates would be made online ( as well as regular updates on the asset store of course), but the good thing is that I think it would be a good starting point to offer an stable and reliable way of managing data within PlayMaker projects as well as allowing the developer to pick what she/he wants from this system and just the specific actions would be downloaded, with notifications of updates, and automatic synchronisation with the project. In effect this would also be something to host all the custom actions eventually, where when you search for an action, it would also look in a database online and give you a choice of actions that you might not yet have on your project, and it would download it directly, ready for you to use it. This would include all the work I did so far on ArrayMaker, XmlMaker, CSV to XML, DataMaker and ParseMaker and few other real cool goodies that are cooking but not yet yet shared with you yet.
bye,
Jean