FWIW, I still think we can/should work together on the compiler. To me, the
only difference in goals is that some folks want to emulate the Flash APIs, but
the current set of committers are not set up to do that, IMO.
-Alex
On 10/27/19, 11:34 AM, "Carlos Rovira" wrote:
Hi Jason,
Hi Jason,
It's a shame that the options don't fit for you. If at any time you think
that Apache Royale
may be an option, do not hesitate to contact us.
We will be happy to talk to you.
Thanks and best of wishes.
Carlos
El sáb., 26 oct. 2019 a las 17:03, Jason Huang ()
escribió:
> Thanks
Thanks guys for everything,
I'm afraid that I could not help you guys that much, anyway best wishes for
all of your hard works.
Best
Jason
On Wed, Oct 23, 2019 at 5:11 PM Carlos Rovira
wrote:
> Hi,
>
> I think this conversation helped a lot to know interested of each one and
> things we can do
Hi,
I think this conversation helped a lot to know interested of each one and
things we can do in the future. Maybe Jason and Kenny can join forces a see
if there's a way to bring WASM to Royale and create something like I
suggested with the name of "FlashRoyale" that could make current Flash
If Royale is successful, there will be libraries emulating all sorts of
platforms and runtimes expecting output in certain languages. Flash can be one
of them, but the repo holding the code doesn't have to be at Apache. Should it
be? Don't know for sure.
I'm sure that most of SpriteFlexJS
Thanks for the info Alex and better clarifying some of Royale's
overall goals. I certainly don't expect any of the current committers to
start working on a Flash API. I'm just more interested in how to integrate
a Flash API and if it's even worth it to do so.
To me, it sounds like a Flash API
First, a technical/factual matter: In Royale, if your code says
org.apache.royale.events.Event, the output is org.apache.royale.events.Event,
not "flash.events.Event". The SWF implementation of
org.apache.royale.events.Event subclasses flash.events.Event, and subclasses
something else for
FlashRoyale sounds like a good option. I’d love to see a good option for Flash
API emulation.
Targeting WASM (whatever the approach) would be a great addition.
Most of our focus has been more on business applications rather than animation
and 3D hardware acceleration. Having more folks on
I think that it's important to understand that while Flex was based on the
Flash API, that doesn't mean that the Royale framework also needs to be
based on the same API. Nor is it necessarily desirable in all cases.
One of the goals of the Royale framework is the concept of PAYG (pay as you
go),
Those are very good points and I've probably misunderstood the overall
picture of Royale.
It sounds like you use MXRoyale directly. FlashRoyale would be the same
thing, but that wouldn't fit into the idea of having a Royale codebase that
links to the proper library depending on target
Hi Carlos,
I’m just very confused with platform specified Apis you mentioned. I think
flash API is the base of everything, including flex. So we make flash API run
everywhere, then all other projects/libs would run everywhere too, including
flex. For our users they use exact same codes and
Hi Kenny,
For each platform there's ultimately a concrete API. So Royale ends
translating to the real APIs. Users writes in Royale ensuring their codes
are reliable over time no matter what platform you use or is trending.
I'd want to write a form, a game or a whatever we want with Royale code
I didn't realize that Royale was actually converting
"org.apache.royale.events.Event" to "flash.events.Event" for the SWF
target. It's the idea of one language for multiple targets. However, this
seems strange in that we are using ActionScript to begin with, but ditching
the naming convention.
Hi Jason,
as a developer that also like 3d software like Blender, Unity, and many
others in that segment I would like to see all the things you mention as
part of Royale.
I really think that would benefit the options give to our users. I think
all that options can be today available for all
Hi, guys.
Thanks for explaining things to me. I know Flex is a great commercial lib
that built base on flash.
Just imagining that we implement enough( minimum requirements) flash apis
for other great tools/libs that built base on flash,
such as Starling frameworks, Away3D, Flare3D(the one I used
Hi Jason,
The scope of Flash was more wide and open than Flex. Flex was created to
target Applications. Most of the time business applications composed by
forms, data grids, lists, graphs and other visual data representations.
While Flash can do that, productivity was very low in real world use
Hi Jason,
Volunteers in this project are welcome to work on whatever they want.
The reason I am interested in Flex instead of Flash is because Flex was
designed to abstract away the Flash API, so Flex is going to be more easily
portable to different runtimes than Flash. Supporting Flash will
Hi guys,
Now I see, we have same goals for delivering a comprehensive SDK to our
users.
As for Flash APIs, for my understanding, it is AS3 language build-in basic
library that provides basic Rendering, IO, networking, etc.
The relationship of Flash APIs with AS3 is similar to DOM with JS, .Net
Hi Jason,
to continue complementing the understanding of our goals. Royale has the
advantage to be prepared in theory to output to multiple targets (SWF, JS,
WASM, ...native iOS?, native Android?,). Since Royale is an SDK it
provides all the user need to build an app (compiler, framework, UI
Royale is currently primarily focused on migrating Flex apps, which is a subset
of all Flash apps. There are a couple of other non-Apache projects looking at
emulating the Flash APIs. So if your app is pure Flash, you might want to
contact those other projects. The main restriction is pretty
Hi,
I understood what you concerned about licensing/copyrights. I won't use the
previous AJC approaching at all, but writing a new compiler that compiles
AS3 codes to wasm format instead. So that would be a totally different
approach than I used to do.
As Alex mentioned "Royale currently has no
Hi Jason,
Welcome. I hope we find a way to work well with you.
First, a slight correction to what Carlos said about copyrights. Just about
everything of significance is copyrighted by a company or individual, so we're
not looking for things "not under a copyright".. But there must be an
Hi Jason,
great to have you in the list proposing that plans. Since Royale is multi
target with current support for SWF and JS, we really want to have others
and users asked many times about WASM support. So WASM is maybe the most
requested and wanted new target in Royale. So, yes, we want
23 matches
Mail list logo
