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: local policy)
From: "christofer.dutz@c-ware.de" <christofer.dutz@c-ware.de>
To: "flex-dev@incubator.apache.org" <flex-dev@incubator.apache.org>
Date: Wed, 3 Oct 2012 19:21:29 +0200
Subject: AW: AW: Financing the Design View AIR App (Was: Re: Design View AIR
 App)
Thread-Topic: AW: Financing the Design View AIR App (Was: Re: Design View
 AIR App)
Thread-Index: Ac2hSbQusyv6SrXyTpC1fxBzS06XsgAKlcgwAAOrMvUAAf8xoA==
Message-ID: 
 <66E38C42347D6446BF7FCB22C3D3878072DE7C7A8C@ECCR06PUBLIC.exchange.local>
References: 
 <66E38C42347D6446BF7FCB22C3D3878072DE7C7A78@ECCR06PUBLIC.exchange.local>
 <CC91B363.46AE1%aharui@adobe.com>
In-Reply-To: <CC91B363.46AE1%aharui@adobe.com>
Accept-Language: de-DE
Content-Language: de-DE
acceptlanguage: de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Well isn't it usually that way around?

I create some general UI scetches using some tools like blamiq mockups and =
deal with negoitating the functionallity with my customers. As soon as the =
component works as desired I go "pimp my app" and give it to a designer to =
have it pimped.=20

Using Catalyst this was really easy (As soon as you had a desiger at hand t=
hat was used to it and it's concepts). I was even able to let the designer =
skin a running application deployed by me somewhere on the web, so I didn't=
 have give away the code of the application itself or setup the environment=
 at the designers office. This workflow was the major breakthrough for me a=
nd was one of the major things that made me shift allmost entirely to the F=
lex road.

It's a real pitty to have it dropped and wasted :-(


-----Urspr=FCngliche Nachricht-----
Von: Alex Harui [mailto:aharui@adobe.com]=20
Gesendet: Mittwoch, 3. Oktober 2012 18:18
An: flex-dev@incubator.apache.org
Betreff: Re: AW: Financing the Design View AIR App (Was: Re: Design View AI=
R App)


On 10/3/12 7:38 AM, "christofer.dutz@c-ware.de" <christofer.dutz@c-ware.de>
wrote:

> Oh ... let me thow in a little more weight for the Catalyst ;-)
>=20
> I invested quite some time in setting up a project structure that=20
> allowed me to concentrate on developing (Using an ugly but functional=20
> developer Skin) and having professional Designers use Catalyst to Skin th=
e application.
> Unfortunately it seemed that the designers available on the market=20
> were all even less "finished" than the Catalyst project, but as soon=20
> as the designers got the hang of it, the results were pretty=20
> sattisfying and I had what I was allways dreaming about: Being able to=20
> concentrate on the functionality and have a designer do all the stuff=20
> that sells the application (cool buttons, even greater effects and=20
> animated transitions, ...) :-)
>=20
> I would be really happy if Adobe didn't entirely drop this tool, and=20
> if they did, If they would somehow open-source it.
>=20
It is essentially "dropped".  See [1].   There are no plans to opensource
it.  It too had a lot of "baggage" that made it difficult to implement.  Fo=
r example, it really wasn't extensible as to what components it could handl=
e.

The principle behind it (that you can take designer art and break it down i=
nto components) is compelling, but I question whether it remains valid in a=
 world of dynamic UI.

It is also interesting to note that you used it in completely different way=
 than it was intended.  It was for a design-first-then-develop workflow and=
 you did it the other way (which is what I do when I have a choice as well)=
.

[1] http://www.adobe.com/devnet/flex/whitepapers/roadmap.html
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui