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 bortsen@googlemail.com
 designates 74.125.82.175 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAGgUee2+cPQ=tJxdGz2mUOGFZp2B_T+4M2xvdXT_QyLZg5oJhA@mail.gmail.com>
References: <CB3318EC.39AFA%aharui@adobe.com>
	<B9F90F88-7628-49FA-B126-1FEEF5316C8F@gmail.com>
	<CAAgciqqwhnpywSFdY074FtkLqudXFWdsARMzN6rJSSEMdOO6yQ@mail.gmail.com>
	<F9AD905C-88B1-43EC-831C-818E74D603EF@gmail.com>
	<CAEFz_vtZn0RK9mBDnBw-YN_wy7Ecas1B4NtES2PrvEDGbBrnLA@mail.gmail.com>
	<CANcBHECobifU+sYpoMcqn+GtFZCzfUuz91XE0rPcz-ZsZvkv8A@mail.gmail.com>
	<CAGgUee2+cPQ=tJxdGz2mUOGFZp2B_T+4M2xvdXT_QyLZg5oJhA@mail.gmail.com>
Date: Fri, 13 Jan 2012 12:23:37 +0100
Message-ID: 
 <CANi2vaf_qZZ3mj58xRgNJCVkOR1O84uWGP+=WD+9KStLDsdPLA@mail.gmail.com>
Subject: Re: Goal for Flex: Strengthening large-scale Flex applications
From: Dirk Eismann <bortsen@googlemail.com>
To: flex-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

agree. I also think this should be handled differently and not by Apache Fl=
ex.

IMHO there is no "right" (nor "wrong") way in how to architect a Flex
application at all. And as you can see it's actually depending very
much on your very POV and preferences. Getting consensus on this hot
(religious?) topic will be pretty difficult I would imagine.

Do we really need something bloated like the J2EE Blueprint Patterns?
I don't think so. J2EE needed it because it was not a framework at all
but just a specification so people needed advice, best practices and
patterns. I don't see why we would need this for Flex.

Personally, I use Swiz since 2 or 3 years now in some projects and I
really like it and my team likes it as well. In other projects we do
not use it because we don't have to and don't need to, I would not go
as far as evangelizing Swiz or any other framework or architectural
approach and saying that this ir that is the de-facto standard or a
best practice. I also did use Cairngorm 2 in some projects. Heck, I
even did Cairngorm consulting and training for customers that wanted
to learn and use Cairngorm.

Adobe clearly stated they won't offer any professional (commercial)
services around Apache Flex. Surely they will do it for Adobe Flex 4.6
but there will be a void in the near future that needs to be filled of
course. I think this is a *huge* opportunity for 3rd parties to
provide training, consulting and services around Apache Flex for
companies and developers that need it. This is where you can tell them
how they could / should use Flex in a way that fits their needs.

Again, I don't think that this is something Apache Flex should
provide. We should focus on the framework and the tools going forward
and leave enough flex-ibility for others to do something great with
it.

Dirk.

2012/1/13 Jo=E3o Fernandes <joaopedromartinsfernandes@gmail.com>:
> Jude don't get me wrong but clearly I still don't believe it's an Apache
> Flex matter. Apache Flex exists to drive the future of the project, not t=
o
> teach people how they should do something. Yes, if new stuff comes around=
,
> documentation about new features should be available,eventually some spec=
s
> might be available, similar to what Adobe did with spark specs but that's
> it. I clearly doubt will see at Apache Flex website, content telling peop=
le
> how to build an application.