A number of you voted for us to invest in improving the profiler in Flex Builder. So, what, exactly, should we improve? I'd love your thoughts. Here are a few ideas to get things started...
Thanks for all the feedback on the $100 test. From about 50 responses in comments and emails, here's a few facts:
I'll keep you posted on more submissions as well as how this data informs our feature prioritization.
Tim
The next version of Flex Builder will include significant investment in what we've been calling "IDE maturity" features. These are features that either build on features introduced in FB3 (e.g. profiler, refactoring, debugging), or new features that are intended to increase the productivity of advanced users. There are certain features that professional developers have come to expect in an IDE and, currently, Flex Builder lacks some of them.
Unfortunately, the list of potential features in this area is long. Really long. Far longer than we can deliver in a single release. So we've been working at prioritizing the list; trying to figure out what of the most critical features we can sign up for in the time we have for the release. We've visited with customers, read the bugbase, scrubbed the forums, and more, but I'd still like to get a bit more data. That's where you come in...
I'd like to invite any existing Flex users to take our IDE maturity "$100 test." This is a feature prioritization exercise that I find very useful. Essentially, you get an imaginary $100 to spend on the development of a set of features. If there's one feature you need above all others, feel free to put all $100 on that one. Otherwise, you might put $25 here and $40 there - just make sure that you add up to a total of $100.
Following is a list of some of the possible features. Take a look and then use the comments (or send me an email) to let me know how you'd spend your $100. You can certainly add your own feature ideas, but bear in mind that 100 little features each give $1 will be less useful.
Sorry for the low-tech implementation of this exercise. If anyone wants to build a nice little $100 test app, feel free! I'll try to find a nice reward for you...
Here goes, and thanks in advance for your input.
So your list might be something like:
Right? OK, have fun!
