logo
down
shadow

Can we use compiled Haxe swf's swc's in Actionscript as normal libs?


Can we use compiled Haxe swf's swc's in Actionscript as normal libs?

By : Alma
Date : October 15 2020, 11:12 PM
may help you . Yes, you can, the performance increase is worth it, and it's surprisingly easy! I got 3-4X speed-up on both a simple sum-of-primes algorithm and a complex 2D bin packing algorithm.
I've posted an entire example project on github -- from Haxe source and compile scripts to usage in an AS3 project. Check it out: https://github.com/jcward/HaxeSWCExample
code :


Share : facebook icon twitter icon
ActionScript 3 Workflow using SWCs with linked external classes

ActionScript 3 Workflow using SWCs with linked external classes


By : yehuda2
Date : March 29 2020, 07:55 AM
around this issue As you said SWC is the way to go. I think I ran into a pretty similar situation, and I recommend you check this question out.Here is a dummy project on that approach.
Also, if it might speed up development time, I've made this tiny extension that declares the stage instances, initializes them and puts them in your clipboard so you can add that to your linked class. All you need to do initially is setup a naming scheme in the flash panel, then all you'll need afterwords is the Generate Button.
Securing SWFs, written in Actionscript 2 and 3

Securing SWFs, written in Actionscript 2 and 3


By : Greg Smith
Date : March 29 2020, 07:55 AM
it should still fix some issue Ya that's rite! As Tom said, Obfuscation is the best available method now.
But my concern was, to obfuscate all 3000 over files will be a pain. So I came with something which will automate the process. I just wrote a small piece of VB.net application to do so. (more like a batch file). Have not finalized yet.
ActionScript 3 SharedObjects don't persist across different swfs?

ActionScript 3 SharedObjects don't persist across different swfs?


By : G C
Date : March 29 2020, 07:55 AM
help you fix your problem Shared Objects are actually given their own folder so that they do not potentially collide with another SO of the same name. If you want to have multiple SWF's access a single SO, then you need to specify an actual path for the SO instead of allowing Flash to create one for you. This forces the SWF to read/write the same SO.
Here is the article that contains a deeper explanation and a few different solutions:
In IntelliJ how to create relative paths to swcs in module dependencies for Flex or actionscript modules?

In IntelliJ how to create relative paths to swcs in module dependencies for Flex or actionscript modules?


By : user2517318
Date : March 29 2020, 07:55 AM
To fix the issue you can do Have you tried to use a swc that is inside of the module's folder sources? ( one of the tabs next to dependencies ). I have never needed to identify this I assume its because you want your project portable?
If you establish this is by design, make a feature request if you already don't have an account. http://devnet.jetbrains.net/community/idea
Haxe IntelliJ / VSCode generated SWFs not recognised

Haxe IntelliJ / VSCode generated SWFs not recognised


By : arrowdv
Date : March 29 2020, 07:55 AM
Hope that helps I don't know if this is the correct solution but I built through OpenFL and pointed IntelliJ at the created /Export/flash/haxe/_generated/ directory and it worked. It looks like it would work for VSCode too.
Something doesn't seem right about it, though. like my SWF refs are of my previous build but everything else reflects the next build
shadow
Privacy Policy - Terms - Contact Us © bighow.org