2017-01-13 19:11 GMT+01:00 Alex Harui <aha...@adobe.com>: > > > IMO, there are at least some existing Flex apps that don't use AMF. Now > it may turn out that we will have AMF shortly, but until it is done, those > who don't need it can start migrating their apps today. Some folks are > already migrating.
I don't think so. For me flow data comes first and then other things. Without server connection I think almost no people will start migrating. People even can start a wireframe ugly project, but seeing data is coming and they can sent data. Then will come themes, and other eye candy things... > I will believe that AMF is used by the vast majority > of Flex apps, but as I said upthread, we simply need to attract more > committers/contributors to really get FlexJS off the ground. Some folks > believe that declaring something as 1.0 will invite more folks to try it > and thus get involved. I don't think so. React and others are in 0.15?...and they attract all devs. If we put some groundbreaking examples and say "hey! this is Flex and we have a cool component set, modules, AMF..." People will start then to think in us seriously. Until then we don't have to much to captivate people coming... > I don't have a strong opinion, but that sounds > like a reasonable approach, and better than telling folks not to try > FlexJS for another year or two and wait for the few of us who are active > committers to reproduce all of these killer features that a much larger > team of full-timers did at Adobe over many more years. > I think that people will start to join as they can work with flexJS. we need a set of capabilities that make people could use us in their Apps We are near, but not still there. and the people that we can't attract more are the people that has old flex apps as Chris said. > > Flex 4 had many more features than Flex 3, which had more features than > Flex 2 which had more features than Flex 1.0. FlexJS 1.0 may only allow a > small percentage of Flex customers to migrate, but again, if that brings > in new contributors we can handle more Flex customers with FlexJS 2.0 and > so on. > Flex was popular in 2005 when Adobe bought Macromedia and invest money to make Flex 2.0. That was for me the vortex that make people change from crappy html/js to Flex/swf > > There may also be a way to get traction with new customers and new apps as > well by trying to get attention from Cordova developers, CreateJS > developers, etc. All people I hear talking about Cordoba says "it's crap" and CreateJS is not very popular...I think we should not see in that direction since is not the excellence we can reach to be "the top" tech out there. > I don't care who gets to production first, whether it is > a new app or migrated app, but mainly, I think a testimonial is what we > really need since we don't have a budget for marketing. So when folks > show up with a need in order to get to production, I will try to help them > out. > For me get the 1.0 state is not related to see a guy or a team that say us "hey! I made a FlexJS app and I have in pro"...mmm...definitely no. I see that we are not 1.0...we all see that. We see that we are getting great advances to that path, but for 1.0 means "the minimum set of things that allows me to make a FlexJS app" and that means crafting an interface with controls and layouts (buttons, text inputs, lists, ...), break into parts (modules) and communicate with server (AMF). That marks a round circle come from the user browser and go to the server and come back with something to the user again... and all of that with great "flex" productivity :) > > -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/ Paseo de la Habana 9-11, 28036, Madrid con la documentación necesaria.
