Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

Might you have an AIR_HOME environment variable? The scripts assume a truly clean system where someone wanting js-only wouldn't have AIR set up in the environment. -Alex On 2/5/20, 7:21 PM, "OmPrakash Muppirala" wrote: I'm sorry I missed this thread from a while ago. I tried

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

I'm sorry I missed this thread from a while ago. I tried Alex's suggested fix on my current npm installation, but I am still getting the same error. Here is the pastbein: https://pastebin.com/raw/t4v8CWYe Maybe I am doing it wrong? Thanks, Om On Mon, Oct 14, 2019 at 10:31 AM Alex Harui

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

We've never tried a hotfix release version. Could be a lot of work to get it to work. Might be easier to just roll forward to 0.9.7. Volunteers are welcome to try. I won't be spending time on it. Regarding a "modified SDK", the issue is not a licensing issue, but a branding issue. We

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

Hi Piotr, about license: My common sense says that you can provide a modified SDK (since is an Open Source project) but you should state that *it is not* the official 0.9.6 SDK release, but a modified one provided by Moonshine to fix an issue. Maybe others could know and say more about this.

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

Ok that's can be an idea - It may happen or not - We will see. Currently I'm interested really in an answer for the license question. pon., 14 paź 2019 o 12:34 Carlos Rovira napisał(a): > Hi Piotr, > > I think since is a hot fix it starts from 0.9.6 release branch and there > you apply the fix

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

Hi Piotr, I think since is a hot fix it starts from 0.9.6 release branch and there you apply the fix to generate a 0.9.6.1. Then when released the hot fix is merged in current develop branch with 0.9.7 Or at least is what I suppose it should be El lun., 14 oct. 2019 a las 12:15, Piotr

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

Hi Carlos, I was talking exactly about hot fix. However it seems to me a bit difficult, cause we have now in develop version 0.9.7 - I'm not really sure how maven react if I change it to 0.6.1 ;) Thanks, Piotr pon., 14 paź 2019 o 11:13 Carlos Rovira napisał(a): > Hi Piotr, > > other option is

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

Hi Piotr, other option is to release a hot fix version like 0.9.6.1 if you want to release in few days what do you think? El lun., 14 oct. 2019 a las 9:58, Piotr Zarzycki () escribió: > Hey Guys, > > I'm willing to try release very soon another version of Royale just with > fix for our issue

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

Hey Guys, I'm willing to try release very soon another version of Royale just with fix for our issue with broken royale config. If it won't happen next week I will probably do that next month which will be I think enough to have proper release not only with that fix. Anyway my question is a bit

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

Hi Guys, I would share my experience and feelings as a new and fresh user on Apache Royale, hope it will help... The background : I'm a Flex developper since about 10 years. I love it because for me it's (was...for flashplayer) the fastest way to do something that would have same render on

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

I know this isn't the last post on the thread, and I echo the sentiment of others that we want to know what problems folks are running into getting started with Royale. Meanwhile, back to the technical issue. Josh is mostly right. I don't think folks test the nightly -js package from the

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

Hi Richard (and others in the same wagon), I only can say one thing: If you're a former Flex user, I encourage you to not give up and try to get your path with Royale. I think it can be difficult to start, but at this point (6 months after your latest try). I think is worth it and we are in good

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

Hearing from new users what the roadblocks are, is very useful. To me, Royale feels very plug and play, but I know it well. It’s hard to see the roadblocks to new users when you have been involved for a long time. Thinking back to the days I was learning Flex, I think it was easy to learn it

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

Hi Piotr Last time would be a good 6 months ago. I didn’t ask for help but I know you all would  have been very helpful if I had - I see you doing so week in week out. We are using Angular for new work but still have a number of existing apps we need to port over,  re - write or convert to air

Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

Hey Richard, When you were trying Royale - did you ask for help on dev list or in private? I agree that at the beginning earlier it was a problem to start. Now that barrier is a bit lower. If you need any help you can ask here or in private we are happy to help and get you move forward. Thanks,

Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

Hey Andrew, I recommend you make small workaround. 1) Take again JS only version of Royale 0.9.6 2) Open framework/royale-config.xml 3) Remove everything what is inside tag library-path 4) Try rebuild Thanks, Piotr On Thu, Oct 10, 2019, 12:21 AM Andrew Wetmore wrote: > I recently had a hard

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

Well said Andrew - couldn’t agree more. I am a long time Flex developer (back to the beta) and have tried many times to get started with Royale, so that we can move all our existing apps over,  but have fallen at the first hurdle every time. We have now given up and are moving most over to

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

You were probably using the JS-only version of 0.9.4. As I said, the JS-only version does not require Ant or npm. You're not missing any new requirements/dependencies that were added between 0.9.4 and 0.9.6. *The JS-only version of 0.9.6 is simply broken.* Something in the build went wrong, and

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

I recently had a hard drive crash, so I have a new hard drive without many past artifacts, a virgin system. I was using 0.9.4 in Moonshine before the crash without, as far as I know, any Ant or npm magic. Have things changed significantly between that release and this one?

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

That would be fine. I am stuck, evidently, at something in the 0.9.6 release of the JS-only version being broken. Virus-free. www.avast.com

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

Node/npm is pretty normal prerequisite for most JS development these days, but I understand your point. Ideally, we should be encouraging developers to start with the JS-only version, which doesn't require any of those special dependencies (other than Java, which is necessary to run the

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

The main royale-asjs README mentions the Adobe stuff as optional dependencies, but the instructions seem to be aimed at contributors: https://github.com/apache/royale-asjs#additional-prerequisites-for-swf-output What a non-contributor user is expected to do appears to be mentioned on this page

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

Thanks @Josh Tynjala . Do we say that anywhere in the instructions where a new user would run into it? Virus-free. www.avast.com

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

If you downloaded the js-swf binary distribution, you need to add the Adobe dependencies manually. We cannot distribute them. The playerglobal.swc in the js-only version is not the real one from Adobe. It's just a placeholder to make certain IDEs happy. I think it's just a copy of js.swc. --

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

I wiped out the previous project and tried again with the Royale JS-SWF version. When I try to compile the project in Moonshine for either JS or Flash, I see this error message: "This SDK does not contains playerglobal.swc in frameworks\libs\player\11.7\playerglobal.swc. Download playerglobal

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

When you build with AIR_HOME (which is required to create release artifacts, since we want to produce both jsonly and js-swf in one run), a different target called "jsonly-package" run and tries to muck with some files before packaging the js-only artifacts. It could be that the jsonly-package

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

It looks like the Ant target that updates the library-path for the JS-only build is called tweak-for-jsonly. Copied here for convenience: https://paste.apache.org/asn0i I see that it has unless="env.AIR_HOME", which means that this target is skipped if the AIR_HOME environment variable is set.

Re: Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

I just installed @apache-royale/royale-js from npm, and I'm seeing the same errors. -- Josh Tynjala Bowler Hat LLC On Wed, Oct 9, 2019 at 6:52 AM Piotr Zarzycki wrote: > Hi Guys, > > It looks like we have broken royale-config in released SDK. Andrew raised > in

Broken royale-config in JS only build of released Apache Royale SDK 0.9.6

Hi Guys, It looks like we have broken royale-config in released SDK. Andrew raised in Moonshine GitHub issue that he couldn't build Hello World project. I tried Moonshine and downloaded JS-only version of SDK. I get following error [1]. I downloaded JS-SWF version and tried compile project again