Migrating an app from Apache Flex to Apache Royale (tweet thread)

classic Classic list List threaded Threaded
24 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Migrating an app from Apache Flex to Apache Royale (tweet thread)

Carlos Rovira-2
Hi,

just want to share our recent experience migrating an Apache Flex application to Apache Royale.
So I post a thread of 17 tweets here:


Hope the info will be useful :)

Enjoy and don't forget to share if that was useful for you! :)

--
Reply | Threaded
Open this post in threaded view
|

Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

T-san
Carlos,

I have the following mxml. (Skelton only)

Would like to convert to Apache Royale.

Would you please advise me what I shoud do (such as changing the source a
bit for successful conversion)?

I'd like to convert and build 2 or 3 mxml files for assessment, if possible,
within a couple of days.

Appreciate your help in advance.

T-san

----------------------------------------------------------------------------------------------

<?xml version="1.0" encoding="utf-8"?>
<s:NavigatorContent xmlns:fx="http://ns.adobe.com/mxml/2009"
                                        xmlns:s="library://ns.adobe.com/flex/spark"
                                        xmlns:mx="library://ns.adobe.com/flex/mx"
                                        creationComplete="init()"
                                        xmlns:myComp="jp.co.mycomany.flexapp.view.*">
        <fx:Script>
               
        </fx:Script>
        <fx:Style source="myCompany.css"/>

        <s:Scroller width="100%" height="100%">
                <s:Group>
                        <myComp:Header id="headerS"/>
                        <s:Label y="93" width="100%" height="45" fontFamily="Arial" fontSize="30"
                                         horizontalCenter="" text="Tasklist" textAlign="center"
verticalAlign="top"/>
                        <mx:TabNavigator id="taskListTab" x="7" y="141" width="1890" height="888"
change="tabnavigator1_changeHandler(event)" >
                                <myComp:  ???? />
                                <myComp:  ???? />
                                <myComp:  ???? />
                        </mx:TabNavigator>

                        <s:Panel id="myTaskListPanel" x="11" y="609" width="1118" height="411"
backgroundColor="#CCF5FF"
                                         skinClass="jp.co.mycomany.flexapp.view.skin.PanelSkin"
title="myTaskList">
                                <mx:AdvancedDataGrid ?????>
                                        <mx:dataProvider>
                                                <mx:HierarchicalData ?????/>
                                        </mx:dataProvider>
                                        <mx:groupedColumns>
                                                <mx:AdvancedDataGridColumn ??????? />
                                                <mx:AdvancedDataGridColumn ??????? />
                                                <mx:AdvancedDataGridColumn ??????? />
                                                        <mx:itemRenderer>
                                                                <fx:Component>
                                                                        <mx:Label>
                                                                                <fx:Script>


                . . . . . . . . . . . . . . .      
                                         
                        </s:Panel>
                        <s:Button x="1442" y="1037" label="Return" height="26" width="80"
click="returnToMenu()"/>
                </s:Group>
        </s:Scroller>
</s:NavigatorContent>



--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
Reply | Threaded
Open this post in threaded view
|

Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

Carlos Rovira-2
Hi T-San,

I created this content for you in some few minutes, so please, take into account that needs *much* work. But could be a starting point for you:

Some points:

* I based this content in TourDeJewel project, you can remove one of the files content and paste the following.
* TabBar and TabBarContent components works, but still could not finish jewel styles, so looks a bit basic, but could be just what you need for now. Anyway you could create some CSS 
* To make it fast I'm using some data from TDJ like ListModel and some CSS clases that you can find there too
* About AdvancedDataGrid. There's some work on this in MX and Basic, but nothing in Jewel yet. In that point I can't help you so much, but you can ask about that so others could give you some advice
      - Jewel Table is something similar to a DataGrid, but not to ADG, but is not finished and the API need about selectedItem and selectedItemProperty needs to be rewritten, I don't like the actual approach I did.
      - For DataGrids, even in flex, I use to use simple List with ItemRenderers, since most of the time we don't need all things a DataGrid do. So for this reason in this layout I put an HGroup with 2 labels, and a List with an itemrendere with two items. So what I do is to layout and style the HGroup and the two labels to be the "header" and the List with various items to be the "columns". That works pretty good for me. Since I don't know your needs and seems you need some hierarchical data, maybe you'll need to use the basic Tree or something like that. IOW, Jewel still doesn't have DataGrid, ADG and Tree, so you need to use other UI sets for now for that part, or try other more simple ways like the one based in List I commented before but depends on your use case.

HTH
Carlos



<fx:Script>
        <![CDATA[
            import org.apache.royale.collections.ArrayList;
            import vos.TabBarButtonVO;
private function changeHandler(event:Event):void
{
var item:TabBarButtonVO = (event.target as TabBar).selectedItem as TabBarButtonVO;
tabcontent.selectedContent = item.href;
}

private var _tabBarNavigation:ArrayList = new ArrayList([
                new TabBarButtonVO("First", "tab1"),
                new TabBarButtonVO("Second", "tab2"),
                new TabBarButtonVO("Third", "tab3")     
            ]);

            public function get tabBarNavigation():ArrayList
            {
                return _tabBarNavigation;
            }
        ]]>
    </fx:Script>

    <j:model>
        <models:ListsModel id="listModel"/>
    </j:model>

    <j:beads>
        <js:ContainerDataBinding/>
    </j:beads>
    
    <j:Card>
        <html:H3 text="Some Title"/>

        <j:TabBar id="tabbar" className="tabBarIconItemRenderer" change="changeHandler(event)" selectedIndex="0">
            <j:beads>
                <js:ConstantBinding sourcePropertyName="tabBarNavigation" destinationPropertyName="dataProvider"/>
            </j:beads>
        </j:TabBar>

        <j:TabBarContent id="tabcontent" width="100%">
            <j:SectionContent name="tab1" width="100%">
                <j:Card width="100%">
                    <j:HGroup width="100%">
                        <j:Label text="Header 1"/>
                        <j:Label text="Header 2"/>
                    </j:HGroup >
                    <j:List id="iconList" width="100%" height="300"
                            labelField="label" dataProvider="{listModel.iconListData}"
                            className="iconListItemRenderer" />
                </j:Card>
            </j:SectionContent>
            
            <j:SectionContent name="tab2">
                <j:Label text="Content for second tab"/>
            </j:SectionContent>
            
            <j:SectionContent name="tab3">
                <j:Label text="Content for third tab"/>
            </j:SectionContent>
        </j:TabBarContent>
    </j:Card>






El jue., 21 feb. 2019 a las 2:00, T-san (<[hidden email]>) escribió:
Carlos,

I have the following mxml. (Skelton only)

Would like to convert to Apache Royale.

Would you please advise me what I shoud do (such as changing the source a
bit for successful conversion)?

I'd like to convert and build 2 or 3 mxml files for assessment, if possible,
within a couple of days.

Appreciate your help in advance.

T-san

----------------------------------------------------------------------------------------------

<?xml version="1.0" encoding="utf-8"?>
<s:NavigatorContent xmlns:fx="http://ns.adobe.com/mxml/2009"
                                        xmlns:s="library://ns.adobe.com/flex/spark"
                                        xmlns:mx="library://ns.adobe.com/flex/mx"
                                        creationComplete="init()"
                                        xmlns:myComp="jp.co.mycomany.flexapp.view.*">
        <fx:Script>

        </fx:Script>   
        <fx:Style source="myCompany.css"/>

        <s:Scroller width="100%" height="100%">
                <s:Group>
                        <myComp:Header id="headerS"/>
                        <s:Label y="93" width="100%" height="45" fontFamily="Arial" fontSize="30"
                                         horizontalCenter="" text="Tasklist" textAlign="center"
verticalAlign="top"/>
                        <mx:TabNavigator id="taskListTab" x="7" y="141" width="1890" height="888"
change="tabnavigator1_changeHandler(event)" >
                                <myComp:  ???? />
                                <myComp:  ???? />
                                <myComp:  ???? />
                        </mx:TabNavigator>

                        <s:Panel id="myTaskListPanel" x="11" y="609" width="1118" height="411"
backgroundColor="#CCF5FF"
                                         skinClass="jp.co.mycomany.flexapp.view.skin.PanelSkin"
title="myTaskList">
                                <mx:AdvancedDataGrid ?????>
                                        <mx:dataProvider>
                                                <mx:HierarchicalData ?????/>
                                        </mx:dataProvider>
                                        <mx:groupedColumns>
                                                <mx:AdvancedDataGridColumn ??????? />
                                                <mx:AdvancedDataGridColumn ??????? />
                                                <mx:AdvancedDataGridColumn ??????? />
                                                        <mx:itemRenderer>
                                                                <fx:Component>
                                                                        <mx:Label>
                                                                                <fx:Script>


                . . . . . . . . . . . . . . .     

                        </s:Panel>
                        <s:Button x="1442" y="1037" label="Return" height="26" width="80"
click="returnToMenu()"/>
                </s:Group>
        </s:Scroller>
</s:NavigatorContent>



--
Sent from: http://apache-royale-users.20374.n8.nabble.com/


--
Reply | Threaded
Open this post in threaded view
|

Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

T-san
Carlos,

Thanks for your advice and work.

Let me clarify several things.

1. Do I need to convert mx coding to Jewel?
2. If so, is there any useful information on how to do that?
3. Is there user guide available for Jewel?  Or I have to read the Jewel
source to study?

And if you have a time, would you make your sample code complete for build?
I'd also need to know how to build it since at this moment I do not know how
to create pom.xml.

T-san




--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
Reply | Threaded
Open this post in threaded view
|

Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

Carlos Rovira-2


El jue., 21 feb. 2019 a las 13:46, T-san (<[hidden email]>) escribió:
Carlos,

Thanks for your advice and work.

Let me clarify several things.

1. Do I need to convert mx coding to Jewel?

To get a look and feel similar to the one showed in Tour de Jewel yes. Other ready look is MDL library (material design look and feel). MX /Spark are not skinned yet.
 
2. If so, is there any useful information on how to do that?

No. Most of the components names are the same (Button, TextInput, ComboBox, CheckBox,...)
properties too, but with some differences, for example Button doesn't have "label" you must use "text". Most of the uses are in the TDJ project 
 
3. Is there user guide available for Jewel?  Or I have to read the Jewel
source to study?

Still not much docs, mostly the second and this:

 

And if you have a time, would you make your sample code complete for build?

The code I shared is complete and build. I tried before send. You must choose one of the mxml files (i.e: AlertPlayGround.mxml)
remove the code inside the main tag and copy the one here. Then build TDJ as you did before with maven. When go to Alert you could be this initial layout (remember that is just that...initial)
 
I'd also need to know how to build it since at this moment I do not know how
to create pom.xml.

I think you can follow the pom.xml in TDJ. Apache Royale was deigned with maven in mind (not like Apache Flex where maven is not native to the project)
So you can get all knowledge on how to do things from the royale poms

Carlos
 

T-san




--
Sent from: http://apache-royale-users.20374.n8.nabble.com/


--
Reply | Threaded
Open this post in threaded view
|

Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

Alex Harui-2
In reply to this post by T-san
Hi T-San,

There is no single perfect migration strategy for Royale.  You will have to choose a path.

One way to think about migration is that there is your starting point, some amount of work, and an ending point.

Carlos just finished taking a bunch of MXML and AS, rewrote most of the MXML, modified about 30% of the AS, and used the Jewel component set to end up with an app with a very nice looking UI with modern UI components.  If you want a cool new UI because it is time to modernize and older Flex UI, then Jewel is a good choice.

