Hi Alex, 2015-07-29 18:20 GMT+02:00 Alex Harui <aha...@adobe.com>:
> Hi Carlos, > > I agree that making it easier to get started is important. It would be > great if you can find time to try the latest builds once the build server > comes up. I think we fixed the SDK dependencies in the binary package. > Building from the source will probably always require other upstream > sources/repos, however. > yeah, I'd like to test, and I'd get some free time in a few days I enter on vacation period. > > If you have ideas for a simple HTTPService/REST/JSON sample that you think > would be a killer example for us to include, please provide more details > so we can ponder whether to delay the release or just ship what we have > and focus on things like that for the next release (which will hopefully > not be a year from now, probably a couple of months). > The data communication I was talking about was relating to feathers (I want to expose how easy it was for me to get up and running) The main key point for me is getting FlexJS get rid off any complication and get as smooth installation as we could get, so people entering FlexJS world could get a package and start testing this technology in few minutes. So in the end some folks could go further and start contributing. The key is...if people (like me) that loves this technology but has very few time, can't get his hands dirty is why the setup complexity is very high. We should be able to lower the barrier in this release (no more things, please, only remove configuration things, additional environment setup,...) People should be running with no other things installed or configured... > > I’m going to spend the rest of this week polishing the examples we do > have. New in this release will be the FlexJSStore example which does grab > JSON data from a local file. I think I’ll also spend time on the Windows > install since I think it often doesn’t find Java correctly. And, of > course, volunteers are welcome to pitch in. > -Alex > > On 7/29/15, 7:51 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira" > <carlos.rov...@gmail.com on behalf of carlos.rov...@codeoscopic.com> > wrote: > > >Hi Alex, > > > >from my point of view I want to share some thoughts about what I would > >expect from a new release. > > > >I little background first please: Things are going very fast out there, > >with Polymer reaching 1.0, people exploring ReactJS, AngularJS 2 coming, > >Coffescript/Frame doing some cool and simple screens... Dart+PolymertDart > >is the preferred combo for people that search something like Flex in > >HTML5/JS... > > > >And in our side we had a great effort in FlexJS, and aside (since is not > >in > >this project), but is completely related, Josh add MXML to feathers and > >now integrated FlexJS and CreateJS in a very cool experiment. > > > >Now going to the point: One thing I liked so much was the ease of testing > >that Josh made in the feathers/MXML 2 beta. I could download and test it > >to > >take a real taste of what is going on. For me the framework is very cool, > >but it could not find resources or examples of data communication (AMF, > >REST, JSON,..). So in few hours of testing and searching I have a clear > >idea now of feathers, and I liked it, (but in TI enviroments it needs a > >companion project that manages some version of HTTPService, RemoteObject, > >web Services,...) > > > >In FlexJS, I would expect the same ease of testing so people could enter > >the game. In my case, I have many difficulties to get my hands dirty, but > >my passion for this technology makes me continue following it. But, for > >others, it's not the case. We need to make things more easy to get > >started, > >and that's what I would expect from a new release...something I could > >donwload, install and test (no environment variables to configure, no > >tricky steps that makes me reach out of time and wait for another day to > >continue figuring how to get things work. > > > >For, example, I know some months ago FlexJS is not requiring Flex SDK > >anymore...but I was testing it and I find I need it!. > >I think we have lots of complexity, and I would ask here that the effort > >to > >make the release would be driven towards making the release much more > >friendly so people could taste it, love it, and want to contribute. > > > >I think there's much more peple out there like me that want to help, but > >maybe because there's few time to invest or maybe by the complexity of > >things, we end throwing the towel without reaching the point of get the > >environment set up correctly since there's many things involved. > > > >We would need first to make things more simple, already configured, > >without > >the need to manualy set up variables that some people could set up wrong > >and get lost in the process. > > > >Just my thoughts on this from a point of view that someone that is > >following the project closely although my last contribution was several > >months ago. > > > >Thanks for reading > > > >Best, > > > >Carlos > > > >2015-07-29 16:44 GMT+02:00 Héctor A <neverbi...@gmail.com>: > > > >> I agree with Michael, just release it ASAP, seeing an actual release, > >>even > >> if it has problems, will motivate some people out there and will let > >>others > >> know that FlexJS is alive, of course then part of that same people will > >> complain that the release has bugs, but that's a different fight. > >> > >> On Wed, Jul 29, 2015 at 4:32 PM, Michael Schmalle < > >> teotigraphix...@gmail.com > >> > wrote: > >> > >> > Release it, the externs code is tested. :) JK but seriously, FlexJS > >>and > >> JSC > >> > needs to get out on a real release not just nightlies, especially > >>since > >> > Josh just "tested" the externc compiler with his project. > >> > > >> > Mike > >> > > >> > On Wed, Jul 29, 2015 at 9:55 AM, Alex Harui <aha...@adobe.com> wrote: > >> > > >> > > Hi, > >> > > > >> > > It’s been too long since the last release, but I think we are at or > >> near > >> > a > >> > > good stopping point for the next release. The default UI looks > >>better, > >> > > you can swap in a theme for many components, the layout subsystem is > >> > > working better, etc. > >> > > > >> > > Is there anything else we “must” put in the next release? I was > >>going > >> to > >> > > put off the rewrite of our handwritten JS to use the JS externs to a > >> > > future release but I am open to waiting until that gets done as it > >>will > >> > > test the externs code we have now. > >> > > > >> > > Thoughts? > >> > > -Alex > >> > > > >> > > > >> > > >> > > > > > > > >-- > > > >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/ Tres Creus, nº 104, 2-1, 08202 de Sabadell (Barcelona) 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/ Tres Creus, nº 104, 2-1, 08202 de Sabadell (Barcelona) con la documentación necesaria.
