Jump to content
Hash, Inc. Forums
Sign in to follow this  
Rodney

Project Files in JSON format

Recommended Posts

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
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.

Share this post


Link to post
Share on other sites

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.

 

 

xmlView.jpg

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×