Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of jackringg@gmail.com designates
 209.85.210.175 as permitted sender)
Received-SPF: pass (google.com: domain of jackringg@gmail.com designates
 10.42.175.5 as permitted sender) client-ip=10.42.175.5;
Subject: Re: Adobe might think of open-sourcing the Design View if there is
 sufficient interest
References: <73EAD4BA8D3A4DBB98C28857CB669C70@KORODESKTOP>
 <D5D58A73C6CD4AC5AB5B08E5A815931B@KORODESKTOP>
 <CALFuuO23yeRApPNAS1d-phGSX_UDUbLcy2rgEnzb9x_FH1wvCQ@mail.gmail.com>
From: Jack Ring <jackringg@gmail.com>
Content-Type: text/plain;
	charset=utf-8
In-Reply-To: 
 <CALFuuO23yeRApPNAS1d-phGSX_UDUbLcy2rgEnzb9x_FH1wvCQ@mail.gmail.com>
Message-Id: <55884A77-EA27-48F7-B97B-160AE55407E6@gmail.com>
Date: Wed, 22 Feb 2012 09:17:41 -0500
To: "flex-dev@incubator.apache.org" <flex-dev@incubator.apache.org>
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (1.0)

+1 for design view.

On Feb 22, 2012, at 9:08 AM, Pepe <pepe.fxug@gmail.com> wrote:

> +1 for Design View
>=20
> 2012/2/22 Dimitri k. <koro@noos.fr>:
>> After the discussion on the ML about the Design View, I thought it would b=
e
>> a good idea to ask Deepa at the Flex Paris meeting if Adobe could conside=
r
>> to open-source it after the removal from next version of Flash Builder.
>> Fr=C3=A9d=C3=A9ric Thomas, also on the ML, was quicker than me and ask De=
epa about
>> that.
>> She said that Adobe hasn't thought about it because they didn't believe w=
e
>> were interested, but she was thinking it could be a good idea.
>> In fact, the Design View is a Flex app, so the community can easily
>> contribute to it, and legal scrubbing should not be such a drag.
>>=20
>> She concluded that the best thing to make it happen would be to show
>> interrest for the open-sourcing of DV on this list.
>>=20
>> I know that lots of people don't care about the Design View (I rarely use=
 it
>> myself), but here are 4 reasons I think it could be a good move for Apach=
e
>> Flex:
>>=20
>> - DV is a great tool to understand the MXML paradigm, particularly for
>> people coming for a Flash Pro background (timeline+stage), and its remova=
l
>> would increase the barrier of entry to Flex.
>>=20
>> - I heard several times about devs for which the DV is central to their Fl=
ex
>> workflow. It's often the case for heavy form-based application, where
>> standard Flex components are use exclusively and the Design View help
>> avoiding "design re-compilation".
>> In fact, I was told by an Adobe enterprise evangelist that he sold Flex t=
o
>> some big companies mainly because of the Design View and the ease they se=
e
>> in it to train their employees.
>>=20
>> - DV can be really helpful when designing Mobile apps, because you can te=
st
>> quickly your design with different resolutions and orientations
>>=20
>> - If we have access to the Design View code, maybe we could improve it in=
 a
>> way that even current Design View haters would use it ;)
>>=20
>> Dimitri K.