This content has been marked as final. Show 7 replies
Sorry you're disappointed. We're looking at adding more refactoring support into Flex Builder in the next version but we simply couldn't fit more in with all of the other work we're doing. As I mentioned on my blog a few days ago you'll be able to vote on deferred bugs very soon.
I agree with you, those of us that come from SW Engineering/Programing development background and have long experience with the evolution of IDEs for other programing languages ( Java/C/C++ / C# ...) and systems learn to expect certain "Obvious" features. Maybe for Flash/Web designers that have been less exposed to a full blown systems ( with thousands of source files) large teams and several years of SW development/maintenance cycles the lack of these features are less "Obvious".
I hope that eventually Adobe will realize that to successfully win over SW Developers with FB3 they'll have to at least match the "Obvious " features. Unfortunately, I believe that by releasing a platfrom/IDE with some "glaring" gaps would immediately turn SW Developers off. Especially those who are involved with large systems / applications & teams.
I had similar issue with a simpler (somehow related) feature of logging all the Find/Replace in "current file " see: http://bugs.adobe.com/jira/browse/FB-11690
Anyway, hope by voicing our opinion we are helping Adobe steer the development in the right direction ..
Agreed, But there you go.
I just hope that, as with many applications, there will be partial (ie - free) .xx updates where some of these features could be implimented. I suppose it's always a case of we want it released now, and with everything we need. As we are all developers here we know the score. there are always going to be a limited number of things that can be included within the given development time. (i do however agree that this one is a biggy).
onwards and upwards, it'll get there. It's up to us to stick with the platform and it's shortcomings and help push these features forward. I'm also sure that the developers are as gutted as us at some of the features that have had to be 'deferred' in order to get the boxes into the shops.
I don't mean to sound ingrateful or anything, but I really do think that even a significant delay would have been worth the effort. Without this feature, I'm having a hard time deciding whether going from 2 to 3 is worth it.
As an example, yesterday I just spent probably 30 - 45 minutes removing some code that accidentally used deprecated classes. Grrr!
Hopefully this is the first thing homed in on for improvements after 3 is released... it'd be awesome if it was released as a patch update, too, instead of something for version 4.
patch update - now that's an idea!
Yeah I'd definitely upgrade if we were told that it'd be "patched in", not sure otherwise.