A while ago, Harbs took a bunch of MXML and AS, rewrote most of the MXML, not sure about how much of the AS he changed, but he used Basic set and created a smaller faster application, but I don't think it has as many new UI components.   If you have concerns about size and performance and can spend a bit more time rewriting more code and customizing your UI, then using Basic is a good choice.

A couple of folks that I know of are trying to use the Emulation set.  The goal of the emulation set is to minimize the amount of changes to your MXML and AS.  A fair amount of Tour De Flex has been migrated using the Emulation components.  There is still work to be done, but there were very few changes to the MXML and AS.  All of the changes are in the emulation components.

To me, the emulation components are the charitable way of helping the rest of the folks migrating Flex apps who don't have the time or need for a modernized UI and aren't too concerned about performance.  Because, if you use the emulation set and it doesn't run or look correct, then the fix is to change the code in the emulation compoents and then every other user of those components benefits from that change.  If you choose one of the other options and change your code, then only you benefit from that change.  I wish I could convince more of the other Royale committers to help with the emulation components.  As the clock marches towards 2020, folks will have less and less time to move.

If you choose to go with the emulation components (which has AdvancedDataGrid working to some degree) then you are expected to try to learn how to fix bugs in the emulation components yourself.  In reality, this is true for Jewel and Basic as well, but is especially true for the emulation components because there are a lot more code paths to maintain.

So, think about it, and pick one of the three strategies and let us know what choice you make.  And feel free to ask more questions.

HTH,
-Alex

On 2/21/19, 4:46 AM, "T-san" <[hidden email]> wrote:

    Carlos,
   
    Thanks for your advice and work.
   
    Let me clarify several things.
   
    1. Do I need to convert mx coding to Jewel?
    2. If so, is there any useful information on how to do that?
    3. Is there user guide available for Jewel?  Or I have to read the Jewel
    source to study?
   
    And if you have a time, would you make your sample code complete for build?
    I'd also need to know how to build it since at this moment I do not know how
    to create pom.xml.
   
    T-san
   
   
   
   
    --
    Sent from: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-users.20374.n8.nabble.com%2F&amp;data=02%7C01%7Caharui%40adobe.com%7C73bc5071226444dab0f508d697faa246%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636863500060250570&amp;sdata=NSR584KJpjT2fdd91uv%2BE3AwcAwwww8SdN3nA1LHgys%3D&amp;reserved=0
   

Reply | Threaded
Open this post in threaded view
|

Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

T-san
In reply to this post by Carlos Rovira-2
Carols,

Thanks for your further advice.

<c:ExampleAndSourceCodeTabbedSectionContent
xmlns:fx="http://ns.adobe.com/mxml/2009"
    xmlns:j="library://ns.apache.org/royale/jewel"
    xmlns:html="library://ns.apache.org/royale/html"
    xmlns:js="library://ns.apache.org/royale/basic"
    xmlns:models="models.*"
    xmlns:c="components.*" "sourceCodeUrl=??????.mxml">

I did not include 5th line; including it makes the build success.

I'm studying how to build a specific mxml without using the TourDeJewel's
project structure.

T-San



--
Sent from: http://apache-royale-users.20374.n8.nabble.com/
Reply | Threaded
Open this post in threaded view
|

Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

Carlos Rovira-2
Hi,

you can use SectionContent as Main tag. ExampleAndSourceCodeTabbedSectionContent is a component developed for TDJ to show 2 tabs, one for examples and other for the code in GitHub, so folks can browse the code easily.

sourceCodeUrl is used to point to that file in GitHub

Right now studying TDJ code is the best way to know how to work with Jewel, just notice that Jewel is still in development and some of the pieces are stable while others need more work or rethink at some degree. For the later I expect to have most of the paths stable in the next 3-4 months, but hopefully your could adapt to the changes as I do it. I recommend you to stick with development branches (compiler, typedefs and asjs) and run full builds each day. We already shared scripts that build with maven the three repos and build the SDK for that day with ANT. The scripts are for Windows and Mac.

You're invited to join us on dev and provided patches and contribute vía Pull request too. And be a committer eventually if you get a good knowledge of Royale, and provide good contributions, and you're interested of course

Good luck! :)

Carlos




El vie., 22 feb. 2019 a las 7:06, T-san (<[hidden email]>) escribió:
Carols,

Thanks for your further advice.

<c:ExampleAndSourceCodeTabbedSectionContent
xmlns:fx="http://ns.adobe.com/mxml/2009"
    xmlns:j="library://ns.apache.org/royale/jewel"
    xmlns:html="library://ns.apache.org/royale/html"
    xmlns:js="library://ns.apache.org/royale/basic"
    xmlns:models="models.*"
    xmlns:c="components.*" "sourceCodeUrl=??????.mxml">

I did not include 5th line; including it makes the build success.

I'm studying how to build a specific mxml without using the TourDeJewel's
project structure.

T-San



--
Sent from: http://apache-royale-users.20374.n8.nabble.com/


--
Reply | Threaded
Open this post in threaded view
|

Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

T-san
In reply to this post by Alex Harui-2
Alex,

Thanks a lot for providing me a set of choices to go.
I need some time to decide after doing some benchmark.

I'm interested in modern UI that may make users happy.  And also need to think about minimizing the migration effort to save time and money.   

Where can I find the more detailed information for (1) Basic set migration examples and (2) migration with emulation?

Best rega 
 

On Fri, Feb 22, 2019 at 3:00 PM Alex Harui <[hidden email]> wrote:
Hi T-San,

There is no single perfect migration strategy for Royale.  You will have to choose a path.

One way to think about migration is that there is your starting point, some amount of work, and an ending point.

Carlos just finished taking a bunch of MXML and AS, rewrote most of the MXML, modified about 30% of the AS, and used the Jewel component set to end up with an app with a very nice looking UI with modern UI components.  If you want a cool new UI because it is time to modernize and older Flex UI, then Jewel is a good choice.

A while ago, Harbs took a bunch of MXML and AS, rewrote most of the MXML, not sure about how much of the AS he changed, but he used Basic set and created a smaller faster application, but I don't think it has as many new UI components.   If you have concerns about size and performance and can spend a bit more time rewriting more code and customizing your UI, then using Basic is a good choice.

A couple of folks that I know of are trying to use the Emulation set.  The goal of the emulation set is to minimize the amount of changes to your MXML and AS.  A fair amount of Tour De Flex has been migrated using the Emulation components.  There is still work to be done, but there were very few changes to the MXML and AS.  All of the changes are in the emulation components.

To me, the emulation components are the charitable way of helping the rest of the folks migrating Flex apps who don't have the time or need for a modernized UI and aren't too concerned about performance.  Because, if you use the emulation set and it doesn't run or look correct, then the fix is to change the code in the emulation compoents and then every other user of those components benefits from that change.  If you choose one of the other options and change your code, then only you benefit from that change.  I wish I could convince more of the other Royale committers to help with the emulation components.  As the clock marches towards 2020, folks will have less and less time to move.

If you choose to go with the emulation components (which has AdvancedDataGrid working to some degree) then you are expected to try to learn how to fix bugs in the emulation components yourself.  In reality, this is true for Jewel and Basic as well, but is especially true for the emulation components because there are a lot more code paths to maintain.

So, think about it, and pick one of the three strategies and let us know what choice you make.  And feel free to ask more questions.

HTH,
-Alex

On 2/21/19, 4:46 AM, "T-san" <[hidden email]> wrote:

    Carlos,

    Thanks for your advice and work.

    Let me clarify several things.

    1. Do I need to convert mx coding to Jewel?
    2. If so, is there any useful information on how to do that?
    3. Is there user guide available for Jewel?  Or I have to read the Jewel
    source to study?

    And if you have a time, would you make your sample code complete for build?
    I'd also need to know how to build it since at this moment I do not know how
    to create pom.xml.

    T-san




    --
    Sent from: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-users.20374.n8.nabble.com%2F&amp;data=02%7C01%7Caharui%40adobe.com%7C73bc5071226444dab0f508d697faa246%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636863500060250570&amp;sdata=NSR584KJpjT2fdd91uv%2BE3AwcAwwww8SdN3nA1LHgys%3D&amp;reserved=0




--
Shoichiro Takeshita
武下 祥一郎
Reply | Threaded
Open this post in threaded view
|

Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

Alex Harui-2

Hi,

 

The examples using emulation components are in examples/mxroyale.  The most sophisticated example is a migration of a subset of Tour De Flex.  It is still a work in progress.  The most current version is here: http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/TourDeFlexMigration/lastSuccessfulBuild/artifact/examples/mxroyale/tourdeflexmodules/bin/js-debug/index.html

 

The Flex version it is based on is here:  http://flex.apache.org/tourdeflex/index.html

 

The repos do not contain any serious example of migrating Flex to Basic   The focus of Basic was more about code size and performance than ease of migration.  We did migrate the FlexStore example.  It is in examples/royale/RoyaleStore.  The source it is based on is here: https://github.com/apache/flex-examples/tree/develop/FlexStore  There aren’t any examples running on a server at the moment.  Still, Harbs ported his app to Basic and he can tell you more about it.

 

-Alex

 

From: Takeshita Shoichiro <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Friday, February 22, 2019 at 5:01 PM
To: "[hidden email]" <[hidden email]>
Subject: Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

 

Alex,

 

Thanks a lot for providing me a set of choices to go.

I need some time to decide after doing some benchmark.

 

I'm interested in modern UI that may make users happy.  And also need to think about minimizing the migration effort to save time and money.   

 

Where can I find the more detailed information for (1) Basic set migration examples and (2) migration with emulation?

 

Best rega 

 

 

On Fri, Feb 22, 2019 at 3:00 PM Alex Harui <[hidden email]> wrote:

Hi T-San,

There is no single perfect migration strategy for Royale.  You will have to choose a path.

One way to think about migration is that there is your starting point, some amount of work, and an ending point.

Carlos just finished taking a bunch of MXML and AS, rewrote most of the MXML, modified about 30% of the AS, and used the Jewel component set to end up with an app with a very nice looking UI with modern UI components.  If you want a cool new UI because it is time to modernize and older Flex UI, then Jewel is a good choice.

A while ago, Harbs took a bunch of MXML and AS, rewrote most of the MXML, not sure about how much of the AS he changed, but he used Basic set and created a smaller faster application, but I don't think it has as many new UI components.   If you have concerns about size and performance and can spend a bit more time rewriting more code and customizing your UI, then using Basic is a good choice.

A couple of folks that I know of are trying to use the Emulation set.  The goal of the emulation set is to minimize the amount of changes to your MXML and AS.  A fair amount of Tour De Flex has been migrated using the Emulation components.  There is still work to be done, but there were very few changes to the MXML and AS.  All of the changes are in the emulation components.

To me, the emulation components are the charitable way of helping the rest of the folks migrating Flex apps who don't have the time or need for a modernized UI and aren't too concerned about performance.  Because, if you use the emulation set and it doesn't run or look correct, then the fix is to change the code in the emulation compoents and then every other user of those components benefits from that change.  If you choose one of the other options and change your code, then only you benefit from that change.  I wish I could convince more of the other Royale committers to help with the emulation components.  As the clock marches towards 2020, folks will have less and less time to move.

If you choose to go with the emulation components (which has AdvancedDataGrid working to some degree) then you are expected to try to learn how to fix bugs in the emulation components yourself.  In reality, this is true for Jewel and Basic as well, but is especially true for the emulation components because there are a lot more code paths to maintain.

So, think about it, and pick one of the three strategies and let us know what choice you make.  And feel free to ask more questions.

HTH,
-Alex

On 2/21/19, 4:46 AM, "T-san" <[hidden email]> wrote:

    Carlos,

    Thanks for your advice and work.

    Let me clarify several things.

    1. Do I need to convert mx coding to Jewel?
    2. If so, is there any useful information on how to do that?
    3. Is there user guide available for Jewel?  Or I have to read the Jewel
    source to study?

    And if you have a time, would you make your sample code complete for build?
    I'd also need to know how to build it since at this moment I do not know how
    to create pom.xml.

    T-san




    --
    Sent from: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-users.20374.n8.nabble.com%2F&amp;data=02%7C01%7Caharui%40adobe.com%7C73bc5071226444dab0f508d697faa246%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636863500060250570&amp;sdata=NSR584KJpjT2fdd91uv%2BE3AwcAwwww8SdN3nA1LHgys%3D&amp;reserved=0


 

--

Shoichiro Takeshita
武下 祥一郎

Reply | Threaded
Open this post in threaded view
|

Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

T-san
Alex, thanks for the link information.

I understand Flash version takes more time for loading SWF than new Apache Royale.  Is my observation correct?

It seems what I'm looking for is the Advanced Data Grid.  It seems not implemented in Royale yet.  

But anyway, the progress seems to be great.

T-san

On Sat, Feb 23, 2019 at 2:28 PM Alex Harui <[hidden email]> wrote:

Hi,

 

The examples using emulation components are in examples/mxroyale.  The most sophisticated example is a migration of a subset of Tour De Flex.  It is still a work in progress.  The most current version is here: http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/TourDeFlexMigration/lastSuccessfulBuild/artifact/examples/mxroyale/tourdeflexmodules/bin/js-debug/index.html

 

The Flex version it is based on is here:  http://flex.apache.org/tourdeflex/index.html

 

The repos do not contain any serious example of migrating Flex to Basic   The focus of Basic was more about code size and performance than ease of migration.  We did migrate the FlexStore example.  It is in examples/royale/RoyaleStore.  The source it is based on is here: https://github.com/apache/flex-examples/tree/develop/FlexStore  There aren’t any examples running on a server at the moment.  Still, Harbs ported his app to Basic and he can tell you more about it.

 

-Alex

 

From: Takeshita Shoichiro <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Friday, February 22, 2019 at 5:01 PM
To: "[hidden email]" <[hidden email]>
Subject: Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

 

Alex,

 

Thanks a lot for providing me a set of choices to go.

I need some time to decide after doing some benchmark.

 

I'm interested in modern UI that may make users happy.  And also need to think about minimizing the migration effort to save time and money.   

 

Where can I find the more detailed information for (1) Basic set migration examples and (2) migration with emulation?

 

Best rega 

 

 

On Fri, Feb 22, 2019 at 3:00 PM Alex Harui <[hidden email]> wrote:

Hi T-San,

There is no single perfect migration strategy for Royale.  You will have to choose a path.

One way to think about migration is that there is your starting point, some amount of work, and an ending point.

Carlos just finished taking a bunch of MXML and AS, rewrote most of the MXML, modified about 30% of the AS, and used the Jewel component set to end up with an app with a very nice looking UI with modern UI components.  If you want a cool new UI because it is time to modernize and older Flex UI, then Jewel is a good choice.

A while ago, Harbs took a bunch of MXML and AS, rewrote most of the MXML, not sure about how much of the AS he changed, but he used Basic set and created a smaller faster application, but I don't think it has as many new UI components.   If you have concerns about size and performance and can spend a bit more time rewriting more code and customizing your UI, then using Basic is a good choice.

A couple of folks that I know of are trying to use the Emulation set.  The goal of the emulation set is to minimize the amount of changes to your MXML and AS.  A fair amount of Tour De Flex has been migrated using the Emulation components.  There is still work to be done, but there were very few changes to the MXML and AS.  All of the changes are in the emulation components.

To me, the emulation components are the charitable way of helping the rest of the folks migrating Flex apps who don't have the time or need for a modernized UI and aren't too concerned about performance.  Because, if you use the emulation set and it doesn't run or look correct, then the fix is to change the code in the emulation compoents and then every other user of those components benefits from that change.  If you choose one of the other options and change your code, then only you benefit from that change.  I wish I could convince more of the other Royale committers to help with the emulation components.  As the clock marches towards 2020, folks will have less and less time to move.

If you choose to go with the emulation components (which has AdvancedDataGrid working to some degree) then you are expected to try to learn how to fix bugs in the emulation components yourself.  In reality, this is true for Jewel and Basic as well, but is especially true for the emulation components because there are a lot more code paths to maintain.

So, think about it, and pick one of the three strategies and let us know what choice you make.  And feel free to ask more questions.

HTH,
-Alex

On 2/21/19, 4:46 AM, "T-san" <[hidden email]> wrote:

    Carlos,

    Thanks for your advice and work.

    Let me clarify several things.

    1. Do I need to convert mx coding to Jewel?
    2. If so, is there any useful information on how to do that?
    3. Is there user guide available for Jewel?  Or I have to read the Jewel
    source to study?

    And if you have a time, would you make your sample code complete for build?
    I'd also need to know how to build it since at this moment I do not know how
    to create pom.xml.

    T-san




    --
    Sent from: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-users.20374.n8.nabble.com%2F&amp;data=02%7C01%7Caharui%40adobe.com%7C73bc5071226444dab0f508d697faa246%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636863500060250570&amp;sdata=NSR584KJpjT2fdd91uv%2BE3AwcAwwww8SdN3nA1LHgys%3D&amp;reserved=0


 

--

Shoichiro Takeshita
武下 祥一郎



--
Shoichiro Takeshita
武下 祥一郎
Reply | Threaded
Open this post in threaded view
|

Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

Alex Harui-2

Hi, Takeshita-san,

 

For these examples, I also think the Royale version loads faster.  It makes some sense, especially from a clean cache, as the browser has to load the player (essentially, downloading and starting an application), then load and parse the SWF, then run it.  The browser running a Royale app has to load a pile of JS and CSS files, but the browsers have been optimizing that over the past years.

 

To see the Advanced DataGrid in the Royale migration of Tour De Flex, first click on “MX Framework” then “Data Visualization”, then “AdvancedDataGrid” and then on the “AdvancedDataGrid” that appears as a child of the first one.  It should show an AdvancedDataGrid with a GroupingCollection.

 

HTH,

-Alex

 

From: Takeshita Shoichiro <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Friday, February 22, 2019 at 10:04 PM
To: "[hidden email]" <[hidden email]>
Subject: Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

 

Alex, thanks for the link information.

 

I understand Flash version takes more time for loading SWF than new Apache Royale.  Is my observation correct?

 

It seems what I'm looking for is the Advanced Data Grid.  It seems not implemented in Royale yet.  

 

But anyway, the progress seems to be great.

 

T-san

 

On Sat, Feb 23, 2019 at 2:28 PM Alex Harui <[hidden email]> wrote:

Hi,

 

The examples using emulation components are in examples/mxroyale.  The most sophisticated example is a migration of a subset of Tour De Flex.  It is still a work in progress.  The most current version is here: http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/TourDeFlexMigration/lastSuccessfulBuild/artifact/examples/mxroyale/tourdeflexmodules/bin/js-debug/index.html

 

The Flex version it is based on is here:  http://flex.apache.org/tourdeflex/index.html

 

The repos do not contain any serious example of migrating Flex to Basic   The focus of Basic was more about code size and performance than ease of migration.  We did migrate the FlexStore example.  It is in examples/royale/RoyaleStore.  The source it is based on is here: https://github.com/apache/flex-examples/tree/develop/FlexStore  There aren’t any examples running on a server at the moment.  Still, Harbs ported his app to Basic and he can tell you more about it.

 

-Alex

 

From: Takeshita Shoichiro <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Friday, February 22, 2019 at 5:01 PM
To: "[hidden email]" <[hidden email]>
Subject: Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

 

Alex,

 

Thanks a lot for providing me a set of choices to go.

I need some time to decide after doing some benchmark.

 

I'm interested in modern UI that may make users happy.  And also need to think about minimizing the migration effort to save time and money.   

 

Where can I find the more detailed information for (1) Basic set migration examples and (2) migration with emulation?

 

Best rega 

 

 

On Fri, Feb 22, 2019 at 3:00 PM Alex Harui <[hidden email]> wrote:

Hi T-San,

There is no single perfect migration strategy for Royale.  You will have to choose a path.

One way to think about migration is that there is your starting point, some amount of work, and an ending point.

Carlos just finished taking a bunch of MXML and AS, rewrote most of the MXML, modified about 30% of the AS, and used the Jewel component set to end up with an app with a very nice looking UI with modern UI components.  If you want a cool new UI because it is time to modernize and older Flex UI, then Jewel is a good choice.

A while ago, Harbs took a bunch of MXML and AS, rewrote most of the MXML, not sure about how much of the AS he changed, but he used Basic set and created a smaller faster application, but I don't think it has as many new UI components.   If you have concerns about size and performance and can spend a bit more time rewriting more code and customizing your UI, then using Basic is a good choice.

A couple of folks that I know of are trying to use the Emulation set.  The goal of the emulation set is to minimize the amount of changes to your MXML and AS.  A fair amount of Tour De Flex has been migrated using the Emulation components.  There is still work to be done, but there were very few changes to the MXML and AS.  All of the changes are in the emulation components.

To me, the emulation components are the charitable way of helping the rest of the folks migrating Flex apps who don't have the time or need for a modernized UI and aren't too concerned about performance.  Because, if you use the emulation set and it doesn't run or look correct, then the fix is to change the code in the emulation compoents and then every other user of those components benefits from that change.  If you choose one of the other options and change your code, then only you benefit from that change.  I wish I could convince more of the other Royale committers to help with the emulation components.  As the clock marches towards 2020, folks will have less and less time to move.

If you choose to go with the emulation components (which has AdvancedDataGrid working to some degree) then you are expected to try to learn how to fix bugs in the emulation components yourself.  In reality, this is true for Jewel and Basic as well, but is especially true for the emulation components because there are a lot more code paths to maintain.

So, think about it, and pick one of the three strategies and let us know what choice you make.  And feel free to ask more questions.

HTH,
-Alex

On 2/21/19, 4:46 AM, "T-san" <[hidden email]> wrote:

    Carlos,

    Thanks for your advice and work.

    Let me clarify several things.

    1. Do I need to convert mx coding to Jewel?
    2. If so, is there any useful information on how to do that?
    3. Is there user guide available for Jewel?  Or I have to read the Jewel
    source to study?

    And if you have a time, would you make your sample code complete for build?
    I'd also need to know how to build it since at this moment I do not know how
    to create pom.xml.

    T-san




    --
    Sent from: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-users.20374.n8.nabble.com%2F&amp;data=02%7C01%7Caharui%40adobe.com%7C73bc5071226444dab0f508d697faa246%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636863500060250570&amp;sdata=NSR584KJpjT2fdd91uv%2BE3AwcAwwww8SdN3nA1LHgys%3D&amp;reserved=0


 

--

Shoichiro Takeshita
武下 祥一郎


 

--

Shoichiro Takeshita
武下 祥一郎

Reply | Threaded
Open this post in threaded view
|

Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

T-san
Alex, got it. Cool.

I would like to try conversion of our mxml using this emulation approach.
To do that, how I can?  Appreciate your help.

Thank you, S. Takeshita  


On Sat, Feb 23, 2019 at 3:09 PM Alex Harui <[hidden email]> wrote:

Hi, Takeshita-san,

 

