On 2/6/15, 2:58 AM, "Raj Raju" <raj.virtu...@gmail.com> wrote:
>Hi Alex, > >May be am going bit crazy here but just a thought. Can we directly migrate >by using any *tool or some logic *(not now , but in the near feature >) which will do the work for us instead of rewriting the code ?, if this >will work then , that will save our lot of energies and development time >and I would say this will definitely a game changer in the current market. > >Thanks for your replies. Again, anything not available now has to be created by the community. A migration tool will be created if folks reading this start coding it, or help me out with other tasks so that I end up with time to code it. How important a migration tool is has yet to be determined. But if it is important to you, start working on it or convince others to start working on it. For me, it is too early to start right now. I’ve heard from some folks that the main migration effort is in migrating the MXML for the UI. If you have good separation of UI from other code and that other code is event driven and written in AS, that AS code should not require too much migration if at all. I’ve seen a good sized library get ported by only changing a few classes. And then those folks decide they’d rather rewrite their UI anyway in order to modernize it a bit. If you look at the differences between FlexJSStore and FlexStore, you’ll see that a lot of the migration was in changing component namespaces and handling styles differently. That can certainly be reduced by creating a Spark-like or MX-like component set that tries to mimic old Flex behavior. The current component set thinly wraps native HTML/CSS behavior or wraps Jquery so you get best performance on the JS side. Again, creating a Spark-like or MX-like component set depends on folks jumping in and doing it or helping me find time to do it. So consider, especially if you have a Flex 3 app, whether the UI does need to be preserved as is or it is time to upgrade the UI, and whether your AS code has good boundaries around it and significant portions of it can be re-used as is. If it can, feel free to try migrating manually now and give us feedback on how it feels. Thanks, -Alex > > >On Fri, Feb 6, 2015 at 1:47 PM, Alex Harui <aha...@adobe.com> wrote: > >> >> >> On 2/5/15, 11:53 PM, "Deepak MS" <megharajdee...@gmail.com> wrote: >> >> >Hi Alex, >> >When you say: I ported the old FlexStore example app from MX to Spark >>and >> >then to FlexJS >> > >> >Does that mean that if we want to migrate flex 3 applications, we have >>to >> >compulsorily migrate it to flex 4 first(before migrating to FlexJS)? >> >> No. I went to Spark first because I figured that more folks are using >> Spark than MX these days and didn’t want folks to discount FlexJS as >>being >> targeted towards older apps. >> >> You can compare the MX FlexStore against the FlexJSStore and see that >> there are a lot of similarities there. >> >> FlexJS is being designed on purpose to support multiple component sets. >> The FlexJSStore example uses the basic component set we’ve written from >> scratch. Next to it in the repo is a version of FlexJSStore that uses >> Jquery UI widgets. I had envisioned writing the beginnings of a more >> Spark-like and/or MX-like component set to see if that would cut down on >> the migration effort and seee if it results in larger JS output and >>lower >> performance. I may still get to that, but first I want to finish a few >> other things. Any other volunteer is welcome to get started on that. >> >> The key thing to remember is that this is an Apache effort even though >>my >> adobe.com email keeps showing up on the list. What FlexJS becomes and >>how >> soon, and what component APIs it gets sooner rather than later is up to >> you. We need more folks to help out in any way they can. There is no >> corporation that is going get a team of developers to create a product >>and >> market it like Adobe used to. >> >> And IMO, those who join in sooner and therefore have more experience >>with >> FlexJS will have an advantage over others if FlexJS gets some traction >>and >> folks start looking for FlexJS developers. >> >> Also, set your short-term expectations on what Flex 1 or Flex 2 was. It >> was enough to get the ball rolling, but nothing like Flex 3 or Flex 4. >>We >> can probably eventually get to something like Flex 3 or Flex 4 but it >> takes time depending on how many people we get working on it. >> >> Hope to see you contributing, >> -Alex >> >> > >> >On Fri, Feb 6, 2015 at 12:22 PM, Alex Harui <aha...@adobe.com> wrote: >> > >> >> >> >> >> >> On 2/5/15, 10:06 PM, "Raj Raju" <raj.virtu...@gmail.com> wrote: >> >> >> >> >Hello Dev-team, >> >> > >> >> > >> >> >I been following this group from quite long time , but no where i >> >>noticed >> >> >, >> >> >migrating Flex 3/4 apps to Flex JS. Is this possible to migrate our >> >>apps >> >> >with our new Flex JS framework? >> >> > >> >> >> >> Well, that’s the goal. For sure, we don’t have all of the components >> >>yet. >> >> FlexJS is effectively alpha-quality. We welcome volunteers to help >> >>write >> >> more components. I recently posted that I ported the old FlexStore >> >>example >> >> app from MX to Spark and then to FlexJS. The source for the MX >>version >> >>is >> >> here [1], the Spark version is here [2] and the FlexJS version is >>here >> >> [3]. A running version of the FlexJS example is here [4] >> >> >> >> If you want to work with us on make migration more possible and >>easier, >> >>I >> >> will do what I can to help. >> >> >> >> -Alex >> >> >> >> [1] >> >> >> >> >> >>https://git-wip-us.apache.org/repos/asf/flex-sdk/repo?p=flex-examples.git >> >>;a >> >> >> >>>>=tree;f=FlexStore/mx;h=6ec4b395951886f8cbb40c7c2f9967b401983ac7;hb=refs >>>>/h >> >>ea >> >> ds/develop >> >> [2] >> >> >> >> >> >>https://git-wip-us.apache.org/repos/asf/flex-sdk/repo?p=flex-examples.git >> >>;a >> >> >> >>>>=tree;f=FlexStore/spark;h=d3900c6ff221ef439b3f3d3b27d6a45a19062f3e;hb=r >>>>ef >> >>s/ >> >> heads/develop >> >> [3] >> >> >> >> >> >>https://git-wip-us.apache.org/repos/asf/flex-sdk/repo?p=flex-asjs.git;a=t >> >>re >> >> >> >>>>e;f=examples/FlexJSStore;h=f251e06cb71de9da6cdf76b8b9813de8ba4b26e8;hb= >>>>re >> >>fs >> >> /heads/develop >> >> [4] http://people.apache.org/~aharui/FlexJS/FlexJSStore/ >> >> >> >> >> >>
