Project Files in JSON format

[Rodney]

Just as a general curiousity, here's what an empty Project file looks like in JSON format:

 

{

"PROJECT": {

"POSTEFFECTS": "\n",

"IMAGES": "\n",

"SOUNDS": "\n",

"MATERIALS": "\n",

"OBJECTS": "\n",

"ACTIONS": "\n",

"CHOREOGRAPHIES": "\n",

"FileInfo": "\nEmbedded=FALSE\nCreatedBy=YourNameHere\nOrganization=TheAgency\nUrl=https://www.hash.com/forums/\nEmail=firstname.lastname@gmail.com\nLastModifiedBy=ModifiedBy\n",

"__text": "\nProductVersion=19\nRelease=19.0 PC\n\n\nSelected=TRUE\nFPS=30\n\n\n\n\n\n\n\n\n\n\n\n\n\n\nFileInfoPos=253\n"

}

}

 

 

When converting back (to xml) there are a few formatting things to watch out for:

 

Embedded=FALSE

CreatedBy=YourNameHere

Organization=TheAgency

Url=https://www.hash.com/forums/

Email=firstname.lastname@gmail.com

LastModifiedBy=ModifiedBy

<__text>

ProductVersion=19

Release=19.0 PC

Selected=TRUE

FPS=30

FileInfoPos=253

 

Extraneous text in red. The extra space needs to be removed as well.

[Rodney]

As an aside...

 

It would be nice if A:M could be forgiving of extra entries such as ... and extra space so that in addition to generally compatibility comments could be entered inside that would not immediately corrupt the file.

 

Update: Actually, A:M may already be forgiving of the and extra spaces. As long as the first line is removed.

And of course the file cannot be named with the extension .xml but needs to be .prj.

 

Also, I can see where leaving files unembedded can be advantageous when working with A:M files as xml assets.

That simplifies things considerably at the local level.