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 masuland@gmail.com designates
 209.85.214.47 as permitted sender)
From: Sebastian Mohr <masuland@gmail.com>
Mime-Version: 1.0 (Apple Message framework v1084)
Content-Type: multipart/alternative; boundary=Apple-Mail-3--627003591
Subject: Re: Apache Flex GUI Designer tools
Date: Tue, 2 Oct 2012 18:21:07 +0200
In-Reply-To: <58806CB1-1D6A-4615-90EA-015D8650AFB6@gmail.com>
To: flex-dev@incubator.apache.org
References: <CC9067FF.2ED9%pent@adobe.com>
 <20121002101316.104018d2e55r0ha4@www.teotigraphix.com>
 <58806CB1-1D6A-4615-90EA-015D8650AFB6@gmail.com>
Message-Id: <9F81F877-CB08-4D64-A2FC-4ACD7AF59429@gmail.com>

--Apple-Mail-3--627003591
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Forgot to mention those links about Adobe Brackets [1] [2].=20
So, when seeing this, it seems to be very easy that Adobe=20
loves to collaborate with the HTML5 folks. What about an=20
open GUI designer tool for Apache Flex?


Sincerely Yours,

Sebastian Mohr
Apache Flex Developer (PPMC), =20
Interaction Designer & Musician
http://www.linkedin.com/in/masuland

[1] http://www.youtube.com/watch?v=3DxirIHMtpc4c
[2] =
http://www.adobe.com/devnet/html5/articles/bracket-code-architecture.html


On Oct 2, 2012, at 5:55 PM, Sebastian Mohr wrote:

> @Peter Ent ... the missing piece is: Who is working on=20
> such a design tool right now? There are Apache Flex=20
> designers and developers on this mailing list that see=20
> the need to have those tools.
>=20
>> You know, if I was actually making some type of money from Flex right =
now I would consider this project [...]
>=20
>=20
> As Michael Schmalle correctly pointed out: There are=20
> probably people on this list that are capable of building=20
> those GUI designer tools, but, most probably they won't
> have the time and money to work on that.
>=20
> @Adobe ... what's wrong with continuing building GUI=20
> designer tools for Apache Flex? Is that really something=20
> that is not worth investing into? You already created those=20
> tools. So, why not sharing some of your expertise with the=20
> community, and, not locking your code in the archives of=20
> Adobe history?
>=20
> I also doubt, that building such Apache Flex GUI designer=20
> tools would be hardly manageable by a single person alone.=20
> Maybe Adobe could consider to open up some of their GUI=20
> designer tool code on Github and collaborate with the=20
> Apache Flex community, just like they are doing right=20
> now with Adobe Brackets [1] !?
>=20
>=20
> Sincerely Yours,
>=20
> Sebastian Mohr
> Apache Flex Developer (PPMC), =20
> Interaction Designer & Musician
> http://www.linkedin.com/in/masuland
>=20
> [1] https://github.com/adobe/brackets
>=20
>=20
>=20
>=20
> On Oct 2, 2012, at 4:13 PM, Michael Schmalle wrote:
>=20
>> I was going to say the exact same thing.
>>=20
>> I think why people have not said this is because a lot of developers =
are used to a design view being located "inside" their IDE as with =
Design View.
>>=20
>> This is definitely not that hard to do, back in the Flex 2 days I =
experimented in creating such tools in Flex.
>>=20
>> Thinking about it, I guess FlashCatalyst "wasn't" in and IDE perse =
so, the paradigm of an external editor has been around.
>>=20
>> Seeing as Google's Android design view is decent in Eclipse, I don't =
see why something couldn't be started in an IDE either.
>>=20
>> The trick is starting with something SMALL and prototype, get the =
idea to work and slowly build on. You know, if I was actually making =
some type of money from Flex right now I would consider this project =
but, my spare time will be devoted to the compiler and extensions of.
>>=20
>> Now if we get some revolution going with AS -> JS compiling that is =
not using the Flash API, then it's time to really start thinking about a =
design inspector. ;-)
>>=20
>> Mike
>>=20
>>=20
>> Quoting Peter Ent <pent@adobe.com>:
>>=20
>>> This is a good opportunity for [someone in] the Apache Flex =
community to
>>> develop such a tool. Using Apache Flex, an AIR app would be able to
>>> present UI components rendered correctly, in real-time, and be able =
to
>>> read and write local files. If Adobe does not contribute UI tools, =
the
>>> community can make their own. There are many talented people here =
with the
>>> background to do this. Of course, time and resources are probably =
the
>>> biggest constraints.
>>>=20
>>> Peter Ent
>>> Flex SDK Team
>>> Adobe Systems.
>>>=20
>>> On 10/2/12 6:52 AM, "Michael Schmalle" <apache@teotigraphix.com> =
wrote:
>>>=20
>>>> Quoting Sebastian Mohr <masuland@gmail.com>:
>>>>=20
>>>>> Nope ... I am seeing Flash Catalyst as being the representation =
for
>>>>> Adobe's work on the Spark-Component model, FXG and Flash Catalyst
>>>>> (formerly codenamed Thermo) with the Designer-Developer workflow
>>>>> started in 2007 [1]. For whatever reasons it took ages to finish =
it.
>>>>=20
>>>>=20
>>>> For the same reason the Spark component set isn't finished and the
>>>> same reason why Flex is now an Apache project and the same reason =
why
>>>> they axed design view in Flash Builder and the same reason they
>>>> renamed Flex Builder to Flash Builder.
>>>>=20
>>>>=20
>>>> --
>>>> Michael Schmalle - Teoti Graphix, LLC
>>>> http://www.teotigraphix.com
>>>> http://blog.teotigraphix.com
>>>>=20
>>>=20
>>>=20
>>=20
>> --=20
>> Michael Schmalle - Teoti Graphix, LLC
>> http://www.teotigraphix.com
>> http://blog.teotigraphix.com
>>=20
>=20


--Apple-Mail-3--627003591--