For these examples, I also think the Royale version loads faster.  It makes some sense, especially from a clean cache, as the browser has to load the player (essentially, downloading and starting an application), then load and parse the SWF, then run it.  The browser running a Royale app has to load a pile of JS and CSS files, but the browsers have been optimizing that over the past years.

 

To see the Advanced DataGrid in the Royale migration of Tour De Flex, first click on “MX Framework” then “Data Visualization”, then “AdvancedDataGrid” and then on the “AdvancedDataGrid” that appears as a child of the first one.  It should show an AdvancedDataGrid with a GroupingCollection.

 

HTH,

-Alex

 

From: Takeshita Shoichiro <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Friday, February 22, 2019 at 10:04 PM
To: "[hidden email]" <[hidden email]>
Subject: Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

 

Alex, thanks for the link information.

 

I understand Flash version takes more time for loading SWF than new Apache Royale.  Is my observation correct?

 

It seems what I'm looking for is the Advanced Data Grid.  It seems not implemented in Royale yet.  

 

But anyway, the progress seems to be great.

 

T-san

 

On Sat, Feb 23, 2019 at 2:28 PM Alex Harui <[hidden email]> wrote:

Hi,

 

The examples using emulation components are in examples/mxroyale.  The most sophisticated example is a migration of a subset of Tour De Flex.  It is still a work in progress.  The most current version is here: http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/TourDeFlexMigration/lastSuccessfulBuild/artifact/examples/mxroyale/tourdeflexmodules/bin/js-debug/index.html

 

The Flex version it is based on is here:  http://flex.apache.org/tourdeflex/index.html

 

The repos do not contain any serious example of migrating Flex to Basic   The focus of Basic was more about code size and performance than ease of migration.  We did migrate the FlexStore example.  It is in examples/royale/RoyaleStore.  The source it is based on is here: https://github.com/apache/flex-examples/tree/develop/FlexStore  There aren’t any examples running on a server at the moment.  Still, Harbs ported his app to Basic and he can tell you more about it.

 

-Alex

 

From: Takeshita Shoichiro <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Friday, February 22, 2019 at 5:01 PM
To: "[hidden email]" <[hidden email]>
Subject: Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

 

Alex,

 

Thanks a lot for providing me a set of choices to go.

I need some time to decide after doing some benchmark.

 

I'm interested in modern UI that may make users happy.  And also need to think about minimizing the migration effort to save time and money.   

 

Where can I find the more detailed information for (1) Basic set migration examples and (2) migration with emulation?

 

Best rega 

 

 

On Fri, Feb 22, 2019 at 3:00 PM Alex Harui <[hidden email]> wrote:

Hi T-San,

There is no single perfect migration strategy for Royale.  You will have to choose a path.

One way to think about migration is that there is your starting point, some amount of work, and an ending point.

Carlos just finished taking a bunch of MXML and AS, rewrote most of the MXML, modified about 30% of the AS, and used the Jewel component set to end up with an app with a very nice looking UI with modern UI components.  If you want a cool new UI because it is time to modernize and older Flex UI, then Jewel is a good choice.

A while ago, Harbs took a bunch of MXML and AS, rewrote most of the MXML, not sure about how much of the AS he changed, but he used Basic set and created a smaller faster application, but I don't think it has as many new UI components.   If you have concerns about size and performance and can spend a bit more time rewriting more code and customizing your UI, then using Basic is a good choice.

A couple of folks that I know of are trying to use the Emulation set.  The goal of the emulation set is to minimize the amount of changes to your MXML and AS.  A fair amount of Tour De Flex has been migrated using the Emulation components.  There is still work to be done, but there were very few changes to the MXML and AS.  All of the changes are in the emulation components.

To me, the emulation components are the charitable way of helping the rest of the folks migrating Flex apps who don't have the time or need for a modernized UI and aren't too concerned about performance.  Because, if you use the emulation set and it doesn't run or look correct, then the fix is to change the code in the emulation compoents and then every other user of those components benefits from that change.  If you choose one of the other options and change your code, then only you benefit from that change.  I wish I could convince more of the other Royale committers to help with the emulation components.  As the clock marches towards 2020, folks will have less and less time to move.

If you choose to go with the emulation components (which has AdvancedDataGrid working to some degree) then you are expected to try to learn how to fix bugs in the emulation components yourself.  In reality, this is true for Jewel and Basic as well, but is especially true for the emulation components because there are a lot more code paths to maintain.

So, think about it, and pick one of the three strategies and let us know what choice you make.  And feel free to ask more questions.

HTH,
-Alex

On 2/21/19, 4:46 AM, "T-san" <[hidden email]> wrote:

    Carlos,

    Thanks for your advice and work.

    Let me clarify several things.

    1. Do I need to convert mx coding to Jewel?
    2. If so, is there any useful information on how to do that?
    3. Is there user guide available for Jewel?  Or I have to read the Jewel
    source to study?

    And if you have a time, would you make your sample code complete for build?
    I'd also need to know how to build it since at this moment I do not know how
    to create pom.xml.

    T-san




    --
    Sent from: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-users.20374.n8.nabble.com%2F&amp;data=02%7C01%7Caharui%40adobe.com%7C73bc5071226444dab0f508d697faa246%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636863500060250570&amp;sdata=NSR584KJpjT2fdd91uv%2BE3AwcAwwww8SdN3nA1LHgys%3D&amp;reserved=0


 

--

Shoichiro Takeshita
武下 祥一郎


 

--

Shoichiro Takeshita
武下 祥一郎



--
Shoichiro Takeshita
武下 祥一郎
Reply | Threaded
Open this post in threaded view
|

Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

Alex Harui-2

First, lower your expectations 😉

 

Then, make a copy of your code.

And read this:  https://apache.github.io/royale-docs/create-an-application/migrate-an-existing-app/migrate-from-flex.html

 

Good luck.  I’m about to stop work for today as I am on the road in the middle of the US.  I’ll be back on the west coast of the US in about 24 hours.

 

Thanks,

-Alex

 

From: Takeshita Shoichiro <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Friday, February 22, 2019 at 10:22 PM
To: "[hidden email]" <[hidden email]>
Subject: Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

 

Alex, got it. Cool.

 

I would like to try conversion of our mxml using this emulation approach.

To do that, how I can?  Appreciate your help.

 

Thank you, S. Takeshita  

 

 

On Sat, Feb 23, 2019 at 3:09 PM Alex Harui <[hidden email]> wrote:

Hi, Takeshita-san,

 

For these examples, I also think the Royale version loads faster.  It makes some sense, especially from a clean cache, as the browser has to load the player (essentially, downloading and starting an application), then load and parse the SWF, then run it.  The browser running a Royale app has to load a pile of JS and CSS files, but the browsers have been optimizing that over the past years.

 

To see the Advanced DataGrid in the Royale migration of Tour De Flex, first click on “MX Framework” then “Data Visualization”, then “AdvancedDataGrid” and then on the “AdvancedDataGrid” that appears as a child of the first one.  It should show an AdvancedDataGrid with a GroupingCollection.

 

HTH,

-Alex

 

From: Takeshita Shoichiro <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Friday, February 22, 2019 at 10:04 PM
To: "[hidden email]" <[hidden email]>
Subject: Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

 

Alex, thanks for the link information.

 

I understand Flash version takes more time for loading SWF than new Apache Royale.  Is my observation correct?

 

It seems what I'm looking for is the Advanced Data Grid.  It seems not implemented in Royale yet.  

 

But anyway, the progress seems to be great.

 

T-san

 

On Sat, Feb 23, 2019 at 2:28 PM Alex Harui <[hidden email]> wrote:

Hi,

 

The examples using emulation components are in examples/mxroyale.  The most sophisticated example is a migration of a subset of Tour De Flex.  It is still a work in progress.  The most current version is here: http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/TourDeFlexMigration/lastSuccessfulBuild/artifact/examples/mxroyale/tourdeflexmodules/bin/js-debug/index.html

 

The Flex version it is based on is here:  http://flex.apache.org/tourdeflex/index.html

 

The repos do not contain any serious example of migrating Flex to Basic   The focus of Basic was more about code size and performance than ease of migration.  We did migrate the FlexStore example.  It is in examples/royale/RoyaleStore.  The source it is based on is here: https://github.com/apache/flex-examples/tree/develop/FlexStore  There aren’t any examples running on a server at the moment.  Still, Harbs ported his app to Basic and he can tell you more about it.

 

-Alex

 

From: Takeshita Shoichiro <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Friday, February 22, 2019 at 5:01 PM
To: "[hidden email]" <[hidden email]>
Subject: Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

 

Alex,

 

Thanks a lot for providing me a set of choices to go.

I need some time to decide after doing some benchmark.

 

I'm interested in modern UI that may make users happy.  And also need to think about minimizing the migration effort to save time and money.   

 

Where can I find the more detailed information for (1) Basic set migration examples and (2) migration with emulation?

 

Best rega 

 

 

On Fri, Feb 22, 2019 at 3:00 PM Alex Harui <[hidden email]> wrote:

Hi T-San,

There is no single perfect migration strategy for Royale.  You will have to choose a path.

One way to think about migration is that there is your starting point, some amount of work, and an ending point.

Carlos just finished taking a bunch of MXML and AS, rewrote most of the MXML, modified about 30% of the AS, and used the Jewel component set to end up with an app with a very nice looking UI with modern UI components.  If you want a cool new UI because it is time to modernize and older Flex UI, then Jewel is a good choice.

A while ago, Harbs took a bunch of MXML and AS, rewrote most of the MXML, not sure about how much of the AS he changed, but he used Basic set and created a smaller faster application, but I don't think it has as many new UI components.   If you have concerns about size and performance and can spend a bit more time rewriting more code and customizing your UI, then using Basic is a good choice.

A couple of folks that I know of are trying to use the Emulation set.  The goal of the emulation set is to minimize the amount of changes to your MXML and AS.  A fair amount of Tour De Flex has been migrated using the Emulation components.  There is still work to be done, but there were very few changes to the MXML and AS.  All of the changes are in the emulation components.

To me, the emulation components are the charitable way of helping the rest of the folks migrating Flex apps who don't have the time or need for a modernized UI and aren't too concerned about performance.  Because, if you use the emulation set and it doesn't run or look correct, then the fix is to change the code in the emulation compoents and then every other user of those components benefits from that change.  If you choose one of the other options and change your code, then only you benefit from that change.  I wish I could convince more of the other Royale committers to help with the emulation components.  As the clock marches towards 2020, folks will have less and less time to move.

If you choose to go with the emulation components (which has AdvancedDataGrid working to some degree) then you are expected to try to learn how to fix bugs in the emulation components yourself.  In reality, this is true for Jewel and Basic as well, but is especially true for the emulation components because there are a lot more code paths to maintain.

So, think about it, and pick one of the three strategies and let us know what choice you make.  And feel free to ask more questions.

HTH,
-Alex

On 2/21/19, 4:46 AM, "T-san" <[hidden email]> wrote:

    Carlos,

    Thanks for your advice and work.

    Let me clarify several things.

    1. Do I need to convert mx coding to Jewel?
    2. If so, is there any useful information on how to do that?
    3. Is there user guide available for Jewel?  Or I have to read the Jewel
    source to study?

    And if you have a time, would you make your sample code complete for build?
    I'd also need to know how to build it since at this moment I do not know how
    to create pom.xml.

    T-san




    --
    Sent from: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-users.20374.n8.nabble.com%2F&amp;data=02%7C01%7Caharui%40adobe.com%7C73bc5071226444dab0f508d697faa246%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636863500060250570&amp;sdata=NSR584KJpjT2fdd91uv%2BE3AwcAwwww8SdN3nA1LHgys%3D&amp;reserved=0


 

