on AIR Weblog

Flex Builder 3: Winsha Chen on Design View

June 10th, 2007 by Lee Brimelow

Winsha Chen describes some of the new Design View features in Flex Builder 3.

This entry was posted on Sunday, June 10th, 2007 at 7:53 pm and is filed under flex, flex builder. Both comments and pings are currently closed.

6 Responses to “Flex Builder 3: Winsha Chen on Design View”

  1. On June 10th, 2007 at 8:02 pm, Faisal Abid wrote:

    GREAT JOB ! Moxie is sexy!

  2. On June 10th, 2007 at 9:39 pm, Rashmi wrote:

    Superb feature. This makes working with CSS very easy.

  3. On June 10th, 2007 at 9:40 pm, jonnymac blog » Flex 3 Beta Link Round-Up wrote:

    [...] has five new videos posted showing the new features of Flex Builder 3 including Design View, Refactoring, Importing Skins, and Multiple SDK Support, as well as a video from Mike Chambers [...]

  4. On June 12th, 2007 at 7:22 am, Quantium wrote:

    Good visual integration. this makes working with CSS fast and easy

  5. On June 14th, 2007 at 3:07 pm, Peter wrote:

    While Flex Moxie has a lot of cool new enhancements for designers, and a lot of effort has been put into CSS design view & other skin/gfx import magic, there’s still a critical feature missing: Design Time CSS (just like in Dreamweaver).

    As long as you don’t link to the same global gfx.css in the many mxml files a Flex Builder project can have, you won’t see the styles in action while developing a certain mxml file. You have to put “mx:Style source=”gfx.css” in every mxml file in order to get the real WYSIWYG design view experience. A finished project just needs one link to gfx.css in order to get compiled, not in every mxml file.

    I currently have a project with over 50 nicely designed mxml files all sharing one global gfx.css. The compile time & swf filesize difference is enormous between a project which only has one reference to “mx:Style source=”gfx.css” or 50. The compile time can be up to 10 times longer, while the filesize triples, for no reason at all. The compile time in Flex 3 M2 doesn’t show any difference for this project.

    My current workflow is therefor a manual hassle of adding and removing “mx:Style source=”gfx.css” lines in the many mxml files, just to speed up and optimize compiling.

    So, being able to just use a or multiple specific CSS file(s) during design view on a single mxml file or global Flex project, which will be ignored when compiling, is a much needed feature for designers/developers, in order to solve the above issues.

    Go have a talk with the DreamWeaver team, they know exactly what I mean :) .

  6. On July 27th, 2007 at 9:45 am, ScaleNine Blog » Blog Archive » The Days Are Flying By wrote:

    [...] great and a lot of the themes featured here have filtered out into a number of Flex projects and Adobe demonstrations. As I’ve been busy, other individuals in the community have contributed to some of the free [...]

Trackback URI