MonthOctober 2015

Manually installing Flash2Svg

Before trying this I would recommend trying to install using the ZXP Installer tool, this will give you access to the HTML5-based User Interface, but will still require manual updates.

If you’re having trouble installing Flash2Svg in Flash, here are some instructions to manually install the plugin.
This works in all versions (CS5 – CC 2017, as of writing) but will only give you the older, flash-based UI, not the newer HTML5-based UI.
Also note, the last version of the plugin that is compatible with CS5/CS6 is version 3.36.
This means some of the functionality won’t be there (e.g. embedding assets) but all of the most recent bug fixes will be available.

  • Download the latest ZXP
  • Change the file name of the extension from ZXP to ZIP
  • Extract the contents of the zip archive
  • Copy the SVG.swf and svg-help.xml files from the FLASH folder into this folder:
    C:\Users\{username}\AppData\Local\Adobe\Flash CS5\en_US\Configuration\WindowSWF
  • Copy the Extensible folder (also from the FLASH folder) and copy the whole folder into this folder:
    C:\Users\{username}\AppData\Local\Adobe\Flash CS5\en_US\Configuration\Javascript

Obviously change the version of flash in those paths to the correct one (e.g. ‘Flash CC 2015’).

Mac is very similar, something like:
/Users/{username}/Library/Application Support/Adobe/Flash CS5/…

On both systems you’ll probably have to show hidden folders to get there.

Haxe > Python > Remote debug on Raspberry Pi

Just got the Python remote step-through debugger working on RPi.
You can compile Haxe to Python your laptop, automatically deploy it to the RPi and then start a remote Python debug session on the device with one button.

Check out this article for the python debugger part of things:

Add an hxml file to your project called compile.hxml, in the project root:

-cp src
-python bin/
-main my.pack.Main

Change the details in there to match your project.

Then add a pre-launch tool to compile the Haxe code:

  • Run > Edit Configurations
  • Select your run configuration on left
  • Add a ‘Before launch’ task > “Run External Tool”
  • Add a new Tool
  • Locate the Haxe compiler in the Program field
  • Add these parameters (inc. -debug to include hx source back-references):
    compile.hxml -debug
  • Set working directory to ‘$ProjectFileDir$’

Note, this Tool configuration can be reused across projects, as long as they have the compile.hxml file.

Sticking points:

  • JetBrains Haxe plugin doesn’t work well with PyCharm (ended up using FD for coding).
  • Would be awesome to get the hx source back-references integrated into the debugger so that you’re debugging Haxe not Python code.

© 2017 Thomas Byrne

Theme by Anders NorenUp ↑