--

Shoichiro Takeshita
武下 祥一郎


 

--

Shoichiro Takeshita
武下 祥一郎


 

--

Shoichiro Takeshita
武下 祥一郎

Reply | Threaded
Open this post in threaded view
|

Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

T-san
Alex, 

I tried to build tourdeflexmodules (incl. AdvancedDataGridExample.mxml) but seemed fail.  (no result)

Under the following directory, I ran mvn clean install.

\royale-asjs\royale-asjs\examples\mxroyale

Did I use the wrong procedure?

Appreciate your advice.

Best regards,

S. Takeshita

On Sat, Feb 23, 2019 at 3:33 PM Alex Harui <[hidden email]> wrote:

First, lower your expectations 😉

 

Then, make a copy of your code.

And read this:  https://apache.github.io/royale-docs/create-an-application/migrate-an-existing-app/migrate-from-flex.html

 

Good luck.  I’m about to stop work for today as I am on the road in the middle of the US.  I’ll be back on the west coast of the US in about 24 hours.

 

Thanks,

-Alex

 

From: Takeshita Shoichiro <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Friday, February 22, 2019 at 10:22 PM
To: "[hidden email]" <[hidden email]>
Subject: Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

 

Alex, got it. Cool.

 

I would like to try conversion of our mxml using this emulation approach.

To do that, how I can?  Appreciate your help.

 

Thank you, S. Takeshita  

 

 

On Sat, Feb 23, 2019 at 3:09 PM Alex Harui <[hidden email]> wrote:

Hi, Takeshita-san,

 

For these examples, I also think the Royale version loads faster.  It makes some sense, especially from a clean cache, as the browser has to load the player (essentially, downloading and starting an application), then load and parse the SWF, then run it.  The browser running a Royale app has to load a pile of JS and CSS files, but the browsers have been optimizing that over the past years.

 

To see the Advanced DataGrid in the Royale migration of Tour De Flex, first click on “MX Framework” then “Data Visualization”, then “AdvancedDataGrid” and then on the “AdvancedDataGrid” that appears as a child of the first one.  It should show an AdvancedDataGrid with a GroupingCollection.

 

HTH,

-Alex

 

From: Takeshita Shoichiro <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Friday, February 22, 2019 at 10:04 PM
To: "[hidden email]" <[hidden email]>
Subject: Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

 

Alex, thanks for the link information.

 

I understand Flash version takes more time for loading SWF than new Apache Royale.  Is my observation correct?

 

It seems what I'm looking for is the Advanced Data Grid.  It seems not implemented in Royale yet.  

 

But anyway, the progress seems to be great.

 

T-san

 

On Sat, Feb 23, 2019 at 2:28 PM Alex Harui <[hidden email]> wrote:

Hi,

 

The examples using emulation components are in examples/mxroyale.  The most sophisticated example is a migration of a subset of Tour De Flex.  It is still a work in progress.  The most current version is here: http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/TourDeFlexMigration/lastSuccessfulBuild/artifact/examples/mxroyale/tourdeflexmodules/bin/js-debug/index.html

 

The Flex version it is based on is here:  http://flex.apache.org/tourdeflex/index.html

 

The repos do not contain any serious example of migrating Flex to Basic   The focus of Basic was more about code size and performance than ease of migration.  We did migrate the FlexStore example.  It is in examples/royale/RoyaleStore.  The source it is based on is here: https://github.com/apache/flex-examples/tree/develop/FlexStore  There aren’t any examples running on a server at the moment.  Still, Harbs ported his app to Basic and he can tell you more about it.

 

-Alex

 

From: Takeshita Shoichiro <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Friday, February 22, 2019 at 5:01 PM
To: "[hidden email]" <[hidden email]>
Subject: Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

 

Alex,

 

Thanks a lot for providing me a set of choices to go.

I need some time to decide after doing some benchmark.

 

I'm interested in modern UI that may make users happy.  And also need to think about minimizing the migration effort to save time and money.   

 

Where can I find the more detailed information for (1) Basic set migration examples and (2) migration with emulation?

 

Best rega 

 

 

On Fri, Feb 22, 2019 at 3:00 PM Alex Harui <[hidden email]> wrote:

Hi T-San,

There is no single perfect migration strategy for Royale.  You will have to choose a path.

One way to think about migration is that there is your starting point, some amount of work, and an ending point.

Carlos just finished taking a bunch of MXML and AS, rewrote most of the MXML, modified about 30% of the AS, and used the Jewel component set to end up with an app with a very nice looking UI with modern UI components.  If you want a cool new UI because it is time to modernize and older Flex UI, then Jewel is a good choice.

A while ago, Harbs took a bunch of MXML and AS, rewrote most of the MXML, not sure about how much of the AS he changed, but he used Basic set and created a smaller faster application, but I don't think it has as many new UI components.   If you have concerns about size and performance and can spend a bit more time rewriting more code and customizing your UI, then using Basic is a good choice.

A couple of folks that I know of are trying to use the Emulation set.  The goal of the emulation set is to minimize the amount of changes to your MXML and AS.  A fair amount of Tour De Flex has been migrated using the Emulation components.  There is still work to be done, but there were very few changes to the MXML and AS.  All of the changes are in the emulation components.

To me, the emulation components are the charitable way of helping the rest of the folks migrating Flex apps who don't have the time or need for a modernized UI and aren't too concerned about performance.  Because, if you use the emulation set and it doesn't run or look correct, then the fix is to change the code in the emulation compoents and then every other user of those components benefits from that change.  If you choose one of the other options and change your code, then only you benefit from that change.  I wish I could convince more of the other Royale committers to help with the emulation components.  As the clock marches towards 2020, folks will have less and less time to move.

If you choose to go with the emulation components (which has AdvancedDataGrid working to some degree) then you are expected to try to learn how to fix bugs in the emulation components yourself.  In reality, this is true for Jewel and Basic as well, but is especially true for the emulation components because there are a lot more code paths to maintain.

So, think about it, and pick one of the three strategies and let us know what choice you make.  And feel free to ask more questions.

HTH,
-Alex

On 2/21/19, 4:46 AM, "T-san" <[hidden email]> wrote:

    Carlos,

    Thanks for your advice and work.

    Let me clarify several things.

    1. Do I need to convert mx coding to Jewel?
    2. If so, is there any useful information on how to do that?
    3. Is there user guide available for Jewel?  Or I have to read the Jewel
    source to study?

    And if you have a time, would you make your sample code complete for build?
    I'd also need to know how to build it since at this moment I do not know how
    to create pom.xml.

    T-san




    --
    Sent from: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-users.20374.n8.nabble.com%2F&amp;data=02%7C01%7Caharui%40adobe.com%7C73bc5071226444dab0f508d697faa246%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636863500060250570&amp;sdata=NSR584KJpjT2fdd91uv%2BE3AwcAwwww8SdN3nA1LHgys%3D&amp;reserved=0


 

--

Shoichiro Takeshita
武下 祥一郎


 

--

Shoichiro Takeshita
武下 祥一郎


 

--

Shoichiro Takeshita
武下 祥一郎



--
Shoichiro Takeshita
武下 祥一郎
Reply | Threaded
Open this post in threaded view
|

Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

Piotr Zarzycki
I'm not sure whether Maven build working for that example. Ant for sure. 

Thanks,
Piotr

On Sun, Feb 24, 2019, 11:29 AM Takeshita Shoichiro <[hidden email]> wrote:
Alex, 

I tried to build tourdeflexmodules (incl. AdvancedDataGridExample.mxml) but seemed fail.  (no result)

Under the following directory, I ran mvn clean install.

\royale-asjs\royale-asjs\examples\mxroyale

Did I use the wrong procedure?

Appreciate your advice.

Best regards,

S. Takeshita

On Sat, Feb 23, 2019 at 3:33 PM Alex Harui <[hidden email]> wrote:

First, lower your expectations 😉

 

Then, make a copy of your code.

And read this:  https://apache.github.io/royale-docs/create-an-application/migrate-an-existing-app/migrate-from-flex.html

 

Good luck.  I’m about to stop work for today as I am on the road in the middle of the US.  I’ll be back on the west coast of the US in about 24 hours.

 

Thanks,

-Alex

 

From: Takeshita Shoichiro <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Friday, February 22, 2019 at 10:22 PM
To: "[hidden email]" <[hidden email]>
Subject: Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

 

Alex, got it. Cool.

 

I would like to try conversion of our mxml using this emulation approach.

To do that, how I can?  Appreciate your help.

 

Thank you, S. Takeshita  

 

 

On Sat, Feb 23, 2019 at 3:09 PM Alex Harui <[hidden email]> wrote:

Hi, Takeshita-san,

 

For these examples, I also think the Royale version loads faster.  It makes some sense, especially from a clean cache, as the browser has to load the player (essentially, downloading and starting an application), then load and parse the SWF, then run it.  The browser running a Royale app has to load a pile of JS and CSS files, but the browsers have been optimizing that over the past years.

 

To see the Advanced DataGrid in the Royale migration of Tour De Flex, first click on “MX Framework” then “Data Visualization”, then “AdvancedDataGrid” and then on the “AdvancedDataGrid” that appears as a child of the first one.  It should show an AdvancedDataGrid with a GroupingCollection.

 

HTH,

-Alex

 

From: Takeshita Shoichiro <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Friday, February 22, 2019 at 10:04 PM
To: "[hidden email]" <[hidden email]>
Subject: Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

 

Alex, thanks for the link information.

 

I understand Flash version takes more time for loading SWF than new Apache Royale.  Is my observation correct?

 

It seems what I'm looking for is the Advanced Data Grid.  It seems not implemented in Royale yet.  

 

But anyway, the progress seems to be great.

 

T-san

 

On Sat, Feb 23, 2019 at 2:28 PM Alex Harui <[hidden email]> wrote:

Hi,

 

The examples using emulation components are in examples/mxroyale.  The most sophisticated example is a migration of a subset of Tour De Flex.  It is still a work in progress.  The most current version is here: http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/TourDeFlexMigration/lastSuccessfulBuild/artifact/examples/mxroyale/tourdeflexmodules/bin/js-debug/index.html

 

The Flex version it is based on is here:  http://flex.apache.org/tourdeflex/index.html

 

The repos do not contain any serious example of migrating Flex to Basic   The focus of Basic was more about code size and performance than ease of migration.  We did migrate the FlexStore example.  It is in examples/royale/RoyaleStore.  The source it is based on is here: https://github.com/apache/flex-examples/tree/develop/FlexStore  There aren’t any examples running on a server at the moment.  Still, Harbs ported his app to Basic and he can tell you more about it.

 

-Alex

 

From: Takeshita Shoichiro <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Friday, February 22, 2019 at 5:01 PM
To: "[hidden email]" <[hidden email]>
Subject: Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

 

Alex,

 

Thanks a lot for providing me a set of choices to go.

I need some time to decide after doing some benchmark.

 

I'm interested in modern UI that may make users happy.  And also need to think about minimizing the migration effort to save time and money.   

 

Where can I find the more detailed information for (1) Basic set migration examples and (2) migration with emulation?

 

Best rega 

 

 

On Fri, Feb 22, 2019 at 3:00 PM Alex Harui <[hidden email]> wrote:

Hi T-San,

There is no single perfect migration strategy for Royale.  You will have to choose a path.

One way to think about migration is that there is your starting point, some amount of work, and an ending point.

