Carlos,
I understand your logic now. Yes, having the SDK package / bundle updated
outside our environment on another machine once and then brought into the
environment with other downloaded attached pieces would be fine.
So I was allowed 2 weeks to test convert our only small app's client layout
(Flex targeting flash). I think we've managed to do about 60% mockup in that
time. Would you like me to start a new thread with my experiences / challenges
/ work-arounds?
-Mark K
-----Original Message-----
From: Carlos Rovira [mailto:carlosrov...@apache.org]
Sent: Friday, January 11, 2019 12:18 PM
To: dev@royale.apache.org
Subject: [Non-DoD Source] Re: Jewel alert.as
Hi Mark,
as part of the PAYG philosophy in Apache Royale we try to avoid extra
checks, at least in cases like this that the component required that
script, so in order to be used it must exists.
So we need to get a better way to ensure scripts inside controlled
environments. I still think we should manage it through some nodejs or npm
(package.json) so that script will ensure you download the right script and
package in the solution...
btw, I think I should support as you say since I expect you and other use
Jewel and want to join us providing PRs, patches, and new code to the mix.
I started this effort, but I think now is time for others to start using
and helping in adding and solving issues to grow to something very useful.
So thanks to you as well for taking the time to share with us your
experience :)
thanks!
Carlos
