craiggrummitt / actionswift3 Goto Github PK

Firstly - I somehow think Adobe will never ever release as4.
anyone searching could find this repo - and get onboard.
http://www.yeahbutisitflash.com/?p=4812

https://plus.google.com/+JosephLabrecque/posts/HEr4m1eLZgC

If adobe open a lawsuit because of supposed trademarks on AS4 - it could only be a good PR exercise for this repo.

Hi Craig,

I love what you are doing here and Adobe / Google should totally throw some resources behind this.
Given Google are considering using swift as a first class language for Android- having a uikit alternative totally makes sense. Adobe should come to the party and help rebuild actionscript / ui libraries in swift.
This is an amazing job you've started. I built an objective-c to swift converter -> objc2swift.io I open sourced it on github - https://github.com/BellGeorge/objc2swift.io/

Porting flash over to swift is something that I'm looking to embark on shortly.
There's so many syntactical similarities.

I know Facebook rebuilt their uitableview to speed up things. AsyncDisplay.
I'd need to take another look - but removing UIKit would be a milestone.....do you agree?
Can core image be used on android?

Can you envisage this project working on other platforms ?

https://github.com/yahoojapan/objc2swift
This may warrant an entirely new project - but consider

the ecmascript standard is a known antlr format -
hypothetically -we could rejig the antlr grammar file from ecma to swift then rebuild this project here
https://github.com/yahoojapan/objc2swift

I have a ticket open for the code generation
https://github.com/yahoojapan/objc2swift/issues/22

I can imagine a webpage like this - where people could throw some actionscript class /or python for that matter - and it would spit out the corresponding swift class - easy - peasy.

I actually own the property http://objc2swift.io which I open sourced some time ago.

It would be nice if there was a podspec for this project...

if you run swift package build
it will automatically spit out a swift package structure

I believe if you nest a folder inside the Sources/ folder it will maintain the structure of project / other wise you have to flatten everything into the Sources folder.

once you have the package building
you may consider adding a make file / with a settings override file
eg.
--xcconfig-overrides settings.xcconfig
https://github.com/johndpope/tensorflow/blob/master/tensorflow/swift/settings.xcconfig

this was a Makefile I hacked the other week.
https://github.com/johndpope/tensorflow/blob/master/tensorflow/swift/Makefile

N.B. - todo the version control is pretty trivial - just create a tag on github repo.

came across this looking at as3lang.org http://gamua.com/starling/
https://twitter.com/as3lang

https://github.com/Gamua/Sparrow-Framework/tree/master/sparrow/src/Classes