Carlos just finished taking a bunch of MXML and AS, rewrote most of the MXML, modified about 30% of the AS, and used the Jewel component set to end up with an app with a very nice looking UI with modern UI components.  If you want a cool new UI because it is time to modernize and older Flex UI, then Jewel is a good choice.

A while ago, Harbs took a bunch of MXML and AS, rewrote most of the MXML, not sure about how much of the AS he changed, but he used Basic set and created a smaller faster application, but I don't think it has as many new UI components.   If you have concerns about size and performance and can spend a bit more time rewriting more code and customizing your UI, then using Basic is a good choice.

A couple of folks that I know of are trying to use the Emulation set.  The goal of the emulation set is to minimize the amount of changes to your MXML and AS.  A fair amount of Tour De Flex has been migrated using the Emulation components.  There is still work to be done, but there were very few changes to the MXML and AS.  All of the changes are in the emulation components.

To me, the emulation components are the charitable way of helping the rest of the folks migrating Flex apps who don't have the time or need for a modernized UI and aren't too concerned about performance.  Because, if you use the emulation set and it doesn't run or look correct, then the fix is to change the code in the emulation compoents and then every other user of those components benefits from that change.  If you choose one of the other options and change your code, then only you benefit from that change.  I wish I could convince more of the other Royale committers to help with the emulation components.  As the clock marches towards 2020, folks will have less and less time to move.

If you choose to go with the emulation components (which has AdvancedDataGrid working to some degree) then you are expected to try to learn how to fix bugs in the emulation components yourself.  In reality, this is true for Jewel and Basic as well, but is especially true for the emulation components because there are a lot more code paths to maintain.

So, think about it, and pick one of the three strategies and let us know what choice you make.  And feel free to ask more questions.

HTH,
-Alex

On 2/21/19, 4:46 AM, "T-san" <[hidden email]> wrote:

    Carlos,

    Thanks for your advice and work.

    Let me clarify several things.

    1. Do I need to convert mx coding to Jewel?
    2. If so, is there any useful information on how to do that?
    3. Is there user guide available for Jewel?  Or I have to read the Jewel
    source to study?

    And if you have a time, would you make your sample code complete for build?
    I'd also need to know how to build it since at this moment I do not know how
    to create pom.xml.

    T-san




    --
    Sent from: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-users.20374.n8.nabble.com%2F&amp;data=02%7C01%7Caharui%40adobe.com%7C73bc5071226444dab0f508d697faa246%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636863500060250570&amp;sdata=NSR584KJpjT2fdd91uv%2BE3AwcAwwww8SdN3nA1LHgys%3D&amp;reserved=0


 

--

Shoichiro Takeshita
武下 祥一郎


 

--

Shoichiro Takeshita
武下 祥一郎


 

--

Shoichiro Takeshita
武下 祥一郎



--
Shoichiro Takeshita
武下 祥一郎
Reply | Threaded
Open this post in threaded view
|

Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

T-san
Piotr, thanks.

Could show me the entire Ant command to be used?

Best regards,
S. Takeshita 

2019年2月24日(日) 20:39 Piotr Zarzycki <[hidden email]>:
I'm not sure whether Maven build working for that example. Ant for sure. 

Thanks,
Piotr

On Sun, Feb 24, 2019, 11:29 AM Takeshita Shoichiro <[hidden email]> wrote:
Alex, 

I tried to build tourdeflexmodules (incl. AdvancedDataGridExample.mxml) but seemed fail.  (no result)

Under the following directory, I ran mvn clean install.

\royale-asjs\royale-asjs\examples\mxroyale

Did I use the wrong procedure?

Appreciate your advice.

Best regards,

S. Takeshita

On Sat, Feb 23, 2019 at 3:33 PM Alex Harui <[hidden email]> wrote:

First, lower your expectations 😉

 

Then, make a copy of your code.

And read this:  https://apache.github.io/royale-docs/create-an-application/migrate-an-existing-app/migrate-from-flex.html

 

Good luck.  I’m about to stop work for today as I am on the road in the middle of the US.  I’ll be back on the west coast of the US in about 24 hours.

 

Thanks,

-Alex

 

From: Takeshita Shoichiro <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Friday, February 22, 2019 at 10:22 PM
To: "[hidden email]" <[hidden email]>
Subject: Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

 

Alex, got it. Cool.

 

I would like to try conversion of our mxml using this emulation approach.

To do that, how I can?  Appreciate your help.

 

Thank you, S. Takeshita  

 

 

On Sat, Feb 23, 2019 at 3:09 PM Alex Harui <[hidden email]> wrote:

Hi, Takeshita-san,

 

For these examples, I also think the Royale version loads faster.  It makes some sense, especially from a clean cache, as the browser has to load the player (essentially, downloading and starting an application), then load and parse the SWF, then run it.  The browser running a Royale app has to load a pile of JS and CSS files, but the browsers have been optimizing that over the past years.

 

To see the Advanced DataGrid in the Royale migration of Tour De Flex, first click on “MX Framework” then “Data Visualization”, then “AdvancedDataGrid” and then on the “AdvancedDataGrid” that appears as a child of the first one.  It should show an AdvancedDataGrid with a GroupingCollection.

 

HTH,

-Alex

 

From: Takeshita Shoichiro <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Friday, February 22, 2019 at 10:04 PM
To: "[hidden email]" <[hidden email]>
Subject: Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

 

Alex, thanks for the link information.

 

I understand Flash version takes more time for loading SWF than new Apache Royale.  Is my observation correct?

 

It seems what I'm looking for is the Advanced Data Grid.  It seems not implemented in Royale yet.  

 

But anyway, the progress seems to be great.

 

T-san

 

On Sat, Feb 23, 2019 at 2:28 PM Alex Harui <[hidden email]> wrote:

Hi,

 

The examples using emulation components are in examples/mxroyale.  The most sophisticated example is a migration of a subset of Tour De Flex.  It is still a work in progress.  The most current version is here: http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/TourDeFlexMigration/lastSuccessfulBuild/artifact/examples/mxroyale/tourdeflexmodules/bin/js-debug/index.html

 

The Flex version it is based on is here:  http://flex.apache.org/tourdeflex/index.html

 

The repos do not contain any serious example of migrating Flex to Basic   The focus of Basic was more about code size and performance than ease of migration.  We did migrate the FlexStore example.  It is in examples/royale/RoyaleStore.  The source it is based on is here: https://github.com/apache/flex-examples/tree/develop/FlexStore  There aren’t any examples running on a server at the moment.  Still, Harbs ported his app to Basic and he can tell you more about it.

 

-Alex

 

From: Takeshita Shoichiro <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Friday, February 22, 2019 at 5:01 PM
To: "[hidden email]" <[hidden email]>
Subject: Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

 

Alex,

 

Thanks a lot for providing me a set of choices to go.

I need some time to decide after doing some benchmark.

 

I'm interested in modern UI that may make users happy.  And also need to think about minimizing the migration effort to save time and money.   

 

Where can I find the more detailed information for (1) Basic set migration examples and (2) migration with emulation?

 

Best rega 

 

 

On Fri, Feb 22, 2019 at 3:00 PM Alex Harui <[hidden email]> wrote:

Hi T-San,

There is no single perfect migration strategy for Royale.  You will have to choose a path.

One way to think about migration is that there is your starting point, some amount of work, and an ending point.

Carlos just finished taking a bunch of MXML and AS, rewrote most of the MXML, modified about 30% of the AS, and used the Jewel component set to end up with an app with a very nice looking UI with modern UI components.  If you want a cool new UI because it is time to modernize and older Flex UI, then Jewel is a good choice.

A while ago, Harbs took a bunch of MXML and AS, rewrote most of the MXML, not sure about how much of the AS he changed, but he used Basic set and created a smaller faster application, but I don't think it has as many new UI components.   If you have concerns about size and performance and can spend a bit more time rewriting more code and customizing your UI, then using Basic is a good choice.

A couple of folks that I know of are trying to use the Emulation set.  The goal of the emulation set is to minimize the amount of changes to your MXML and AS.  A fair amount of Tour De Flex has been migrated using the Emulation components.  There is still work to be done, but there were very few changes to the MXML and AS.  All of the changes are in the emulation components.

To me, the emulation components are the charitable way of helping the rest of the folks migrating Flex apps who don't have the time or need for a modernized UI and aren't too concerned about performance.  Because, if you use the emulation set and it doesn't run or look correct, then the fix is to change the code in the emulation compoents and then every other user of those components benefits from that change.  If you choose one of the other options and change your code, then only you benefit from that change.  I wish I could convince more of the other Royale committers to help with the emulation components.  As the clock marches towards 2020, folks will have less and less time to move.

If you choose to go with the emulation components (which has AdvancedDataGrid working to some degree) then you are expected to try to learn how to fix bugs in the emulation components yourself.  In reality, this is true for Jewel and Basic as well, but is especially true for the emulation components because there are a lot more code paths to maintain.

So, think about it, and pick one of the three strategies and let us know what choice you make.  And feel free to ask more questions.

HTH,
-Alex

On 2/21/19, 4:46 AM, "T-san" <[hidden email]> wrote:

    Carlos,

    Thanks for your advice and work.

    Let me clarify several things.

    1. Do I need to convert mx coding to Jewel?
    2. If so, is there any useful information on how to do that?
    3. Is there user guide available for Jewel?  Or I have to read the Jewel
    source to study?

    And if you have a time, would you make your sample code complete for build?
    I'd also need to know how to build it since at this moment I do not know how
    to create pom.xml.

    T-san




    --
    Sent from: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-users.20374.n8.nabble.com%2F&amp;data=02%7C01%7Caharui%40adobe.com%7C73bc5071226444dab0f508d697faa246%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636863500060250570&amp;sdata=NSR584KJpjT2fdd91uv%2BE3AwcAwwww8SdN3nA1LHgys%3D&amp;reserved=0


 

--

Shoichiro Takeshita
武下 祥一郎


 

--

Shoichiro Takeshita
武下 祥一郎


 

--

Shoichiro Takeshita
武下 祥一郎



--
Shoichiro Takeshita
武下 祥一郎
--
Shoichiro Takeshita
武下 祥一郎
Reply | Threaded
Open this post in threaded view
|

Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

Carlos Rovira-2
Hi Takeshita,

if maven is not working for that example because no body used it with maven before, you're invited to fix the pom.xml file and submit a Pull Request to us, so we can try and incorporate your fix. I think it should be easy for you based on other pomx already working, and will both, help the project, and make you learn more about Royale. In that way the help is two way not only one.

El dom., 24 feb. 2019 a las 12:43, Takeshita Shoichiro (<[hidden email]>) escribió:
Piotr, thanks.

Could show me the entire Ant command to be used?

Best regards,
S. Takeshita 

2019年2月24日(日) 20:39 Piotr Zarzycki <[hidden email]>:
I'm not sure whether Maven build working for that example. Ant for sure. 

Thanks,
Piotr

On Sun, Feb 24, 2019, 11:29 AM Takeshita Shoichiro <[hidden email]> wrote:
Alex, 

I tried to build tourdeflexmodules (incl. AdvancedDataGridExample.mxml) but seemed fail.  (no result)

Under the following directory, I ran mvn clean install.

\royale-asjs\royale-asjs\examples\mxroyale

Did I use the wrong procedure?

Appreciate your advice.

Best regards,

S. Takeshita

On Sat, Feb 23, 2019 at 3:33 PM Alex Harui <[hidden email]> wrote:

First, lower your expectations 😉

 

Then, make a copy of your code.

And read this:  https://apache.github.io/royale-docs/create-an-application/migrate-an-existing-app/migrate-from-flex.html

 

