+1 for option 2. Least risky option. That whole code path needs lots of changes and testing.
I am worried if we would get peoole to vote in an another voting round. But, I will leave that up to the community. Om On Oct 20, 2012 8:12 AM, "Omar Gonzalez" <omarg.develo...@gmail.com> wrote: > Agreed, remove localization, release the app, and then bring back > localization in a new release and we can then do more extensive testing and > fixing, I'd vote #2. > > -omar > > On Saturday, October 20, 2012, Erik de Bruin wrote: > > > Hi, > > > > Om, first: sorry for changing my mind ;-) > > > > All, here are my thoughts: after careful reading of the VOTE thread I > > see three ways to continue: > > > > 1. release > > 2. remove localisation from first release > > 3. fix localisation (and maybe other issues) before first release > > > > I'm now changing my vote away from option 1 (however tempting) because > > I sure that we'll never get a second chance for a first impression. > > And first impressions are all that matter since we're trying to win > > back confidence in Flex as a viable software creation tool. > > > > I'm also not a big fan of 3. This would mean that we have to change > > around some stuff, and test the changes etc. I think this is more work > > that we'd do for a next release (in concert, maybe, with the next > > release of the framework, as Alex suggested). > > > > I would like to suggest that we go with option 2. This would (I think, > > without looking at the code) require only the changing of one line of > > code (setting the ONLY language option to en_US) and the setting of > > one property (hiding the option ComboBox from view). Minimal changes > > would allow us to cut RC8 really soon and get a new VOTE going... > > > > Thoughts? > > > > EdB > > > > > > > > -- > > Ix Multimedia Software > > > > Jan Luykenstraat 27 > > 3521 VB Utrecht > > > > T. 06-51952295 > > I. www.ixsoftware.nl > > >
