Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix JSON error compiling Flare with Flex SDK 4.6 and compc #7

Open
rpitting opened this issue Jun 14, 2012 · 2 comments
Open

Fix JSON error compiling Flare with Flex SDK 4.6 and compc #7

rpitting opened this issue Jun 14, 2012 · 2 comments

Comments

@rpitting
Copy link

If you are having trouble compiling Flare with the Flex SDK 4.6 and getting some error with com.adobe.serialization.json.JSON, it's because the API has changed.

How to fix:

  1. Remove any imports of com.adobe.serialization.json.JSON, it's not needed anymore.

  2. Replace JSON.encode with JSON.stringify

  3. Replace JSON.decode with JSON.parse

  4. In build.xml, in the target flare, uncomment this line

      <source-path path-element="${flare.lib}/"/>
    
@charlesone
Copy link

I went through these changes using Flashbuilder 4.6 and got the number of errors down to one:


So, following the direction of "Essential ActionScript 3.0" - Colin Moock, pp. 787-8:


To do so in Flex Builder 2, follow these steps: 
1. In the Navigator panel, select the project folder for the Main.swf application. 
2. On the Project Menu, choose Properties. 
3. On the Properties dialog, choose ActionScript Build Path. 
4. On the Library path tab, click the Add SWC button. 
5. On the Add SWC dialog, specify the path to module.swc.
6. On the Add SWC dialog, click OK. 
7. Under "Build path libraries," expand module.swc in the tree. 
8. Under module.swc, select "Link Type: Merged into code." 
9. Click the Edit button. 
10. On the Library Path Item Options dialog, for Link Type, choose External. 
11. On the Library Path Item Options dialog, click OK. 
12. On the Properties dialog, click OK.

You might have thought that would fix it, but no, the error persists doggedly.

What might be next?

Charlie ...

@quocuy
Copy link

quocuy commented May 25, 2015

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants