On Tue, Jul 10, 2012 at 4:40 PM, Jeffry Houser <jef...@dot-com-it.com>wrote:
> What you're proposing here is different than the original suggestion, but > I believe in the same spirit. Anyway, I can probably be sold on the > benefit of such a tool, I'm not sure if such a tool belongs in the Flex > SDK, but I'm not sure. It is different than his original suggestion, but only slightly. I was looking to the spirit of his request which is a good one. Think of it like an integrated Tour De Flex. I was mainly pushing to slow people down and think about the positives of the idea rather than just hanging onto specific points. We should be looking for solutions to common problems and letting people have the support to make those solutions. Sometimes support means giving back ideas and small course corrections. Though I love Ruby I'm not going to put it into Flex - but there are really good ideas over there that are usable. If someone wants to run with this idea then great. When some code is completed then we can talk about if it goes into Flex or not. Just saying no at the beginning isn't helpful to anyone. -- Jonathan Campos
