Re: Migration of Adobe Flex to Apache Royale - Support needed

[Alex Harui]

Hi Liju,

The option -load-config=C:/.../royale-config.xml should not be there. 
 Are you specifying that or is that in some default launcher we have?  You'll 
know you have it right when it loads flex-config.xml (because of 
+configname=flex) instead of royale-config.xml

HTH,
-Alex

On 6/10/20, 10:52 PM, "Liju Thomas (OSV)"  
wrote:

Hey Alex,

Yes it is FLEX 3, I updated as per your comment, following error is coming. 
You may check the configuration:

 [echo] *** create 
D:\Work\Clients\FedEx\Apps\WGRT\VCWorkspace\SVN\WGRTFLEX/../WGRTFLEX/WGRTFreightIntegration.swf
 ***
[mxmlc] MXMLJSC
[mxmlc] -compiler.keep-generated-actionscript=false
[mxmlc] -compiler.debug=false
[mxmlc] 
+royalelib=C:/AppData/Roaming/npm/node_modules/@apache-royale/royale-js/frameworks/
[mxmlc] -compiler.actionscript-file-encoding=UTF-8
[mxmlc] -compiler.locale=
[mxmlc] -link-report=D:\/FLEX/../WGRTFLEX/externs.txt
[mxmlc] +configname=flex
[mxmlc] -default-size
[mxmlc] 800
[mxmlc] 1000
[mxmlc] 
-load-config=C:/AppData/Roaming/npm/node_modules/@apache-royale/royale-js/royale-asjs/frameworks/royale-config.xml
[mxmlc] -output=D:FLEX\WGRTFreightIntegration.swf
[mxmlc] --
[mxmlc] D:\FLEX/../WGRTFLEX/src/WGRTFLEX.mxml
[mxmlc] 6.7364493 seconds
[mxmlc] D:\WGRTFLEX\src\WGRTFLEX.mxml(2): col: 1 Error: This 
tag could not be resolved to an ActionScript class. It will be ignored.
[mxmlc]
[mxmlc] https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009data=02%7C01%7Caharui%40adobe.com%7C1461f139655a4a79fce708d80dcb978f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637274515361385816sdata=NaTwt7nmEHAZlKewX1YqGSax8R1hk9WXu1d7CBEWFdI%3Dreserved=0;
 xmlns:mx="library://ns.apache.org/royale/mx"
[mxmlc] ^
[mxmlc]
FLEX.mxml(2): col: 1 Error: This tag could not be resolved to an 
ActionScript class. It will be ignored.
[mxmlc]
[mxmlc] https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009data=02%7C01%7Caharui%40adobe.com%7C1461f139655a4a79fce708d80dcb978f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637274515361385816sdata=NaTwt7nmEHAZlKewX1YqGSax8R1hk9WXu1d7CBEWFdI%3Dreserved=0;
 xmlns:mx="library://ns.apache.org/royale/mx"
[mxmlc] ^
[mxmlc]

Regards,

Liju


From: Alex Harui 
Sent: Thursday, June 11, 2020 11:06 AM
To: dev@royale.apache.org 
Cc: Arya Sankar (OSV) 
Subject: [EXTERNAL] Re: Migration of Adobe Flex to Apache Royale - Support 
needed

Hi Liju,

I posted a reply earlier, but maybe you are having subscription problems.

Are you migrating a Flex 3 application?  If so, then yes, the xmlns have to 
be changed to look like this:

  
xmlns:fx="https://nam04.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009data=02%7C01%7Caharui%40adobe.com%7C1461f139655a4a79fce708d80dcb978f%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C1%7C637274515361395812sdata=DKq3q7smafHdAd%2BULDEMqMocoje8lqIf5DQZAufLwfs%3Dreserved=0;
  xmlns:mx="library://ns.apache.org/royale/mx"

And you may need to add the compiler option: +configname=flex
Note the "+" instead of "-".

