Reputation: 19735
I asked this question:
Can Flash Builder with Flex mobile drag and drop controls for mobile apps in the design view?
One of the responses comments said the design view was going away.
Why would Adobe remove this? How can you design without it? I know you can position things in the source code but it seems like it'd be much quick to at least build the layout graphically. Why not have something like this:
http://developer.apple.com/technologies/tools/whats-new.html#interface-builder
I was interested in the Adobe products for flex mobile but it would take me much longer to position and set things right without the drag and drop of controls. I'd like to concentrate on the business part of the project.
Thanks.
Upvotes: 2
Views: 3729
Reputation: 113976
Flex Builder Alternative
There's a new Visual Studio based desginer for Flex apps for all the flex designers out there. Its called Amethyst and its supports visual designing of Flex forms and debugging and stuff. If you don't have VS you can grab a free version (google "visual studio express").
I've checked out the trial with Visual Studio 2012, and my review is as follows:
If you come from a Flash Builder background:
If you come from a FlashDevelop background:
So my conclusion is : if you come from a Flash Builder background and you need the visual designer then by all means use this. If you come from FlashDevelop background, steer clear of this horrid code editor!
Upvotes: 1
Reputation: 62769
I'm guessing with all the different screen sizes and rotations the builder just became impractical. With designers the best way to handle different screen sizes is often to create a new screen for each size. Now we are up to hundreds of size/rotation combinations it could be that the designer view just isn't the right way to go.
In java every group I've worked with (or discussed the issue with) that has used a swing GUI builder has eventually reverted to layouts in code to deal with 2-way problems, screen resizing issues and forward/backward/lateral compatibility (tool updates or moving across to different visual designer tools).
On top of that, the design view of 3.6 continually destabilized our eclipse sessions--you could work in design view for 3 files over an hour or so before eclipse would crash. It's possible they couldn't overcome the bugs or decided it was too much trobule.
Upvotes: 2
Reputation: 370
Probably due to the new focus which seems to be on "gaming", i.e. perhaps abandoning one of the core developer groups (intranet/business). It also was (as Adobe says) not the most stable part of the IDE, so it would probably have required a rewrite & much testing to assure it works with Apache Flex 4.8.
Also, perhaps the myth that "nobody uses design view" (apparently there are a lot of "nobodies") finally took hold. The myth should have been: "nobody who isn't designing a complex form or application uses design view". (Excuse the double negative..)
A number of vocal people want to promote their own feature requests over those of other people, so they downplay the need or usefulness of the features they don't use or need. Yeah, it's easy to go without design view if you're only developing components, or if you're designing mobile apps to fit on a 2 inch screen... too bad Flex is about 1000% more ideally deployed in an Intranet PC environment.
No design view means I'm probably not a Flex developer moving forward, unless some alternative appears. JavaFX is looking nice, nowadays.
Upvotes: 1