I've been coding Flex apps since '06 and started to use design view to bump things around only about 6 mos ago.
It has improved my workflow. I can't imagine not using it anymore. I do however toggle Enable Design View on when needed. Jack On Feb 16, 2012, at 10:25 AM, Nicholas Kwiatkowski <nicho...@spoon.as> wrote: > I've been developing Flex applications since 2005, and yes I still use the > Design View. My workflow usually consists of mocking up an application > quickly and getting customer sign-off on a non-functional UX prototype. > It's not about dragging-and-dropping stuff onto the stage, but rather > making sure they line up, look cohesive, and have a good UX feel. (Does > this button look better with 10px spacing, or 12? Is 100px enough space > for this button including the icon and text? If I only have 150px width > for my app, do three buttons look too crowded?). Once the UX is signed > off, then I go into code view and never look back. > > But for that case, it make the tool for me. There are so many other tools > that are much better at straight ActionScript -- but some of the design > view and other small things that I expect to be cut based on these > announcements are what keep me in Flash Builder. > > On another related note, it looks like there is a plugin being developed > for IntelliJ that will fill this gap. It won't allow drag-and-drop, but it > will have a live-preview of your MXML so you can quickly see what some of > those changes will do without having to wait through a complete compile for > each iteration. > > -Nick > > On Thu, Feb 16, 2012 at 9:55 AM, Yousif Atique <atique.you...@gmail.com>wrote: > >> I would agree that design view is great for a very new beginner but for >> someone who has got at least 2+ years of RIA experience, s/he wouldn't want >> to get into the business of dragging and dropping controls just like how it >> was done back in VB days.... one would want to understand and >> learn/memorize different properties (along with their respective possible >> vales) to get his/her dirty with deep down details. >> >> In the past 4+ years, I haven't come across anyone who loved this feature >> religiously. And, need not to mention that design view is super slow if you >> try to make FB read an existing screen... >> >> No offense to anyone and with all respect to all, personally I think >> 'squeeze is not worth the juice'.... >> >> Regards, >> On Feb 16, 2012 9:24 AM, "Jeremy Tellier" <jeremytell...@gmail.com> wrote: >> >>> I agree, I use design view to quickly mock up what needs to be on the >>> screen, then jump into code for refinement. I was miffed when they >> dropped >>> the CSS designer as I had a crew of non-technical designers creating >> skins >>> for my apps that were left high and dry when that occurred. Why does >> Adobe >>> just drop features left and right? Remember when Dreamweaver had Java and >>> DotNet Support? ;) >>> >>> Thanks, >>> Jeremy >>> >>> -----Original Message----- >>> From: Eugene Diana [mailto:edi...@myersinfosys.com] >>> Sent: Thursday, February 16, 2012 9:19 AM >>> To: flex-dev@incubator.apache.org >>> Subject: [RT] Design View in FlashBuilder >>> >>> Last night at the Boston meeting I was surprised to see that almost none >> of >>> the participants take advantage of the Design View (which Adobe will drop >>> from FB).as a relative beginner, I find it quick and easy to build a >> screen >>> (we have many in our app, and it is very data-driven).what am I missing? >>> What method is easier than simply dragging the components to the spot >> where >>> you want them, aligned and sized the way you want? >>> >>> >>> >>> Thanks much, >>> >>> Eugene >>> >>> >>
