That sounds awesome! On 10/23/16, 2:57 AM, "Christofer Dutz" <christofer.d...@c-ware.de> wrote:
>Ok ... so I just added a first version of Corodva support. > > >After my last mail about the cordova-maven-plugin from the errai guys I >had another look at the current version in their repo. Here I noticed >that they had cleaned up quite a bit since the 3.x versions I >experimented with. With the 4.x versions it seems that the configuration >fits nicely to the current setup of the FlexJS examples. So I added what >needed to be added and now I can have Cordova kick in to build mobile >applications from the mobile FlexJS examples. > > >As this requires users to eventually install Android SDK and IOs SDKs >(Which might not be available on all platforms) I put this into a profile >that has to be explicitly activated "with-cordova" ... so if you want to >build the example with cordova support, you need to execute the following >build: > > >mvn clean install -P build-examples,with-cordova -s template-settings.xml > > >Next I'll try this out on a windows VM > > >Chris > >________________________________ >Von: Alex Harui <aha...@adobe.com> >Gesendet: Samstag, 22. Oktober 2016 07:25:57 >An: dev@flex.apache.org >Betreff: Re: [FlexJS] Maveninze MobileStocks (was [FlexJS] Mobile Apps) > >FWIW, I just pushed a change to cordova-build.xml that let me do the >following: >- git clone https://git-wip-us.apache.org/repos/asf/flex-asjs.git >flex-asjs >- cd flex-asjs >- git checkout develop >- mvn clean install >- cd examples/flexjs/MobileStocks >- mvn clean install >- ant -f ../../../cordova-build.xml > >I didn't get any rat errors. There were some warnings on the GCC compile >on the last step. > >Then: >- ant -f ../../../cordova-build.xml run.android > >And it showed up on my android phone. The run.android took several >minutes to do a final build before installing on the device. > >HTH, >-Alex > >On 10/21/16, 4:45 PM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" ><carlos.rov...@gmail.com on behalf of carlos.rov...@codeoscopic.com> >wrote: > >>> What I don't know how to do is replicate what cordova_build.xml does in >>> Maven. That's where we could use Chris or other Maven experts. >>> >>> >>Yes mavenizing a simple project is not a problem (my MDL project and the >>example are proof that is easy thank to Chris's work in preparing the >>entire project. I think as well we need Chris only in something new that >>is >>not implemented yet. >> >> >>> Carlos, what was your setup when you tried the Ant script? Were you >>> working from the repo, or some other configuration? >>> >> >>I has the repo synchronized with source tree, and as you guys make some >>changes I pull to my local and rebuild 0.8.0-snapshot with maven and >>continue working. Now for MobileStock: if try to build with maven it >>arise >>that many files are without license (see rat.txt). That's easy to solve, >>just check the rat file and see what files are and add license. But this >>told me that no maven build was considered. >> >> >> >>> >>> Thanks, >>> -Alex >>> >>> On 10/21/16, 1:03 PM, "omup...@gmail.com on behalf of OmPrakash >>>Muppirala" >>> <omup...@gmail.com on behalf of bigosma...@gmail.com> wrote: >>> >>> >Chris, >>> > >>> >Can you please take this opportunity to create a wiki page on how to >>> >create >>> >a pom.xml or in other words - how to mavenize a project? It seems >>>like we >>> >are going to have more of this and obviously you dont want all this >>>work >>> >ending up on yourself. >>> > >>> >Thanks, >>> >Om >>> > >>> >On Fri, Oct 21, 2016 at 1:01 PM, Christofer Dutz >>> ><christofer.d...@c-ware.de> >>> >wrote: >>> > >>> >> Hi Carlos, >>> >> >>> >> Thanks for that positive feedback. Ist incredibly nice to hear that >>>:-) >>> >> >>> >> Usually as soon as I detect a new example not building with Maven, I >>>add >>> >> the missing poms. So if there us anything missing, just drop a nite >>>and >>> >> I'll take care of it. >>> >> >>> >> Chris >>> >> >>> >> >>> >> >>> >> Von meinem Samsung Galaxy Smartphone gesendet. >>> >> >>> >> >>> >> -------- Ursprüngliche Nachricht -------- >>> >> Von: Carlos Rovira <carlos.rov...@codeoscopic.com> >>> >> Datum: 21.10.16 21:30 (GMT+01:00) >>> >> An: dev@flex.apache.org >>> >> Betreff: [FlexJS] Maveninze MobileStocks (was [FlexJS] Mobile Apps) >>> >> >>> >> Maybe Chris could help with that. He's the man that makes the "maven >>> >>magic" >>> >> >>> >> One think to notice here. My laptop was recently reinstaled from >>>zero >>> >>with >>> >> macOS Sierra. >>> >> I used Homebrew and it was amazingly simple to configure the dev >>> >> environment and I even no need to >>> >> start adding environment variable (no JAVA_HOME, no M2_HOME, >>> >>no...nothing) >>> >> thanks to use maven as build tool >>> >> >>> >> Now trying to build MobileStocks with Ant is starting to complain >>>"that >>> >> FALCON_HOME doesn't exist", and then willl be come another... >>> >> >>> >> Evidently I must now to configure that, but I want to expose the >>> >> incredible,amazing easy environment that is now FlexJS thanks to the >>> >> mavenization. >>> >> If we decided (If I remember well) to make maven as the official >>>tool, >>> >>we >>> >> should try to make all project maven aware, so people coming does >>>not >>> >>have >>> >> any problem with some parts build with ant and others with maven. >>> >> >>> >> just my opinion >>> >> >>> >> Thanks >>> >> >>> >> >>> >> 2016-10-21 20:13 GMT+02:00 Alex Harui <aha...@adobe.com>: >>> >> >>> >> > We could probably make cordova-build.xml work with Maven output in >>>the >>> >> > target folder instead of bin-debug. But yes, I don't think Peter >>>or I >>> >> > understand how to use Maven with Cordova, so the last piece will >>>still >>> >> > require Ant until some other volunteer steps up. >>> >> > >>> >> > -Alex >>> >> > >>> >> > On 10/21/16, 11:00 AM, "Peter Ent" <p...@adobe.com> wrote: >>> >> > >>> >> > >I used maven on a very complex project a number of years ago and >>> >>don't >>> >> > >really remember much about it. I can try to piece together a pom >>>file >>> >> > >using another example, but I would have no idea how to do >>>something >>> >>like >>> >> > >the cordova-build.xml file. >>> >> > > >>> >> > >‹peter >>> >> > > >>> >> > >On 10/21/16, 12:16 PM, "carlos.rov...@gmail.com on behalf of >>>Carlos >>> >> > >Rovira" <carlos.rov...@gmail.com on behalf of >>> >> > >carlos.rov...@codeoscopic.com> wrote: >>> >> > > >>> >> > >>One final note, I'm building all with maven. I didn't try maven >>>as >>> >>you >>> >> > >>posted ANT build instructions. >>> >> > >>Are maven pom configured to work. It would be very handy >>> >> > >>thanks! >>> >> > >> >>> >> > >>2016-10-21 18:12 GMT+02:00 Carlos Rovira < >>> >> carlos.rov...@codeoscopic.com >>> >> > >: >>> >> > >> >>> >> > >>> Hi Peter, >>> >> > >>> >>> >> > >>> congrats for reaching the milestone. I'm trying but finding >>>some >>> >> > >>>problems: >>> >> > >>> >>> >> > >>> (Prerequisites: I'm on Mac and want to try iOS version, I >>>already >>> >>has >>> >> > >>> Xcode installed. I don't have FB anymore. I installed Cordova >>>vía >>> >> > >>>NPM...all >>> >> > >>> ok) >>> >> > >>> >>> >> > >>> *I run from MobileStocks folder, but ant told me that there's >>>no >>> >> > >>> bin/je-debug folder. Checking wiki url you gave I created >>>manually >>> >> > >>> bin/debug. finaly I get ANT BUILD SUCCESSFUL (maybe ant should >>> >>create >>> >> > >>>bin >>> >> > >>> and js-debug folders?) >>> >> > >>> >>> >> > >>> * Then for your instructions I use "run.ios"...this is a file >>>(I >>> >> don't >>> >> > >>> find any). I'm stuck there. >>> >> > >>> >>> >> > >>> For getting styling you mention, there's 2 approach, one to >>>use >>> >>what >>> >> we >>> >> > >>> have and try to style ( I think this is limited), the second >>>is >>> >>use >>> >> > >>>some >>> >> > >>> good library out there like MDL, BootStrap, or others. I'm on >>>the >>> >> works >>> >> > >>>as >>> >> > >>> you already know with MDL. Right now I'm doing components in >>>the >>> >> "mdl" >>> >> > >>> namespace, but this is not the ideal scenario, since it would >>>be >>> >> great >>> >> > >>>to >>> >> > >>> get a MDL style in a js:Button without the need to change it >>>to >>> >> > >>>mdl:Button, >>> >> > >>> only applying styles. >>> >> > >>> >>> >> > >>> I'm finding some more few things: >>> >> > >>> >>> >> > >>> * CSS styles already in place are very cumbersome and I think >>>we >>> >> would >>> >> > >>> need to work on a clean separation to avoid mixing and >>>generating >>> >> side >>> >> > >>> effect. Alex propose in other thread some compiler options to >>> >>avoid >>> >> > >>>include >>> >> > >>> CSS...maybe this is a nice option. >>> >> > >>> * classNames and typeNames are part of the problems, but only >>>due >>> >>to >>> >> > >>>the >>> >> > >>> before mentioned point. If we can compile without already set >>> >>styles >>> >> > >>>this >>> >> > >>> could solve the problem. >>> >> > >>> * With MDL I'm inserting classNames inside class components, >>>what >>> >>I >>> >> > >>>don't >>> >> > >>> like since is a clear mixing of AS3 code declaration with CSS >>> >>styles. >>> >> > >>> * from the experience I'm getting with MDL (and suppose that >>>other >>> >> > >>> libraries like bootstrap will be the same), those good looking >>> >>styles >>> >> > >>>are >>> >> > >>> dependent from a concrete way of implementing the html tags >>>and >>> >>use >>> >> of >>> >> > >>>html >>> >> > >>> class. Maybe a component need to create a surrounding div and >>>then >>> >> nest >>> >> > >>>a >>> >> > >>> span, and this maybe is not what our HTML implementation does. >>>I >>> >> think >>> >> > >>>a >>> >> > >>> right approach should be to use the HTML swc and be able to >>>change >>> >> the >>> >> > >>> output to match what a concrete style demands. >>> >> > >>> >>> >> > >>> For example, I'm making a Card component (and btw learning how >>> >>flexjs >>> >> > >>> framework works): >>> >> > >>> https://getmdl.io/components/#cards-section >>> >> > >>> >>> >> > >>> This could be some kind of a Panel...but is not a Panel, so >>>better >>> >> > >>>create >>> >> > >>> a Card component, but if you see the structure, is completely >>> >>made to >>> >> > >>>use >>> >> > >>> the MDL style... >>> >> > >>> >>> >> > >>> looking at the MobileStocks code, it seems, the approach is >>>the >>> >>first >>> >> > >>>one, >>> >> > >>> since is all made with FlexJS comps. In that scenario, I think >>>we >>> >> need >>> >> > >>>as >>> >> > >>> well a way to not be bloated with CSS styles that we don't >>>know >>> >>where >>> >> > >>>came >>> >> > >>> from. and start from a clean state. >>> >> > >>> >>> >> > >>> I think this is something like a prerequisite in order to be >>>able >>> >>to >>> >> > >>>work >>> >> > >>> in some kind of styling. >>> >> > >>> >>> >> > >>> Hope I could first build MobileStocks and try on my iPhone to >>>get >>> >>a >>> >> > >>>look >>> >> > >>> at what we are talking about. >>> >> > >>> >>> >> > >>> Thanks >>> >> > >>> >>> >> > >>> Carlos >>> >> > >>> >>> >> > >>> >>> >> > >>> >>> >> > >>> >>> >> > >>> 2016-10-21 15:53 GMT+02:00 Peter Ent <p...@adobe.com>: >>> >> > >>> >>> >> > >>>> Hi, >>> >> > >>>> >>> >> > >>>> We've been working on an improved FlexJS mobile app: >>> >>MobileStocks. >>> >> It >>> >> > >>>>is >>> >> > >>>> in the FlexJS examples directory. This example runs on both >>> >>Android >>> >> > >>>>and iOS >>> >> > >>>> devices and is a version of MobileTrader, offering just two >>> >>views. >>> >> The >>> >> > >>>> first view allows you to enter a stock symbol and a number of >>> >> shares. >>> >> > >>>>It >>> >> > >>>> then puts that information into a DataGrid and a chart, >>> >>monitoring >>> >> the >>> >> > >>>> change in prices and updating the grid and chart. The second >>>view >>> >> > >>>>allows >>> >> > >>>> you to enter a symbol and watch it in a similar fashion. >>> >> MobileStocks >>> >> > >>>>uses >>> >> > >>>> the FlexJS Storage project to retain the list of stocks >>>between >>> >> > >>>>sessions. >>> >> > >>>> >>> >> > >>>> MobileStocks uses Apache Cordova, making the app run on both >>>iOS >>> >>and >>> >> > >>>> Android from a single code base. Cordova integration is >>>handled >>> >>by >>> >> the >>> >> > >>>> FlexJS Mobile project as well as the Storage project. >>> >> > >>>> >>> >> > >>>> Building and running the app is pretty simple and you can do >>>it >>> >>from >>> >> > >>>>the >>> >> > >>>> command line or from Flash Builder. If you want to use the >>> >>command >>> >> > >>>>line, >>> >> > >>>> pull down the source and run ANT to build the js-debug >>>directory. >>> >> Then >>> >> > >>>>run >>> >> > >>>> "ant -f ../../../cordova-build.xml" to create the Apache >>>Cordova >>> >> > >>>> sub-project. Once that has done, connect your Android device >>>to >>> >>your >>> >> > >>>> computer and run "ant -f ../../../cordova-build.xml >>>run.android" >>> >> which >>> >> > >>>>will >>> >> > >>>> download a little more and then install and run the app on >>>your >>> >> > >>>>device. >>> >> > >>>> iOS users can do the same thing (use "run.ios") which will >>>launch >>> >> the >>> >> > >>>> device simulator; you also need to have Xcode installed. >>> >> > >>>> >>> >> > >>>> You can run this example easily from Flash Builder by >>>following >>> >>the >>> >> > >>>> instructions on the FlexJS wiki [1] and use the launch >>> >> configurations >>> >> > >>>>to >>> >> > >>>> build and run the app. >>> >> > >>>> >>> >> > >>>> The example has shown us a couple of things. >>> >> > >>>> >>> >> > >>>> * We needed to make more beads to handle different types >>>of >>> >>data >>> >> > >>>> providers in the pay-as-you-go world of FlexJS; this keeps >>>the >>> >>app >>> >> as >>> >> > >>>>small >>> >> > >>>> as possible. >>> >> > >>>> * We needed to add additional layouts that were more >>> >>responsive >>> >> to >>> >> > >>>> resizing. >>> >> > >>>> * We needed to fix a couple of bugs as well. >>> >> > >>>> >>> >> > >>>> Please give this a try if you can. The next step for the app >>> >>would >>> >> be >>> >> > >>>> some nice styling. This my "developer's eye" which is just >>> >>minimal, >>> >> so >>> >> > >>>> contribute some updates to that, if you can. >>> >> > >>>> >>> >> > >>>> [1] >>>https://cwiki.apache.org/confluence/pages/viewpage.action? >>> >> > >>>> pageId=63406558 >>> >> > >>>> >>> >> > >>>> Regards, >>> >> > >>>> Peter Ent >>> >> > >>>> Adobe Systems/Apache Flex Project >>> >> > >>>> >>> >> > >>> >>> >> > >>> >>> >> > >>> >>> >> > >>> -- >>> >> > >>> >>> >> > >>> Carlos Rovira >>> >> > >>> Director General >>> >> > >>> M: +34 607 22 60 05 >>> >> > >>> http://www.codeoscopic.com >>> >> > >>> http://www.avant2.es >>> >> > >>> >>> >> > >>> >>> >> > >>> Este mensaje se dirige exclusivamente a su destinatario y >>>puede >>> >> > >>>contener >>> >> > >>> información privilegiada o confidencial. Si ha recibido este >>> >>mensaje >>> >> > >>>por >>> >> > >>> error, le rogamos que nos lo comunique inmediatamente por esta >>> >>misma >>> >> > >>>vía y >>> >> > >>> proceda a su destrucción. >>> >> > >>> >>> >> > >>> De la vigente Ley Orgánica de Protección de Datos (15/1999), >>>le >>> >> > >>> comunicamos que sus datos forman parte de un fichero cuyo >>> >>responsable >>> >> > >>>es >>> >> > >>> CODEOSCOPIC S.A. La finalidad de dicho tratamiento es >>>facilitar la >>> >> > >>> prestación del servicio o información solicitados, teniendo >>>usted >>> >> > >>>derecho >>> >> > >>> de acceso, rectificación, cancelación y oposición de sus datos >>> >> > >>>dirigiéndose >>> >> > >>> a nuestras oficinas c/ Paseo de la Habana 9-11, 28036, Madrid >>>con >>> >>la >>> >> > >>> documentación necesaria. >>> >> > >>> >>> >> > >>> >>> >> > >> >>> >> > >> >>> >> > >>-- >>> >> > >> >>> >> > >>Carlos Rovira >>> >> > >>Director General >>> >> > >>M: +34 607 22 60 05 >>> >> > >>http://www.codeoscopic.com >>> >> > >>http://www.avant2.es >>> >> > >> >>> >> > >> >>> >> > >>Este mensaje se dirige exclusivamente a su destinatario y puede >>> >> contener >>> >> > >>información privilegiada o confidencial. Si ha recibido este >>>mensaje >>> >> por >>> >> > >>error, le rogamos que nos lo comunique inmediatamente por esta >>>misma >>> >> vía >>> >> > >>y >>> >> > >>proceda a su destrucción. >>> >> > >> >>> >> > >>De la vigente Ley Orgánica de Protección de Datos (15/1999), le >>> >> > >>comunicamos >>> >> > >>que sus datos forman parte de un fichero cuyo responsable es >>> >> CODEOSCOPIC >>> >> > >>S.A. La finalidad de dicho tratamiento es facilitar la >>>prestación >>> >>del >>> >> > >>servicio o información solicitados, teniendo usted derecho de >>> >>acceso, >>> >> > >>rectificación, cancelación y oposición de sus datos dirigiéndose >>>a >>> >> > >>nuestras >>> >> > >>oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la >>> >>documentación >>> >> > >>necesaria. >>> >> > > >>> >> > >>> >> > >>> >> >>> >> >>> >> -- >>> >> >>> >> Carlos Rovira >>> >> Director General >>> >> M: +34 607 22 60 05 >>> >> http://www.codeoscopic.com >>> >> http://www.avant2.es >>> >> >>> >> >>> >> Este mensaje se dirige exclusivamente a su destinatario y puede >>>contener >>> >> información privilegiada o confidencial. Si ha recibido este mensaje >>>por >>> >> error, le rogamos que nos lo comunique inmediatamente por esta misma >>> >>vía y >>> >> proceda a su destrucción. >>> >> >>> >> De la vigente Ley Orgánica de Protección de Datos (15/1999), le >>> >>comunicamos >>> >> que sus datos forman parte de un fichero cuyo responsable es >>>CODEOSCOPIC >>> >> S.A. La finalidad de dicho tratamiento es facilitar la prestación >>>del >>> >> servicio o información solicitados, teniendo usted derecho de >>>acceso, >>> >> rectificación, cancelación y oposición de sus datos dirigiéndose a >>> >>nuestras >>> >> oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la >>>documentación >>> >> necesaria. >>> >> >>> >>> >> >> >>-- >> >>Carlos Rovira >>Director General >>M: +34 607 22 60 05 >>http://www.codeoscopic.com >>http://www.avant2.es >> >> >>Este mensaje se dirige exclusivamente a su destinatario y puede contener >>información privilegiada o confidencial. Si ha recibido este mensaje por >>error, le rogamos que nos lo comunique inmediatamente por esta misma vía >>y >>proceda a su destrucción. >> >>De la vigente Ley Orgánica de Protección de Datos (15/1999), le >>comunicamos >>que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC >>S.A. La finalidad de dicho tratamiento es facilitar la prestación del >>servicio o información solicitados, teniendo usted derecho de acceso, >>rectificación, cancelación y oposición de sus datos dirigiéndose a >>nuestras >>oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación >>necesaria. >
