Great example Carlos.
Thank you very much.
I will play around with Royale and I have a few question that I will put in
different threads.
--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
Yes Piotr, it is true.
I am using some libs that are modified like fiber and as3corelib and
shared them on github.
Thanks,
Serkan
16.11.2018 08:56 tarihinde Piotr Zarzycki yazdı:
Hugo,
I'm not sure where I have seen this but I think Serkan who migrating
his app has it on the GitHub.
Serk
Hi Hugo,
I think the closest is this:
https://royale.apache.org/customization-through-the-royale-api/
Is a jewel button that popups a jewel alert and inside some content is
added (a jewel checkbox). You can prepare some content in mxml and add to
the alert content
HTH
Carlos
El vie., 16 nov
Hi Carlos,
Thanks for sharing.
Yes, that's an alternative way to migrate and at same point of view, it's a
good strategy.
It's not proper a migrate/port process but more a total UI refactoring.
It's 2 steps in 1 if someone move from mx/spark Flex to mx/spark Royale and
then jewel Royale.
Yes, fo
Hi,
I'm migrating a project and choose to make a mixed approach based on the
following points:
1.- Left server side (Java with BlazeDS) part without touch. Just turning
off small messages for remote object calls
2.- Migrate as many AS3 code as we can, that part that is not tied to MX or
SPARK com
We're following a slightly different approach; the effort in getting the
emulation classes all put together and working properly is huge and it will
end up being a similar scale to the Flex libraries - lots of code handling
cases that are very rarely used... so I've much preferred the Royale
conce
le-docs/Create%20An%20Application.html
The "Flex equivalents in Royale" is probably a little out of date as there's a
lot more available now I think!
Hope that helps
Andrew
-Original Message-
From: hferreira [mailto:hferre...@solidsoft.pt]
Sent: 16 November 2018 10:
"Yeah, it is a lot to learn. Did you ever make patches to the Flex SDK
framework code? "
A few ones yes, but the deepest I went was:
1. Debug;
2. Find bugs that affects my code;
3. Find logical patch;
4. Copy the original code from the SDK to my project;
5. Apply the patch;
6. Fill a bug on the JI
Hugo,
I'm not sure where I have seen this but I think Serkan who migrating his
app has it on the GitHub.
Serkan please correct me if I'm wrong. Maybe it can help, depends where he
is with his migration...
Piotr
On Fri, Nov 16, 2018, 5:10 AM Alex Harui wrote:
> Yeah, it is a lot to learn. Did
Yeah, it is a lot to learn. Did you ever make patches to the Flex SDK
framework code?
I will try to put together a step-by-step tutorial on the next component I get
to run. I'm not sure there is only one path to take, but maybe. Until I get
to that, you can try looking at the change history
Yes. I read before posted.
In a conceptual point of view is a good material.
Explains the approach.
Create the component without implementation, surrounding Royale API (the
important is the emulation like an interface, the content/implementation can
and should be different from Flex SDK, using dire
Have you already read this?
https://github.com/apache/royale-asjs/wiki/emulation-components#getting-an-emulation-component-to-run
-Alex
On 11/15/18, 4:24 PM, "hferreira" wrote:
Would be great if one of the experients Royale developers produce a basic
step by step tutorial how to imple
Would be great if one of the experients Royale developers produce a basic
step by step tutorial how to implement a MXRoyale or SparkRoyale component
from scratch (a button for example).
So, let's imagine that there is no MXRoyale button iet and with this
tutorial, would be possible to create a but
13 matches
Mail list logo
