What do you think about being compatible with Flash API / OpenFL API? #711
B4uti4github
started this conversation in
Ideas
Replies: 1 comment
-
|
I have a good idea for how it could be integrated. The idea is that it would be a programmable ecmascript node (using the Flash API, but with some elements linked, like the timeline, to Friction), and at the same time, you can create more nodes within the Flash node called symbols. There, you can use assets and everything else seamlessly, but in a Flash environment within Friction, using only the Flash API but redirected to Skia. When you use one of these flash nodes, you can reference the stage (i mean the Flash node) with |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I've seen news in recent days that Adobe Animate was going to be discontinued, although the cancellation was cancelled. I know you have a good user experience similar to Flash/Adobe Animate with properties, such as managing properties in OpenFL, even visually, and with ECMAScript support. What would you think if OpenFL were added to be more compatible with JSFL scripts and to be able to import XFL and SWF files? For me, it would be the best decision because it has a very similar base to Flash and their API also, and the UX will be very easy to migrate from Adobe Animate to this app.
Beta Was this translation helpful? Give feedback.
All reactions