HTH,
-Alex

On 6/10/20, 9:13 PM, "Liju Thomas (OSV)" 
 wrote:

Hi Team,

I'm from Development Team for FedEx, we have an application built on 
Adobe Flex, since Flex is not longer supported after Dec 2020, we need to 
migrate the application to Apache Royale asap.

We followed the instruction mentioned in the Migration of Existing 
app however, we are facing some issue:


  1.  I have 

Re: Migration of Adobe Flex to Apache Royale - Support needed

[Liju Thomas (OSV)]

Hey Alex,

Yes it is FLEX 3, I updated as per your comment, following error is coming. You 
may check the configuration:

 [echo] *** create 
D:\Work\Clients\FedEx\Apps\WGRT\VCWorkspace\SVN\WGRTFLEX/../WGRTFLEX/WGRTFreightIntegration.swf
 ***
[mxmlc] MXMLJSC
[mxmlc] -compiler.keep-generated-actionscript=false
[mxmlc] -compiler.debug=false
[mxmlc] 
+royalelib=C:/AppData/Roaming/npm/node_modules/@apache-royale/royale-js/frameworks/
[mxmlc] -compiler.actionscript-file-encoding=UTF-8
[mxmlc] -compiler.locale=
[mxmlc] -link-report=D:\/FLEX/../WGRTFLEX/externs.txt
[mxmlc] +configname=flex
[mxmlc] -default-size
[mxmlc] 800
[mxmlc] 1000
[mxmlc] 
-load-config=C:/AppData/Roaming/npm/node_modules/@apache-royale/royale-js/royale-asjs/frameworks/royale-config.xml
[mxmlc] -output=D:FLEX\WGRTFreightIntegration.swf
[mxmlc] --
[mxmlc] D:\FLEX/../WGRTFLEX/src/WGRTFLEX.mxml
[mxmlc] 6.7364493 seconds
[mxmlc] D:\WGRTFLEX\src\WGRTFLEX.mxml(2): col: 1 Error: This tag 
could not be resolved to an ActionScript class. It will be ignored.
[mxmlc]
[mxmlc] http://ns.adobe.com/mxml/2009; 
xmlns:mx="library://ns.apache.org/royale/mx"
[mxmlc] ^
[mxmlc]
FLEX.mxml(2): col: 1 Error: This tag could not be resolved to an ActionScript 
class. It will be ignored.
[mxmlc]
[mxmlc] http://ns.adobe.com/mxml/2009; 
xmlns:mx="library://ns.apache.org/royale/mx"
[mxmlc] ^
[mxmlc]

Regards,

Liju


From: Alex Harui 
Sent: Thursday, June 11, 2020 11:06 AM
To: dev@royale.apache.org 
Cc: Arya Sankar (OSV) 
Subject: [EXTERNAL] Re: Migration of Adobe Flex to Apache Royale - Support 
needed

Hi Liju,

I posted a reply earlier, but maybe you are having subscription problems.

Are you migrating a Flex 3 application?  If so, then yes, the xmlns have to be 
changed to look like this:

  
xmlns:fx="https://nam03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fns.adobe.com%2Fmxml%2F2009data=02%7C01%7Cliju.thomas.osv%40fedex.com%7C95d62f533f7243b3794308d80dc96b0d%7Cb945c813dce641f884575a12c2fe15bf%7C1%7C1%7C637274506022941972sdata=jkg6T3sfAKJFQX7K9%2BNy5UjXVQXLZB6rc2Czd%2BVpDbQ%3Dreserved=0;
  xmlns:mx="library://ns.apache.org/royale/mx"

And you may need to add the compiler option: +configname=flex
Note the "+" instead of "-".

HTH,
-Alex

On 6/10/20, 9:13 PM, "Liju Thomas (OSV)"  
wrote:

Hi Team,

