Re: Build failed in Jenkins: royale-asjs_jsonly #3219

Hi Carlos, It looks like you have bump into similar issue as I am some time ago. I was preparing Maven build but have following compilation problems [1] - Alex point me what to do, but it didn't help. I didn't have time yet to back to that task, but I will have to sooner or later. If you figure ou

Re: Build failed in Jenkins: royale-asjs_jsonly #3219

Ah! ok Piotr, I remember that. will try. thanks! :) El mar., 9 jul. 2019 a las 9:33, Piotr Zarzycki () escribió: > Hi Carlos, > > It looks like you have bump into similar issue as I am some time ago. I was > preparing Maven build but have following compilation problems [1] - Alex > point me what

RE: Build failed in Jenkins: royale-asjs_jsonly #3219

Hi Carlos, It looks like [1] this is experimental technology, which is probably why it’s missing from our typedefs [2]. Theoretically it can be added [2], but I don’t know if this is a good idea if it’s not guaranteed to work in every browser. Thoughts? [1] https://developer.mozilla.or

Re: Build failed in Jenkins: royale-asjs_jsonly #3219

Hi Yishay, Should I add also my stuff to make it work to Royale-Extras ? Thanks, Piotr wt., 9 lip 2019 o 10:14 Yishay Weiss napisał(a): > Hi Carlos, > > > > It looks like [1] this is experimental technology, which is probably why > it’s missing from our typedefs [2]. Theoretically it can be ad

RE: Build failed in Jenkins: royale-asjs_jsonly #3219

I’m not sure. Looking at the js build [1] I can see the externs file being read from that repo, so I’m assuming one of them would need to be modified in order for the type to be updated. Maybe Harbs can comment on this, as he set up the repo. [1] https://github.com/apache/royale-typedefs/blob

Build failed in Jenkins: royale-asjs_jsonly #3220

