Hi Alex,
I tested and the Alert is working now.
Also PoupManager add is also working.
I see a lot of features to implement PoupManager remove is not working,
FormItem, etc ...
Thanks for you time on the tutorial I will carefully read and see if I can
implement one of the missing features.
Hi Alex,
I tested and the Alert is working now.
Also PoupManager add is also working.
I see a lot of features to implement PoupManager remove is not working,
FormItem, etc ...
Thanks for you time on the tutorial I will carefully read and see if I can
implement one of the missing features.
Hi Alex,
I tested and the Alert is working now.
Also PoupManager add is also working.
I see a lot of features to implement PoupManager remove is not working,
FormItem, etc ...
Thanks for you time on the tutorial I will carefully read and see if I can
implement one of the missing features.
--
I used version 14 for many years.
Only a few months ago I updated to latest version.
0 improvements about core features.
A lot of bloatware (seems as anti-virus programs) however this can be easily
disabled.
New look and feel comparing to version 14.
Native support for MacBook touchbar (nice to
Hi Alex,
That would be great.
--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
How to add that cool debug toolbar to VS Code solution ?
Currently I have to do cmd + shift + p (macOS) to do a build-debug and then
I have to open the folder and then open the file on my browser.
I would like to:
1. Add that same toolbar
2. If possible when build, automatically open the
And the most important more of your code won't need as much changes.
> Yes. In a framework change perspective is the cheapest approach but for
> now is not there iet (let's see in a near future), meanwhile I will check
> Royale without emulation.
--
Sent from:
Basic cannot work without Jewel. It is correct ?
Jewel it's like a UI implementation using Basic like mx ou spark for Flex,
correct ?
So, what happens if I'm using Jewel and at some point I would like to
completely change my UI aspect ?
Or Jewel is the first implement, a set of UI with a default
Thank you very much.
Now I understand the Express and Basic and Strands and Beads.
Express ends up to be more what Flex is about but Basic + Strands and Beads
it's the best way to go.
--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
OK, thank you.
--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
http://apache-royale-users.20374.n8.nabble.com/
Hi Carlos,
OK, it's a Panel.
Thank you.
--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
OK, thank you.
--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
OK, I understand now.
For one hand it's better than Flex SDK and other frameworks, because avoids
to load tons of code that I don't need all the time.
For another hand I will end up with final mxml with more code but it's OK.
Thank you for the detailed explanation.
--
Sent from:
Royale is the equivalent for in Flex/Spark ?
--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
I saw initialView in every example in Royale.
This seems strange for me.
Why not put the component instance directly on mxml ?
--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
Thanks for the explanation.
--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
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/
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,
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
"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
My logic is:
1. Apache Royale already changed the namespaces of mx and spark, so there is
not reason to do do the same here;
2. It's seems that it's the last rest of piece of code (one line of code per
mxml) with reference to adobe;
3. We should get rid of adobe, flash, air, swf and swc from the
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
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
As the title said.
Why the namespace Adobe in: http://ns.adobe.com/mxml/2009
Could not be updated to http://ns.apache.com/mxml/2018 ?
--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
Yes, it was what I tried but my bad. I failed on my explanation.
I checked tour the flex and it also does not work (mx alert).
For you explanation, I see that the alert it's a custom popup and not a
native alert browser and it makes sense at same point. At least to be
browser independent and more
OK, I see now.
So, in this case I can try to implement the PopUp (it's not an easy one) and
suggest the new implementation.
The same for any mx component.
Correct ?
--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
PopUpManager createPopUp and addPopUp, both methods exists however nothing
happens.
Debugging on addPopUp, I see that the SDK does nothing with the window
instance.
Does methods was created and was not finished for now, right ?
Any special reason ?
--
Sent from:
While debugging on browser (Google Chrome on macOS), I saw that I can put a
break point on my MXML (not the generated JS) and debug and inspect
variables.
UAU !
Great work !
--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
No more errors on console but nothing happens :(
No alert.
--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
It was I thought.
OK, thanks.
Later I will pick up the new build and test again.
I will let you know the results and my findings.
--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
When the Royale night builds/Jenkins runs ?
Once per day, hour or immediately after a commit ?
--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
The bug occurs inside Alert.js
var /** @type {mx.managers.ISystemManager} */ sm =
org.apache.royale.utils.Language.as(mx.core.FlexGlobals.topLevelApplication.systemManager,
mx.managers.ISystemManager, true);
var /** @type {Object} */ mp;
On this case,
"This is the most compelling reason to me."
Yes, I agree.
Last decade was Flash, yesterday was AIR, today is JS but tomorrow could be
something else and it would be easier to target again new technology.
--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
1. Flash offers runtime type checking which helps catch bugs.
This means that I can target JS and quickly switch to SWF just for debug ?
Can't I debug now directly on VS Code + Royale JS ?
I saw something on twitter that currently it's possible to debug from JS but
I could be mistaken however
"Delete the bin/js-debug folder and try again."
That did the trick. I have to get used to this new approach.
With Flex since is a single file, is always updated.
There was probably old files from the previous compile with the previous SDK
version.
Now I can see the button on the page and without
"Delete the bin/js-debug folder and try again."
That did the trick.
I need to get used to this new approach since Flex use a single file.
The previous compile with the previous Royale SDK probably did this
conflite.
Now, I can see the button on the screen without console errors however when
I
Second test from a different e-mail account.
--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
38 matches
Mail list logo