Good luck.  I’m about to stop work for today as I am on the road in the middle of the US.  I’ll be back on the west coast of the US in about 24 hours.

 

Thanks,

-Alex

 

From: Takeshita Shoichiro <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Friday, February 22, 2019 at 10:22 PM
To: "[hidden email]" <[hidden email]>
Subject: Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

 

Alex, got it. Cool.

 

I would like to try conversion of our mxml using this emulation approach.

To do that, how I can?  Appreciate your help.

 

Thank you, S. Takeshita  

 

 

On Sat, Feb 23, 2019 at 3:09 PM Alex Harui <[hidden email]> wrote:

Hi, Takeshita-san,

 

For these examples, I also think the Royale version loads faster.  It makes some sense, especially from a clean cache, as the browser has to load the player (essentially, downloading and starting an application), then load and parse the SWF, then run it.  The browser running a Royale app has to load a pile of JS and CSS files, but the browsers have been optimizing that over the past years.

 

To see the Advanced DataGrid in the Royale migration of Tour De Flex, first click on “MX Framework” then “Data Visualization”, then “AdvancedDataGrid” and then on the “AdvancedDataGrid” that appears as a child of the first one.  It should show an AdvancedDataGrid with a GroupingCollection.

 

HTH,

-Alex

 

From: Takeshita Shoichiro <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Friday, February 22, 2019 at 10:04 PM
To: "[hidden email]" <[hidden email]>
Subject: Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

 

Alex, thanks for the link information.

 

I understand Flash version takes more time for loading SWF than new Apache Royale.  Is my observation correct?

 

It seems what I'm looking for is the Advanced Data Grid.  It seems not implemented in Royale yet.  

 

But anyway, the progress seems to be great.

 

T-san

 

On Sat, Feb 23, 2019 at 2:28 PM Alex Harui <[hidden email]> wrote:

Hi,

 

The examples using emulation components are in examples/mxroyale.  The most sophisticated example is a migration of a subset of Tour De Flex.  It is still a work in progress.  The most current version is here: http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/TourDeFlexMigration/lastSuccessfulBuild/artifact/examples/mxroyale/tourdeflexmodules/bin/js-debug/index.html

 

The Flex version it is based on is here:  http://flex.apache.org/tourdeflex/index.html

 

The repos do not contain any serious example of migrating Flex to Basic   The focus of Basic was more about code size and performance than ease of migration.  We did migrate the FlexStore example.  It is in examples/royale/RoyaleStore.  The source it is based on is here: https://github.com/apache/flex-examples/tree/develop/FlexStore  There aren’t any examples running on a server at the moment.  Still, Harbs ported his app to Basic and he can tell you more about it.

 

-Alex

 

From: Takeshita Shoichiro <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Friday, February 22, 2019 at 5:01 PM
To: "[hidden email]" <[hidden email]>
Subject: Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

 

Alex,

 

Thanks a lot for providing me a set of choices to go.

I need some time to decide after doing some benchmark.

 

I'm interested in modern UI that may make users happy.  And also need to think about minimizing the migration effort to save time and money.   

 

Where can I find the more detailed information for (1) Basic set migration examples and (2) migration with emulation?

 

Best rega 

 

 

On Fri, Feb 22, 2019 at 3:00 PM Alex Harui <[hidden email]> wrote:

Hi T-San,

There is no single perfect migration strategy for Royale.  You will have to choose a path.

One way to think about migration is that there is your starting point, some amount of work, and an ending point.

Carlos just finished taking a bunch of MXML and AS, rewrote most of the MXML, modified about 30% of the AS, and used the Jewel component set to end up with an app with a very nice looking UI with modern UI components.  If you want a cool new UI because it is time to modernize and older Flex UI, then Jewel is a good choice.

A while ago, Harbs took a bunch of MXML and AS, rewrote most of the MXML, not sure about how much of the AS he changed, but he used Basic set and created a smaller faster application, but I don't think it has as many new UI components.   If you have concerns about size and performance and can spend a bit more time rewriting more code and customizing your UI, then using Basic is a good choice.

A couple of folks that I know of are trying to use the Emulation set.  The goal of the emulation set is to minimize the amount of changes to your MXML and AS.  A fair amount of Tour De Flex has been migrated using the Emulation components.  There is still work to be done, but there were very few changes to the MXML and AS.  All of the changes are in the emulation components.

To me, the emulation components are the charitable way of helping the rest of the folks migrating Flex apps who don't have the time or need for a modernized UI and aren't too concerned about performance.  Because, if you use the emulation set and it doesn't run or look correct, then the fix is to change the code in the emulation compoents and then every other user of those components benefits from that change.  If you choose one of the other options and change your code, then only you benefit from that change.  I wish I could convince more of the other Royale committers to help with the emulation components.  As the clock marches towards 2020, folks will have less and less time to move.

If you choose to go with the emulation components (which has AdvancedDataGrid working to some degree) then you are expected to try to learn how to fix bugs in the emulation components yourself.  In reality, this is true for Jewel and Basic as well, but is especially true for the emulation components because there are a lot more code paths to maintain.

So, think about it, and pick one of the three strategies and let us know what choice you make.  And feel free to ask more questions.

HTH,
-Alex

On 2/21/19, 4:46 AM, "T-san" <[hidden email]> wrote:

    Carlos,

    Thanks for your advice and work.

    Let me clarify several things.

    1. Do I need to convert mx coding to Jewel?
    2. If so, is there any useful information on how to do that?
    3. Is there user guide available for Jewel?  Or I have to read the Jewel
    source to study?

    And if you have a time, would you make your sample code complete for build?
    I'd also need to know how to build it since at this moment I do not know how
    to create pom.xml.

    T-san




    --
    Sent from: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-users.20374.n8.nabble.com%2F&amp;data=02%7C01%7Caharui%40adobe.com%7C73bc5071226444dab0f508d697faa246%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636863500060250570&amp;sdata=NSR584KJpjT2fdd91uv%2BE3AwcAwwww8SdN3nA1LHgys%3D&amp;reserved=0


 

--

Shoichiro Takeshita
武下 祥一郎


 

--

Shoichiro Takeshita
武下 祥一郎


 

--

Shoichiro Takeshita
武下 祥一郎



--
Shoichiro Takeshita
武下 祥一郎
--
Shoichiro Takeshita
武下 祥一郎


--
Reply | Threaded
Open this post in threaded view
|

Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

Piotr Zarzycki
Carlos,

I don't think it is an easy as is in case of torudeflex migration. It contains module build etc.

Takeshita,

I believe it's enough to type "ant" in cmd console in folder which contains build.xml.

Piotr


On Sun, Feb 24, 2019, 12:52 PM Carlos Rovira <[hidden email]> wrote:
Hi Takeshita,

if maven is not working for that example because no body used it with maven before, you're invited to fix the pom.xml file and submit a Pull Request to us, so we can try and incorporate your fix. I think it should be easy for you based on other pomx already working, and will both, help the project, and make you learn more about Royale. In that way the help is two way not only one.

El dom., 24 feb. 2019 a las 12:43, Takeshita Shoichiro (<[hidden email]>) escribió:
Piotr, thanks.

Could show me the entire Ant command to be used?

Best regards,
S. Takeshita 

2019年2月24日(日) 20:39 Piotr Zarzycki <[hidden email]>:
I'm not sure whether Maven build working for that example. Ant for sure. 

Thanks,
Piotr

On Sun, Feb 24, 2019, 11:29 AM Takeshita Shoichiro <[hidden email]> wrote:
Alex, 

I tried to build tourdeflexmodules (incl. AdvancedDataGridExample.mxml) but seemed fail.  (no result)

Under the following directory, I ran mvn clean install.

\royale-asjs\royale-asjs\examples\mxroyale

Did I use the wrong procedure?

Appreciate your advice.

Best regards,

S. Takeshita

On Sat, Feb 23, 2019 at 3:33 PM Alex Harui <[hidden email]> wrote:

First, lower your expectations 😉

 

Then, make a copy of your code.

And read this:  https://apache.github.io/royale-docs/create-an-application/migrate-an-existing-app/migrate-from-flex.html

 

Good luck.  I’m about to stop work for today as I am on the road in the middle of the US.  I’ll be back on the west coast of the US in about 24 hours.

 

Thanks,

-Alex

 

From: Takeshita Shoichiro <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Friday, February 22, 2019 at 10:22 PM
To: "[hidden email]" <[hidden email]>
Subject: Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

 

Alex, got it. Cool.

 

I would like to try conversion of our mxml using this emulation approach.

To do that, how I can?  Appreciate your help.

 

Thank you, S. Takeshita  

 

 

On Sat, Feb 23, 2019 at 3:09 PM Alex Harui <[hidden email]> wrote:

Hi, Takeshita-san,

 

For these examples, I also think the Royale version loads faster.  It makes some sense, especially from a clean cache, as the browser has to load the player (essentially, downloading and starting an application), then load and parse the SWF, then run it.  The browser running a Royale app has to load a pile of JS and CSS files, but the browsers have been optimizing that over the past years.

 

To see the Advanced DataGrid in the Royale migration of Tour De Flex, first click on “MX Framework” then “Data Visualization”, then “AdvancedDataGrid” and then on the “AdvancedDataGrid” that appears as a child of the first one.  It should show an AdvancedDataGrid with a GroupingCollection.

 

HTH,

-Alex

 

From: Takeshita Shoichiro <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Friday, February 22, 2019 at 10:04 PM
To: "[hidden email]" <[hidden email]>
Subject: Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

 

Alex, thanks for the link information.

 

I understand Flash version takes more time for loading SWF than new Apache Royale.  Is my observation correct?

 

It seems what I'm looking for is the Advanced Data Grid.  It seems not implemented in Royale yet.  

 

But anyway, the progress seems to be great.

 

T-san

 

On Sat, Feb 23, 2019 at 2:28 PM Alex Harui <[hidden email]> wrote:

Hi,

 

The examples using emulation components are in examples/mxroyale.  The most sophisticated example is a migration of a subset of Tour De Flex.  It is still a work in progress.  The most current version is here: http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/TourDeFlexMigration/lastSuccessfulBuild/artifact/examples/mxroyale/tourdeflexmodules/bin/js-debug/index.html

 

The Flex version it is based on is here:  http://flex.apache.org/tourdeflex/index.html

 

The repos do not contain any serious example of migrating Flex to Basic   The focus of Basic was more about code size and performance than ease of migration.  We did migrate the FlexStore example.  It is in examples/royale/RoyaleStore.  The source it is based on is here: https://github.com/apache/flex-examples/tree/develop/FlexStore  There aren’t any examples running on a server at the moment.  Still, Harbs ported his app to Basic and he can tell you more about it.

 

-Alex

 

From: Takeshita Shoichiro <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Friday, February 22, 2019 at 5:01 PM
To: "[hidden email]" <[hidden email]>
Subject: Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

 

Alex,

 

Thanks a lot for providing me a set of choices to go.

I need some time to decide after doing some benchmark.

 

I'm interested in modern UI that may make users happy.  And also need to think about minimizing the migration effort to save time and money.   

 

Where can I find the more detailed information for (1) Basic set migration examples and (2) migration with emulation?

 

Best rega 

 

 

On Fri, Feb 22, 2019 at 3:00 PM Alex Harui <[hidden email]> wrote:

Hi T-San,

There is no single perfect migration strategy for Royale.  You will have to choose a path.

One way to think about migration is that there is your starting point, some amount of work, and an ending point.

