Like Justin said, I don't have special powers. I do have the luxury of working on this stuff full-time though.
You are not the first person to ask about a roadmap for FlexJS. The fact is, with this group of volunteers and only a few full-time folks, it is hard to predict the future. If we get an alpha-level release out soon and dozens of folks jump in to help, it would totally change the game. If it remains a few full-timers and a few volunteers and everyone else just sits around waiting like you had to do in the Adobe days, it will take us a lot longer. Regarding localization, someone mentioned Pootle. Apache has a Pootle service. I took a brief look and it looked like it would take time to set up, so I passed on it for now. But if it would help in the end and someone has the energy to try to make it work for us, that could also make a big difference. So, it is great to hear what folks want, but the best way to get it is to do it yourself. That's a huge key difference from the Adobe days, but it has the great advantage that what you want will never get deferred or cancelled because scheduling reasons or corporate strategy changes. If you and/or some others can write the code it can be in the next release. -Alex On 3/13/14 8:34 PM, "Justin Mclean" <jus...@classsoftware.com> wrote: >HI, > >> I got the idea: contributors decide the future of flex, that's really >>cool, I'll spread the word to the people I know, and see if anyone could >>do a thing or two. >Much appreciated. > >> And by the way, what's Alex's opinion about this? He is the mentor >>from Adobe. >He's actually the PMC chair, not a mentor. I'm sure he can speak for >himself but don't think he would disagree with anything I said in that >email. > >Thanks, >Justin