I'm from Development Team for FedEx, we have an application built on Adobe 
Flex, since Flex is not longer supported after Dec 2020, we need to migrate the 
application to Apache Royale asap.

We followed the instruction mentioned in the Migration of Existing 
app however, we are facing some issue:


  1.  I have 
xmlns:mx="https://nam03.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.adobe.com%2F2006%2Fmxmldata=02%7C01%7Cliju.thomas.osv%40fedex.com%7C95d62f533f7243b3794308d80dc96b0d%7Cb945c813dce641f884575a12c2fe15bf%7C1%7C1%7C637274506022941972sdata=JAJjxp5Sq6Pl%2B9k8PxG4VP3mszmN9eDRjRREDxfORaE%3Dreserved=0;
 in my .MXML but if  I replace the line with 
xmlns:mx="library://ns.apache.org/royale/mx" Compilation fails with following 
error: .mxml(2): col: 1 Error: This tag could not be resolved to an 
ActionScript class. It will be ignored.
[mxmlc]
[mxmlc] 

Re: Migration of Adobe Flex to Apache Royale - Support needed

[Alex Harui]

Hi Liju,

I posted a reply earlier, but maybe you are having subscription problems.

Are you migrating a Flex 3 application?  If so, then yes, the xmlns have to be 
changed to look like this:

  xmlns:fx="http://ns.adobe.com/mxml/2009;
  xmlns:mx="library://ns.apache.org/royale/mx"

And you may need to add the compiler option: +configname=flex
Note the "+" instead of "-".

HTH,
-Alex

On 6/10/20, 9:13 PM, "Liju Thomas (OSV)"  
wrote:

Hi Team,

I'm from Development Team for FedEx, we have an application built on Adobe 
Flex, since Flex is not longer supported after Dec 2020, we need to migrate the 
application to Apache Royale asap.

We followed the instruction mentioned in the Migration of Existing 
app
 however, we are facing some issue:


  1.  I have xmlns:mx="http://www.adobe.com/2006/mxml; in my .MXML but if  
I replace the line with xmlns:mx="library://ns.apache.org/royale/mx" 
Compilation fails with following error: .mxml(2): col: 1 Error: This tag could 
not be resolved to an ActionScript class. It will be ignored.
[mxmlc]
[mxmlc] 

Migration of Adobe Flex to Apache Royale - Support needed

[Liju Thomas (OSV)]

Hi Team,

I'm from Development Team for FedEx, we have an application built on Adobe 
Flex, since Flex is not longer supported after Dec 2020, we need to migrate the 
application to Apache Royale asap.

We followed the instruction mentioned in the Migration of Existing 
app however, we 
are facing some issue:


  1.  I have xmlns:mx="http://www.adobe.com/2006/mxml; in my .MXML but if  I 
replace the line with xmlns:mx="library://ns.apache.org/royale/mx" Compilation 
fails with following error: .mxml(2): col: 1 Error: This tag could not be 
resolved to an ActionScript class. It will be ignored.
[mxmlc]
[mxmlc] 

Migration of Adobe Flex to Apache Royale - Support needed

[Liju Thomas (OSV)]

Hi Team,

I'm from Development Team for FedEx, we have an application built on Adobe 
Flex, since Flex is not longer supported after Dec 2020, we need to migrate the 
application to Apache Royale asap.

We followed the instruction mentioned in the Migration of Existing 
app however, we 
are facing some issue:


  1.  I have xmlns:mx="http://www.adobe.com/2006/mxml; in my .MXML but if  I 
replace the line with xmlns:mx="library://ns.apache.org/royale/mx" Compilation 
fails with following error: .mxml(2): col: 1 Error: This tag could not be 
resolved to an ActionScript class. It will be ignored.
[mxmlc]
[mxmlc] 

Re: MXRoyale layout issues - questions/discussion

[Greg Dove]