See Changes: [tzivi] Only set the content-type if it’s defined in URLRequest -- [...truncated 1.71 MB...] [java] [getlocal0, pushscope,

Re: Build failed in Jenkins: royale-asjs_jsonly #3219

animate is not yet a standard and it doesn’t work in Edge or Safari. I’m not sure if it’s something we should be adding just yet... > On Jul 9, 2019, at 11:41 AM, Yishay Weiss wrote: > > I’m not sure. Looking at the js build [1] I can see the externs file being > read from that repo, so I’m as

Re: Build failed in Jenkins: royale-asjs_jsonly #3219

Hi Yishay, thanks for the info. I'm using Web Animations API in Jewel through a polyfill to ensure it working properly in all browsers included IE11, so its working fine. The problem was more about getting type checking with Royale, so make it more "royale" instead of using th bracket access, si

Re: Build failed in Jenkins: royale-asjs_jsonly #3219

There are only a few files which are currently being used from that repo, we can add more files to the build scripts. If we do add a typedef for animate, it should probably go in a “non-standard” file. Although simply using bracket notation on animate until it’s a standard might be the right wa

RE: Build failed in Jenkins: royale-asjs_jsonly #3219

There’s also a closure compiler issue [1]. Maybe we can get some direction there. [1] https://github.com/google/closure-compiler/issues/2134 From: Harbs Sent: Tuesday, July 9, 2019 11:58:10 AM To: dev@royale.apache.org Subject: Re: Build failed in Jenkins: r

Re: Build failed in Jenkins: royale-asjs_jsonly #3219

Take a look at the following files in the typedef repo: Lines 108-166 in build.xml Line 67 and later in pom.xml Notice the different paths in externc-config.xml > On Jul 9, 2019, at 11:57 AM, Carlos Rovira wrote: > > So I can add Web Animations API externs there, but this will trigger some > bu

Re: Apache Royale Animations framework

ok Alex, that's fine. For me the game is between the two I already mentioned (web animations api and popmotion. As I have the time to play with both, I'll be able to see if we need both, or one purpose is replacing the other, and what's better or more flexible. In the end seems both are duplicatin

Re: Build failed in Jenkins: royale-asjs_jsonly #3219

Hi Harbs, I think using it through the polyfill is safe [1], since Jewel is already using it and working in Safari, IE11 and Edge (check TabBar example, indicators animation is done with animate FLIP technique). I think is the same as dialog API, that we're using in Jewel Alert from the beginning.

Build failed in Jenkins: royale-asjs_jsonly #3221

See Changes: [shiffy] added colors -- [...truncated 1.71 MB...] [java] [getlocal0, pushscope, newcatch(0), dup, setlocal(5), dup, pushs

Jewel CSS winding up in non-Jewel apps

I have no jewel components in my app, but I’m suddenly seeing TONS of jewel css in my app. Similarly, I’m seeing Basic CSS (such as Button) which did not used to be included (and is messing up the visuals in my app). Has something changed with the logic which includes CSS? Harbs

Re: Jewel CSS winding up in non-Jewel apps

Hi Harbs, there are no changes at least that I know. The way Jewel CSS was done is stable and didn't change for so long. So maybe you're getting some regression introduced recently. Can you give more details? Can imagine what could be happening if you don't have any jewel theme in your build chai

Re: Jewel CSS winding up in non-Jewel apps

Like I mentioned, it seems to be a problem with Basic as well. That leads me to believe it’s a compiler problem. > On Jul 9, 2019, at 1:26 PM, Carlos Rovira wrote: > > Hi Harbs, > > there are no changes at least that I know. The way Jewel CSS was done is > stable and didn't change for so long.

Re: Jewel CSS winding up in non-Jewel apps

For example, I’m getting the following CSS which did not used to be included (as I’m not using Basic Buttons): Button { border: 1px solid #808080; padding: 4px; background-color: #f8f8f8; margin: 0px; border-radius: 2px; } Button:hover { border: 1p

Re: Jewel CSS winding up in non-Jewel apps

I think this was already solved by you many months ago when trying to fix the problems I was getting while implementing Jewel styles. So seems a regression without doubt. El mar., 9 jul. 2019 a las 12:38, Harbs () escribió: > For example, I’m getting the following CSS which did not used to be >

Re: Build failed in Jenkins: royale-asjs_jsonly #3219

Hi Harbs, Unfortunately I don't see different. externc-config.xml has url.js in target/downloads/browser/url.js. Ant build is downloading url.js to that folder [2]. Maven build is doing exactly the same [3]. What am I missing ? [1] https://github.com/apache/royale-typedefs/blob/952664e244c75f970

Re: Build failed in Jenkins: royale-asjs_jsonly #3219

I see you added that line. It does not look like url.js was modified in royale-extras. Why are you downloading it from there? > On Jul 9, 2019, at 2:26 PM, Piotr Zarzycki wrote: > > Hi Harbs, > > Unfortunately I don't see different. externc-config.xml has url.js in > target/downloads/browser/u

Re: Build failed in Jenkins: royale-asjs_jsonly #3219

I thought this is the right place, from where I should download it to have URLSearchParams available ? wt., 9 lip 2019 o 13:33 Harbs napisał(a): > I see you added that line. It does not look like url.js was modified in > royale-extras. Why are you downloading it from there? > > > On Jul 9, 2019,

Jenkins build is back to normal : royale-asjs_jsonly #3222

See

Build failed in Jenkins: royale-asjs #2444

See Changes: [shiffy] added colors [tzivi] Only set the content-type if it’s defined in URLRequest [carlosrovira] Revert "we don't need bracket access for Element.animate method is

Jenkins build is back to normal : royale-asjs #2445

See

Re: Tour de Jewel regression in Jewel Alert (release version)

Hi Josh, I'm finding something similar trying to use .animate instead of ["animate"] COMPILE::JS public function animateIndicator(positionDiff:Number, widthDiff: Number, duration:int, easingFunction:String):void { indicator_content.animate( [

Jenkins build is back to normal : royale-asjs_MXTests #912

See

Support for XML embedded via 'source' attribute

Hi all Am I missing something, or do we not yet have support for something like: This is creating an XML object with ID 'myXML' but then not picking up and initialising it with the contents of that source file.. If this isn't implemented yet, then what would people think is the best way to

Re: Support for XML embedded via 'source' attribute

Hi Andrew, To me if it is possible it should be a bead which is able to load external file and inject to source. Do you get any kind of console output in the browser ? What will happen if you set full path to source property to that XML file ? Thanks, Piotr wt., 9 lip 2019 o 15:52 Frost, Andrew

Re: Tour de Jewel regression in Jewel Alert (release version)

Just added to typedefs web-animations api fro Royale-extras, so now is easy to try it just changing indicator_content.["animate"]( to indicator_content.animate( El mar., 9 jul. 2019 a las 15:33, Carlos Rovira () escribió: > Hi Josh, > > I'm finding something similar trying to use .animate instea

Re: Support for XML embedded via 'source' attribute

Hi The only slight issue with that approach might be the asynchronous nature.. in the Flex world, if we embed something in this way, it's packaged into the SWF and available immediately, and set up during an object's initialisation prior to the "applicationComplete" event. If we do an async loa

RE: Support for XML embedded via 'source' attribute

Hi Andrew, There’s an example [1] here. [1] https://github.com/apache/royale-asjs/blob/develop/examples/mxroyale/tourdeflexmodules/src/explorer.mxml From: Frost, Andrew Sent: Tuesday, July 9, 2019 4:52:36 PM To: dev@royale.apache.org Subject: Support for

RE: Support for XML embedded via 'source' attribute

Thanks - that looks good! I'll have a quick play with that set-up... many thanks Andrew -Original Message- From: Yishay Weiss Sent: 09 July 2019 15:10 To: dev@royale.apache.org Subject: [EXTERNAL] RE: Support for XML embedded via 'source' attribute Hi Andrew, There's an example

RE: Support for XML embedded via 'source' attribute

Maybe this [2] is closer to what you want. I’ve tested [1] but not [2]. According to [2] your syntax was ok, so maybe post a test case demonstrating your problem. [2] https://github.com/apache/royale-asjs/blob/develop/examples/mxroyale/tourdeflexmodules/src/spark/controls/TextLayout3Example

Re: Tour de Jewel regression in Jewel Alert (release version)

You did exactly the same as me and for me it doesn't work. If you will have time can you clean your local Maven repository and build your application with usage of your API ? Let me know if it's working. Of course do this once build of type-defs will be ready [1] and infra fix machine [2] ;) [1] h

Re: Tour de Jewel regression in Jewel Alert (release version)

Hi Piotr, I found that still did remove the api from missing.js in typedefs, removing that and rebuilding all gives me the following error when reach to the build SDK with ANT step: compile-swf: [echo] Compiling libs/Jewel.swc [echo] ROYALE_HOME: /Users/carlosrovira/Dev/Royale/Source/

Re: Tour de Jewel regression in Jewel Alert (release version)

By rebuilding all - You mean that you have build typedefs, compiler and asjs - using Maven and than your app ? wt., 9 lip 2019 o 16:23 Carlos Rovira napisał(a): > Hi Piotr, > > I found that still did remove the api from missing.js in typedefs, removing > that and rebuilding all gives me the foll

RE: Support for XML embedded via 'source' attribute

Hi Okay [2] is exactly what we had, but I've just realised we didn't have this in a section, which is presumably why the compiler had ignored it! So add this, and suddenly I get the XML object being initialised with the XML file being embedded into the main .js file. Interesting difference be

Re: Tour de Jewel regression in Jewel Alert (release version)

yes, and then after maven build sdk with ANT. what seems to fail is ANT SDK build El mar., 9 jul. 2019 a las 16:25, Piotr Zarzycki () escribió: > By rebuilding all - You mean that you have build typedefs, compiler and > asjs - using Maven and than your app ? > > wt., 9 lip 2019 o 16:23 Carlos Rov

Re: Build failed in Jenkins: royale-asjs_jsonly #3219

Generally, if we need a browser API that Closure doesn't include in it's official externs, we add it to missing.js in the appropriate library in royale-typedefs. - Josh On Tue, Jul 9, 2019, 4:39 AM Piotr Zarzycki wrote: > I thought this is the right place, from where I should download it to hav

Build failed in Jenkins: royale-asjs_MXTests #913

See -- [...truncated 944.58 KB...] [mxmlc] scanning for overrides: ConditionalValue [mxmlc] scanning for overrides: DeviceNames [mxmlc] scanning

Re: Build failed in Jenkins: royale-asjs_jsonly #3219

ok Josh, so this means I was doin it correctly from the beginning. I'll do the change to put that API in missing Thanks! El mar., 9 jul. 2019 a las 16:57, Josh Tynjala () escribió: > Generally, if we need a browser API that Closure doesn't include in it's > official externs, we add it to missing.

Re: Apache Royale Animations framework

I'm not sure what "we need both" means. If "we" is your company, then yes, you are welcome to choose one or the other, if "we" is Royale, then I would prefer that Royale does not choose one over the other and hope that volunteers will provide wrapping for both. My 2 cents, -Alex On 7/9/19, 2

Re: Build failed in Jenkins: royale-asjs_jsonly #3219

IMO, adding an API for missing.js should only be done for APIs that are truly cross-browser. If an API requires a polyfill, then if we add it to missing.js and someone tries to use it on the browser that doesn't support it, it won't work for them without the polyfill. Either there should be a

Re: Build failed in Jenkins: royale-asjs_jsonly #3219

+1. > On Jul 9, 2019, at 6:43 PM, Alex Harui wrote: > > IMO, adding an API for missing.js should only be done for APIs that are truly > cross-browser. If an API requires a polyfill, then if we add it to > missing.js and someone tries to use it on the browser that doesn't support > it, it won

Re: Build failed in Jenkins: royale-asjs_jsonly #3219

url.js is part of the standard externs in the closure compiler repo. We only need to download the ones from royale-extras for files that are modified from the google one. > On Jul 9, 2019, at 2:39 PM, Piotr Zarzycki wrote: > > I thought this is the right place, from where I should download it

Re: Support for XML embedded via 'source' attribute

Are you using Windows? Do you have the JAVA_TOOL_OPTIONS set for utf8? I think some parts of the compiler may open a file expecting utf8 and other parts just take whatever the JRE gives it. HTH, -Alex On 7/9/19, 7:31 AM, "Frost, Andrew" wrote: Hi Okay [2] is exactly what we ha

Re: Tour de Jewel regression in Jewel Alert (release version)

Did the typedefs for Ant get rebuilt? How should HTMLSpanElement have a "animate" API defined for it? I’m not sure if we can tell Google Closure Compiler that HTMLSpanElement should have an "animate" API since I think it picks up the externs for built-in browser classes from its own externs, s

Re: Apache Royale Animations framework

Hi Alex, my company really does not need one or another. This is more something I'm interested to get more appealing UX. So I'll be adding one if I have the time, so at least we have some of this available to others. But others could add others too (hope so for this and for many other things ) El

RE: Support for XML embedded via 'source' attribute

I did earlier! but just checked, and no I don't. Time to add that to the system environment variables I think.. that might make the difference I guess; but for now the fx:XML insertion is working well.. thanks -Original Message- From: Alex Harui Sent: 09 July 2019 16:58 To: dev@roya

Re: [royale-compiler] branch develop updated: PackageHeaderEmitter: output goog.require() for externs because release builds fail without it

Without a goog.require(), the .js file for the extern does not seem to be copied to the output folder, and Closure renames its APIs. How the compiler behaved *before* my change: * If I reference the extern in a library, the compiler did not add a goog.require() for it. * If I reference the extern

Re: Build failed in Jenkins: royale-asjs_jsonly #3219

Hi Alex, El mar., 9 jul. 2019 a las 17:43, Alex Harui () escribió: > IMO, adding an API for missing.js should only be done for APIs that are > truly cross-browser. If an API requires a polyfill, then if we add it to > missing.js and someone tries to use it on the browser that doesn't support > i

Re: Tour de Jewel regression in Jewel Alert (release version)

El mar., 9 jul. 2019 a las 18:03, Alex Harui () escribió: > Did the typedefs for Ant get rebuilt? yes, since I pass a script that makes a full rebuilt > How should HTMLSpanElement have a "animate" API defined for it? > since Element.animate() is the API we are trying to add > > I’m not su

Re: Build failed in Jenkins: royale-asjs_jsonly #3219

I’m really not excited about the use of inject_html in Framework code. > On Jul 9, 2019, at 7:13 PM, Carlos Rovira wrote: > > Hi Alex, > > El mar., 9 jul. 2019 a las 17:43, Alex Harui ( >) > escribió: > >> IMO, adding an API for missing.js should only be done f

Re: Build failed in Jenkins: royale-asjs_jsonly #3219

Especially if the purpose of inject_html is to load JS from a CDN. There will definitely be users of Royale who cannot have external dependencies like that, and they'll need a way to override the behavior to load a JS file from their own server instead. -- Josh Tynjala Bowler Hat LLC

Re: [royale-compiler] branch develop updated: PackageHeaderEmitter: output goog.require() for externs because release builds fail without it

I can't tell from this thread what an "extern" is, but I believe at least in js-debug, if you goog.require something that doesn't have a goog.provide in it, there can be other problems. So maybe it was already broken, but this does not seem like a positive change. I expect other things to brea

Re: Tour de Jewel regression in Jewel Alert (release version)

You may need to verify that missing.js APIs get passed to Google Closure Compiler. I think they don't. So a separate typedefs SWC may need to be created for it. It may be that other APIs in missing.js get renamed as well and nobody noticed until now, or by luck, some other API usage was preve

Jenkins build is back to normal : royale-asjs_MXTests #914

See

Re: [royale-compiler] branch develop updated: PackageHeaderEmitter: output goog.require() for externs because release builds fail without it

It seems that Jewel is being compiled with a couple of ActionScript classes marked with @externs. Perhaps that's the problem. Maybe those classes should be compiled into a separate SWC. Maybe the compiler should not allow classes with @externs and classes without it in the same SWC. -- Josh Tynjal

Re: Build failed in Jenkins: royale-asjs_jsonly #3219

IMO, for any wrapping of third-party libraries, there should be inject_html for the third-party JS code. The Basic framework should avoid any use of third-party libraries and thus avoid inject_html, but it would be great to have lots of third-party libraries supported by other SWCs in Royale.

Re: Build failed in Jenkins: royale-asjs_jsonly #3219

IMO, the ability to override the URL for an inject_html is just a missing feature. My 2 cents, -Alex On 7/9/19, 9:30 AM, "Josh Tynjala" wrote: Especially if the purpose of inject_html is to load JS from a CDN. There will definitely be users of Royale who cannot have external dependenc

Re: [royale-compiler] branch develop updated: PackageHeaderEmitter: output goog.require() for externs because release builds fail without it

Well, we should see how hard it would be to allow mixing @externs and regular AS files. I think you are right that we are probably just finding issues with source-externs in libraries instead of the main app. That said, there may be a difference between supporting some third-party library vs s

Re: Build failed in Jenkins: royale-asjs_jsonly #3219

We have 2-3 inject_html in Jewel that can be used to try to configure the inject_hmtl in other way. It would be great to implement some other option that not depend from a CDN load, so Jewel can "eat its own food". If someone have clear how to do that and provide one example of that I can work on t

Re: Tour de Jewel regression in Jewel Alert (release version)

ok Alex, I order to look at this in the compiler. Where I can look? if you remember another js that is passed to GCC I could try to follow the same pattern to add missing.js, El mar., 9 jul. 2019 a las 18:39, Alex Harui () escribió: > You may need to verify that missing.js APIs get passed to Goo

Re: [royale-compiler] branch develop updated: PackageHeaderEmitter: output goog.require() for externs because release builds fail without it

Hi, definitely, needing to add a new library will add overhead, and will turn things more complex and cumbersome without a real need of organization. IMO, we use to break into project libraries for better organization. In this case concrete case (Jewel). both extern classes seems to be more gener

Re: Maven build and URLSearchParams

I have added missing api to missing.js file. I would like to test whether it helped to my application build, but I'm getting the same issue. I have build royale-typedefs and compiler by Maven. What else I should do in order to test stuff before I make any commit ? czw., 27 cze 2019 o 18:41 Alex Ha

Re: Jewel CSS winding up in non-Jewel apps

It looks like JewelJS.swc includes some classes in the SWC that probably shouldn't be there. One example (but there are many more): org.apache.royale.states.State. These are core classes that should be from dependencies, and I suspect that something might be on the library-path instead of the exte

Re: Maven build and URLSearchParams

I think I got it. I was build typedefs without -P main, so it didn't rebuild for me repository fully. wt., 9 lip 2019 o 23:25 Piotr Zarzycki napisał(a): > I have added missing api to missing.js file. I would like to test whether > it helped to my application build, but I'm getting the same issue

Re: Jewel CSS winding up in non-Jewel apps

I have confirmed that these SWCs are defined on the library-path in the compile-js-config.xml used to build JewelJS.swc. Instead, it should be using the external-library-path or js-external-library-path. In compile-swf-config.xml for Jewel.swc, the dependencies are correctly defined on external-li

Re: Tour de Jewel regression in Jewel Alert (release version)

Other typedef SWCs beside js.swc should have .js files in them and the compiler should be picking that up and sending it to the Closure Compiler. However, I think getting missing.js to work will be another level of difficulty because it is part of js.swc. It might be better to create a separate

Re: Maven build and URLSearchParams

I don't think a change to missing.js should be required if it works on Ant. My 2 cents, -Alex On 7/9/19, 2:50 PM, "Piotr Zarzycki" wrote: I think I got it. I was build typedefs without -P main, so it didn't rebuild for me repository fully. wt., 9 lip 2019 o 23:25 Piotr Zarzyck

Re: Maven build and URLSearchParams

I have never tried build any application by ant which uses URLSearchParams and as far as I know we are not using at all that class in our examples. śr., 10 lip 2019 o 00:19 Alex Harui napisał(a): > I don't think a change to missing.js should be required if it works on Ant. > > My 2 cents, > -Ale

Re: Jewel CSS winding up in non-Jewel apps

I'm not sure why Jewel CSS is winding up in non-Jewel apps, but the issue of whether SWC dependencies should be on the library-path or external-library-path isn't so much as a bug (functionality that isn't working as expected) but rather, a problem we've had "forever". With only -library-path a

Re: Maven build and URLSearchParams

I'm pretty sure the Ant build is generating a URLSearchParams.as http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-typedefs/ws/js/target/generated-sources/externc/classes/URLSearchParams.as HTH, -Alex On 7/9/19, 3:21 PM, "Piotr Zarzycki" wrote: I have never tried build any

Re: Jewel CSS winding up in non-Jewel apps

> 3) code that should not be in the output SWC that doesn't support goog.require/goog.provide Is there anything other than a typedef SWC that could be classified as #3? It seems like we have an extra category that doesn't exist in practice, but we're giving it priority over a category that is more

Re: Jewel CSS winding up in non-Jewel apps

Category #1 is when someone intends to combine code from a SWC into another SWC to create one mega-swc, maybe to reduce the number of SWCs or, back in the day, to create one RSL instead of two. I don't think Royale should ever need to do this. Category #2 is the other AS classes from other SWC

Re: Jewel CSS winding up in non-Jewel apps

You know, I just realized... we should start adding the "native" modifier to ActionScript classes in typedef SWCs. Typedef SWCs serve the same purpose as playerglobal/airglobal SWCs, which are also compiled as "native". They all define APIs that will be available at run-time and the SWC should only

Build failed in Jenkins: royale-asjs_MXTests #916

See -- [...truncated 945.19 KB...] [mxmlc] scanning for overrides: ConditionalValue [mxmlc] scanning for overrides: DeviceNames [mxmlc] scanning

Re: Jewel CSS winding up in non-Jewel apps

Good idea. I have this vague memory that there are some other gotchas around using "native", but give it a try and see what happens. -Alex On 7/9/19, 4:21 PM, "Josh Tynjala" wrote: You know, I just realized... we should start adding the "native" modifier to ActionScript classes in ty

Jenkins build is back to normal : royale-asjs_MXTests #917

See

Re: Maven build and URLSearchParams

I would love to know how is this happen... On Wed, Jul 10, 2019, 12:36 AM Alex Harui wrote: > I'm pretty sure the Ant build is generating a URLSearchParams.as > > > http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/royale-typedefs/ws/js/target/generated-sources/externc/classes/URLSearchP