Hi Mark El vie., 11 ene. 2019 a las 19:59, Kessler CTR Mark J (<mark.kessler....@usmc.mil.invalid>) escribió:
> 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. > maybe I'm wrong, but I think "package.json" will build your software (bring the external lib) and put available at "build-time" so then you can deploy as normal. I use Maven and I think there's a maven plugin to do this, since people I know told me, but since I didn't have this problem and have very few time I could not investigate it. If you use maven you could check about that plugin since I think is the right way to do this kind of things for JS libs. > > 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? > > Yes, please, I think it will be good to know about it :) Thanks Carlos > > -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 > -- Carlos Rovira http://about.me/carlosrovira