Sorry for the radio silence, Alex. I will try to find time to get back into
this tonight my time, if not then it might not be until my weekend (2 days
from now).
I'm using the hack-ish solutions I did for now while I focus on
other things in my current work, but definitely keen to see if we can find
a more general solution.
I think this is important and that it could make a big difference to the
porting process (and to first impressions) for some users. So I will get to
this as soon as I can.

On Tue, Jun 9, 2020 at 2:20 PM Alex Harui  wrote:

> The changes in the ChildResize branch didn't take too long because it only
> hooked up re-layout for width/height changes in children.  It doesn’t have
> the propagation of measurement changes because the test case didn't seem to
> need it.  If you have a scenario where measurement does change then we can
> work on adding the propagation.
>
> Lots of components get an initial measured width/height of 0.  Sometimes
> that's because offsetWidth/Height are 0 at initialization, sometimes it is
> because no content has been assigned yet.  So the 0 trigger is sort of a
> hack to deal with that.  It might go away if we implement the measurement
> change propagation.  The getting of measuredWidth/Height was a way to call
> measure() on demand.  But I think we'll end up shifting to calling
> measure() more often as properties that affect measurement change.  It is
> tempting to have invalidateSize() immediately call measure() and then send
> an event if measurement changes, but I'm concerned that measure() might get
> called too often so we might just have setters call measure and send the
> event.
>
> For the existing code, my thinking was that components where 0 is a valid
> measuredWidth/Height would override the getter and do some other
> computation to return a valid number, including 0.
>
> HTH,
> -Alex
>
> On 6/8/20, 4:57 PM, "Greg Dove"  wrote:
>
> Alex, I found another layout related issue to do with measurement.
>
> measuredWidth and measuredHeight can be zero as valid values. But the
> getters in UIComponent consider <= 0 as a trigger to re-evaluate the
> measurement. I'm assuming that we have the zero value to also
> re-trigger
> calculation (and not just NaN) in js for a specific reason.
> In that case I believe the following needs to be added to the
> measuredWidth
> and measuredHeight getters:
>
> e.g. inside
> public function get measuredHeight():Number
> the part that is like this:
>
> if (child)
>mh = Math.max(mh, child.getExplicitOrMeasuredHeight());
>
>
> should, IMO, be like:
>
>   if (child && child.includeInLayout)
>mh = Math.max(mh, child.getExplicitOrMeasuredHeight());
>
>
> (Likewise, similar for measuredWidth)
>
> This fixes an issue in the app I am porting with containers where all
> children can have includeInLayout=false (and the measured height is
> assigned calculated and assigned as zero at the end of the BoxLayout's
> measure method, but then the getter on the target recalculates with a
> higher measuredHeight because it is still including the children which
> ought to be excluded from the calculation : includeInLayout=false)
>
> I'm tempted to make these changes in MXRoyale, but I don't know if
> others
> may be relying on the current behavior. What do you think?
>
> thanks,
> Greg
>
>
>
> On Tue, Jun 9, 2020 at 8:35 AM Greg Dove  wrote:
>
> > Thanks Alex, that was quick! I will try to find time during my
> > Tuesday-Friday to work on this. Otherwise, if I can't get to it
> then, I can
> > definitely spend time on it during my next weekend.
> >
> >
> > On Mon, Jun 8, 2020 at 8:07 PM Alex Harui 
> > wrote:
> >
> >> I pushed a branch called ChildResize.  It seemed to make the
> example work
> >> much better, without even getting into measure() changes, possibly
> because
> >> the example doesn't really test measurement changes.
> >>
> >> IMO, to handle measurement changes, the measure() logic would
> dispatch
> >> some new event if the measureWidth/Height change.  The BoxLayout
> would be
> >> listening, run its measure(), and dispatch that same event to its
> parent if
> >> it changes, and if it doesn't change, then run layout.  That event
> would be
> >> listened for in the listenToChildren() method I added to BoxLayout.
> >>
> >> There should be a difference between measurement changes and setting
> >> width/height.  If you set width/height on a child, then the child's
> layout
> >> should run.  Assuming layout only runs if width/height change, then
> I think
> >> it shouldn't really matter that much if it runs before or after
> notifying
> >> the parent.  The parent should honor the width/height so the
> child's layout
> >> shouldn't run again.  The child can check isWidthSizedToContent() to
> >> determine if the parent 