Carlos just finished taking a bunch of MXML and AS, rewrote most of the MXML, modified about 30% of the AS, and used the Jewel component set to end up with an app with a very nice looking UI with modern UI components.  If you want a cool new UI because it is time to modernize and older Flex UI, then Jewel is a good choice.

A while ago, Harbs took a bunch of MXML and AS, rewrote most of the MXML, not sure about how much of the AS he changed, but he used Basic set and created a smaller faster application, but I don't think it has as many new UI components.   If you have concerns about size and performance and can spend a bit more time rewriting more code and customizing your UI, then using Basic is a good choice.

A couple of folks that I know of are trying to use the Emulation set.  The goal of the emulation set is to minimize the amount of changes to your MXML and AS.  A fair amount of Tour De Flex has been migrated using the Emulation components.  There is still work to be done, but there were very few changes to the MXML and AS.  All of the changes are in the emulation components.

To me, the emulation components are the charitable way of helping the rest of the folks migrating Flex apps who don't have the time or need for a modernized UI and aren't too concerned about performance.  Because, if you use the emulation set and it doesn't run or look correct, then the fix is to change the code in the emulation compoents and then every other user of those components benefits from that change.  If you choose one of the other options and change your code, then only you benefit from that change.  I wish I could convince more of the other Royale committers to help with the emulation components.  As the clock marches towards 2020, folks will have less and less time to move.

If you choose to go with the emulation components (which has AdvancedDataGrid working to some degree) then you are expected to try to learn how to fix bugs in the emulation components yourself.  In reality, this is true for Jewel and Basic as well, but is especially true for the emulation components because there are a lot more code paths to maintain.

So, think about it, and pick one of the three strategies and let us know what choice you make.  And feel free to ask more questions.

HTH,
-Alex

On 2/21/19, 4:46 AM, "T-san" <[hidden email]> wrote:

    Carlos,

    Thanks for your advice and work.

    Let me clarify several things.

    1. Do I need to convert mx coding to Jewel?
    2. If so, is there any useful information on how to do that?
    3. Is there user guide available for Jewel?  Or I have to read the Jewel
    source to study?

    And if you have a time, would you make your sample code complete for build?
    I'd also need to know how to build it since at this moment I do not know how
    to create pom.xml.

    T-san




    --
    Sent from: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-users.20374.n8.nabble.com%2F&amp;data=02%7C01%7Caharui%40adobe.com%7C73bc5071226444dab0f508d697faa246%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636863500060250570&amp;sdata=NSR584KJpjT2fdd91uv%2BE3AwcAwwww8SdN3nA1LHgys%3D&amp;reserved=0


 

--

Shoichiro Takeshita
武下 祥一郎


 

--

Shoichiro Takeshita
武下 祥一郎


 

--

Shoichiro Takeshita
武下 祥一郎



--
Shoichiro Takeshita
武下 祥一郎
--
Shoichiro Takeshita
武下 祥一郎


--
Reply | Threaded
Open this post in threaded view
|

Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

Carlos Rovira-2
Hi Piotr.

you're right, I was thinking in some of the examples in mxroyale examples that are already setup for maven, so thought there was other one in that folder that was not already setup for maven, so that change is easy. Since we're talking about TDF, just another thing.

Maybe he just can copy paste one of those examples (the MX for example that works with maven), and then fill it with the code he wants to try.

El dom., 24 feb. 2019 a las 13:09, Piotr Zarzycki (<[hidden email]>) escribió:
Carlos,

I don't think it is an easy as is in case of torudeflex migration. It contains module build etc.

Takeshita,

I believe it's enough to type "ant" in cmd console in folder which contains build.xml.

Piotr


On Sun, Feb 24, 2019, 12:52 PM Carlos Rovira <[hidden email]> wrote:
Hi Takeshita,

if maven is not working for that example because no body used it with maven before, you're invited to fix the pom.xml file and submit a Pull Request to us, so we can try and incorporate your fix. I think it should be easy for you based on other pomx already working, and will both, help the project, and make you learn more about Royale. In that way the help is two way not only one.

El dom., 24 feb. 2019 a las 12:43, Takeshita Shoichiro (<[hidden email]>) escribió:
Piotr, thanks.

Could show me the entire Ant command to be used?

Best regards,
S. Takeshita 

2019年2月24日(日) 20:39 Piotr Zarzycki <[hidden email]>:
I'm not sure whether Maven build working for that example. Ant for sure. 

Thanks,
Piotr

On Sun, Feb 24, 2019, 11:29 AM Takeshita Shoichiro <[hidden email]> wrote:
Alex, 

I tried to build tourdeflexmodules (incl. AdvancedDataGridExample.mxml) but seemed fail.  (no result)

Under the following directory, I ran mvn clean install.

\royale-asjs\royale-asjs\examples\mxroyale

Did I use the wrong procedure?

Appreciate your advice.

Best regards,

S. Takeshita

On Sat, Feb 23, 2019 at 3:33 PM Alex Harui <[hidden email]> wrote:

First, lower your expectations 😉

 

Then, make a copy of your code.

And read this:  https://apache.github.io/royale-docs/create-an-application/migrate-an-existing-app/migrate-from-flex.html

 

Good luck.  I’m about to stop work for today as I am on the road in the middle of the US.  I’ll be back on the west coast of the US in about 24 hours.

 

Thanks,

-Alex

 

From: Takeshita Shoichiro <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Friday, February 22, 2019 at 10:22 PM
To: "[hidden email]" <[hidden email]>
Subject: Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

 

Alex, got it. Cool.

 

I would like to try conversion of our mxml using this emulation approach.

To do that, how I can?  Appreciate your help.

 

Thank you, S. Takeshita  

 

 

On Sat, Feb 23, 2019 at 3:09 PM Alex Harui <[hidden email]> wrote:

Hi, Takeshita-san,

 

For these examples, I also think the Royale version loads faster.  It makes some sense, especially from a clean cache, as the browser has to load the player (essentially, downloading and starting an application), then load and parse the SWF, then run it.  The browser running a Royale app has to load a pile of JS and CSS files, but the browsers have been optimizing that over the past years.

 

To see the Advanced DataGrid in the Royale migration of Tour De Flex, first click on “MX Framework” then “Data Visualization”, then “AdvancedDataGrid” and then on the “AdvancedDataGrid” that appears as a child of the first one.  It should show an AdvancedDataGrid with a GroupingCollection.

 

HTH,

-Alex

 

From: Takeshita Shoichiro <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Friday, February 22, 2019 at 10:04 PM
To: "[hidden email]" <[hidden email]>
Subject: Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

 

Alex, thanks for the link information.

 

I understand Flash version takes more time for loading SWF than new Apache Royale.  Is my observation correct?

 

It seems what I'm looking for is the Advanced Data Grid.  It seems not implemented in Royale yet.  

 

But anyway, the progress seems to be great.

 

T-san

 

On Sat, Feb 23, 2019 at 2:28 PM Alex Harui <[hidden email]> wrote:

Hi,

 

The examples using emulation components are in examples/mxroyale.  The most sophisticated example is a migration of a subset of Tour De Flex.  It is still a work in progress.  The most current version is here: http://apacheroyaleci.westus2.cloudapp.azure.com:8080/job/TourDeFlexMigration/lastSuccessfulBuild/artifact/examples/mxroyale/tourdeflexmodules/bin/js-debug/index.html

 

The Flex version it is based on is here:  http://flex.apache.org/tourdeflex/index.html

 

The repos do not contain any serious example of migrating Flex to Basic   The focus of Basic was more about code size and performance than ease of migration.  We did migrate the FlexStore example.  It is in examples/royale/RoyaleStore.  The source it is based on is here: https://github.com/apache/flex-examples/tree/develop/FlexStore  There aren’t any examples running on a server at the moment.  Still, Harbs ported his app to Basic and he can tell you more about it.

 

-Alex

 

From: Takeshita Shoichiro <[hidden email]>
Reply-To: "[hidden email]" <[hidden email]>
Date: Friday, February 22, 2019 at 5:01 PM
To: "[hidden email]" <[hidden email]>
Subject: Re: Migrating an app from Apache Flex to Apache Royale (tweet thread)

 

Alex,

 

Thanks a lot for providing me a set of choices to go.

I need some time to decide after doing some benchmark.

 

I'm interested in modern UI that may make users happy.  And also need to think about minimizing the migration effort to save time and money.   

 

Where can I find the more detailed information for (1) Basic set migration examples and (2) migration with emulation?

 

Best rega 

 

 

On Fri, Feb 22, 2019 at 3:00 PM Alex Harui <[hidden email]> wrote:

Hi T-San,

There is no single perfect migration strategy for Royale.  You will have to choose a path.

One way to think about migration is that there is your starting point, some amount of work, and an ending point.

Carlos just finished taking a bunch of MXML and AS, rewrote most of the MXML, modified about 30% of the AS, and used the Jewel component set to end up with an app with a very nice looking UI with modern UI components.  If you want a cool new UI because it is time to modernize and older Flex UI, then Jewel is a good choice.

A while ago, Harbs took a bunch of MXML and AS, rewrote most of the MXML, not sure about how much of the AS he changed, but he used Basic set and created a smaller faster application, but I don't think it has as many new UI components.   If you have concerns about size and performance and can spend a bit more time rewriting more code and customizing your UI, then using Basic is a good choice.

A couple of folks that I know of are trying to use the Emulation set.  The goal of the emulation set is to minimize the amount of changes to your MXML and AS.  A fair amount of Tour De Flex has been migrated using the Emulation components.  There is still work to be done, but there were very few changes to the MXML and AS.  All of the changes are in the emulation components.

To me, the emulation components are the charitable way of helping the rest of the folks migrating Flex apps who don't have the time or need for a modernized UI and aren't too concerned about performance.  Because, if you use the emulation set and it doesn't run or look correct, then the fix is to change the code in the emulation compoents and then every other user of those components benefits from that change.  If you choose one of the other options and change your code, then only you benefit from that change.  I wish I could convince more of the other Royale committers to help with the emulation components.  As the clock marches towards 2020, folks will have less and less time to move.

If you choose to go with the emulation components (which has AdvancedDataGrid working to some degree) then you are expected to try to learn how to fix bugs in the emulation components yourself.  In reality, this is true for Jewel and Basic as well, but is especially true for the emulation components because there are a lot more code paths to maintain.

So, think about it, and pick one of the three strategies and let us know what choice you make.  And feel free to ask more questions.

HTH,
-Alex

On 2/21/19, 4:46 AM, "T-san" <[hidden email]> wrote:

    Carlos,

    Thanks for your advice and work.

    Let me clarify several things.

    1. Do I need to convert mx coding to Jewel?
    2. If so, is there any useful information on how to do that?
    3. Is there user guide available for Jewel?  Or I have to read the Jewel
    source to study?

    And if you have a time, would you make your sample code complete for build?
    I'd also need to know how to build it since at this moment I do not know how
    to create pom.xml.

    T-san




    --
    Sent from: https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapache-royale-users.20374.n8.nabble.com%2F&amp;data=02%7C01%7Caharui%40adobe.com%7C73bc5071226444dab0f508d697faa246%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636863500060250570&amp;sdata=NSR584KJpjT2fdd91uv%2BE3AwcAwwww8SdN3nA1LHgys%3D&amp;reserved=0


 

--

Shoichiro Takeshita
武下 祥一郎


 

--

Shoichiro Takeshita
武下 祥一郎


 

--

Shoichiro Takeshita
武下 祥一郎



--
Shoichiro Takeshita
武下 祥一郎
--
Shoichiro Takeshita
武下 祥一郎


--


--
12