Agreed. This was one of the first things that caused me to adopt Flex 2 was the more than functional design view
_________________________________________________ On 2/17/12 11:05 AM, "Charles Monteiro" <char...@nycsmalltalk.org> wrote: >First of all, just moved to the neighborhood. > >I think you are totally on the money. Folks with the right background >understand how to exploit these tools and a UI design view is >indispensable. They provide a huge productivity advantage, folks not used >to them just don't get it. My core background is in VisualWorks Smalltalk >which has only been used for enterprise apps and in these circles its UI >designer is just integral to an iterative development rad process. > >Just this monday I went to a Flex meeting here in NYC. What I heard is >that >the Flex designer will go away in Flash Builder but what I also thought I >heard is that Adobe will not open source the UI designer. If that's true I >don't get it. They are going to get rid of it why not just give it away ? > >I hope I heard wrong and if not I hope Adobe reconsiders and open sources >the UI designer to Apache. > >thanks for listening. > >On Fri, Feb 17, 2012 at 10:53 AM, Jeremy Tellier ><jeremytell...@gmail.com>wrote: > >> "Design View" as a concept has made development tools very successful, >> there is a reason why Dreamweaver was always way ahead of other WYSIWYG >>and >> that is because it had a great, responsive design view, and an >>uncluttered >> code view. I worked with the original Flex team at Macromedia, simply >> providing input and have used Flex since its inception. I have also >> organized ridiculously large teams of ui designers, ux prototypers and >>ui >> engineers, etc and I find "design" time views to be a feature of a >>system >> that simply cannot be lost. >> >> In my experience most engineer types, usually that came from Java >>tooling, >> never feel they need a "design" view, it is not the "*experience*" >>level as >> some of us are extremely experienced and use the entirety of a toolset >>to >> our advantage. There is no real need to "remove" it, if it is there and >> people do not wish to use it... then don't use it. But why remove >>features >> from a product? It is so much easier to click "Design View" than to >>build >> your entire app and launch it to see how it looks. I have found that >>people >> raised from Visual Studio & even Macromedia tools seem more apt to take >> advantage of "design" views in their day to day routine and enjoy having >> the quick and easy ability to see at least a rough area of how >>components >> are fitting together. >> >> As for rapid prototyping, if Catalyst is gone (and it was never 100%) I >> would suggest my ux designers to use flash builder (100% design view). >> Balsomiq is cute for some things but not for large system prototyping. >> >> If it is simply that Adobe does not wish to provide improvements to >>their >> design functionality, throw up a "Cannot render" tag like dreamweaver >>does >> for unknown asp/jsp tags or better a properly sized "cannot render" >>box. At >> least people will be able to see relative positioning and a real >> "Enterprise" with design, ux, engineering, architecture, etc software >> departments can take advantage of the toolset as they see fit. >> >> My 2 cents >> Jeremy >> >> >> On Fri, Feb 17, 2012 at 6:29 AM, Erik Lundgren <e...@lndgrn.se> wrote: >> >> > >> > 17 feb 2012 kl. 11.48 skrev jude: >> > >> > > [1] http://www.radii8.com/ >> > > [1] http://www.radii8.com/demo/ - read the notes - >> > >> > Would love to see it, but browser tells me it can't find it. >> > >> > /Erik >> > >> > > > >-- >Charles A. Monteiro >www.monteirosfusion.com >sent from the road