Re: Migration of Adobe Flex to Apache Royale - Support needed

[Alex Harui]

Hi Liju,

Are you migrating a Flex 3 application?  If so, then yes, the xmlns have to be 
changed to look like this:

  xmlns:fx="http://ns.adobe.com/mxml/2009; 
  xmlns:mx="library://ns.apache.org/royale/mx"

And you may need to add the compiler option: +configname=flex
Note the "+" instead of "-".

HTH,
-Alex

On 6/10/20, 11:13 AM, "Liju Thomas (OSV)"  
wrote:

Hi Team,

I'm from Development Team for FedEx, we have an application built on Adobe 
Flex, since Flex is not longer supported after Dec 2020, we need to migrate the 
application to Apache Royale asap.

We followed the instruction mentioned in the Migration of Existing 
app
 however, we are facing some issue:


  1.  I have xmlns:mx="http://www.adobe.com/2006/mxml; in my .MXML but if  
I replace the line with xmlns:mx="library://ns.apache.org/royale/mx" 
Compilation fails with following error: .mxml(2): col: 1 Error: This tag could 
not be resolved to an ActionScript class. It will be ignored.
[mxmlc]
[mxmlc] 

Migration of Adobe Flex to Apache Royale - Support needed

[Liju Thomas (OSV)]

Hi Team,

I'm from Development Team for FedEx, we have an application built on Adobe 
Flex, since Flex is not longer supported after Dec 2020, we need to migrate the 
application to Apache Royale asap.

We followed the instruction mentioned in the Migration of Existing 
app however, we 
are facing some issue:


  1.  I have xmlns:mx="http://www.adobe.com/2006/mxml; in my .MXML but if  I 
replace the line with xmlns:mx="library://ns.apache.org/royale/mx" Compilation 
fails with following error: .mxml(2): col: 1 Error: This tag could not be 
resolved to an ActionScript class. It will be ignored.
[mxmlc]
[mxmlc] 

Re: MXRoyale Menu - itemRenderer variation

[Alex Harui]

Pretty sure AdvancedDataGrid supports assignable custom itemrenderers based on 
UIComponent.  Might be a bit more work for Menu/MenuBar as the current 
renderers are not UIComponents.

HTH,
-Alex

On 6/10/20, 1:50 AM, "Greg Dove"  wrote:

Hi - probably another question for Alex, unless Yishay you have something
similar you have faced here:

For mx.controls.Menu :
 specifically for :
set itemRenderer
AFAICS I don't think this is hooked up to take precedence over the default
css IItemRendererFactory for the class, which is picked up in addedToParent.

Do we have other examples I should look at to mirror that, or (based on a
quick check in the Menu code) should I just do a one-time check in
Menu.addedToParent to see if it itemRenderer has already been set and avoid
the load from valuesManager in there, instead adding the explicit
assignment as a bead?

thanks,
Greg

MXRoyale Menu - itemRenderer variation

[Greg Dove]

Hi - probably another question for Alex, unless Yishay you have something
similar you have faced here:

For mx.controls.Menu :
 specifically for :
set itemRenderer
AFAICS I don't think this is hooked up to take precedence over the default
css IItemRendererFactory for the class, which is picked up in addedToParent.

Do we have other examples I should look at to mirror that, or (based on a
quick check in the Menu code) should I just do a one-time check in
Menu.addedToParent to see if it itemRenderer has already been set and avoid
the load from valuesManager in there, instead adding the explicit
assignment as a bead?

thanks,
Greg