incubator-flex-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeremy Tellier <>
Subject Re: [RT] Design View in FlashBuilder
Date Fri, 17 Feb 2012 15:53:38 GMT
"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

On Fri, Feb 17, 2012 at 6:29 AM, Erik Lundgren <> wrote:

> 17 feb 2012 kl. 11.48 skrev jude:
> > [1]
> > [1] - read the notes -
> Would love to see it, but browser tells me it can't find it.
> /Erik

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message