Return-Path: X-Original-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-flex-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0F583B68C for ; Wed, 4 Jan 2012 21:24:01 +0000 (UTC) Received: (qmail 87358 invoked by uid 500); 4 Jan 2012 21:24:00 -0000 Delivered-To: apmail-incubator-flex-dev-archive@incubator.apache.org Received: (qmail 87331 invoked by uid 500); 4 Jan 2012 21:24:00 -0000 Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: flex-dev@incubator.apache.org Delivered-To: mailing list flex-dev@incubator.apache.org Received: (qmail 87323 invoked by uid 99); 4 Jan 2012 21:24:00 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jan 2012 21:24:00 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of joao.saleiro@webfuel.pt designates 216.154.217.150 as permitted sender) Received: from [216.154.217.150] (HELO webfuel.pt) (216.154.217.150) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jan 2012 21:23:53 +0000 Received-SPF: softfail (webfuel.pt: domain of transitioning joao.saleiro@webfuel.pt does not designate 77.54.127.141 as permitted sender) receiver=webfuel.pt; client-ip=77.54.127.141; helo=[192.168.1.83]; envelope-from=joao.saleiro@webfuel.pt; x-software=spfmilter 0.97 http://www.acme.com/software/spfmilter/ with libspf2-1.0.0; Received: from [192.168.1.83] (141.127.54.77.rev.vodafone.pt [77.54.127.141]) by webfuel.pt (8.14.3/8.14.3) with ESMTP id q04LNVXS011920 for ; Wed, 4 Jan 2012 21:23:31 GMT Message-ID: <4F04C345.2080707@webfuel.pt> Date: Wed, 04 Jan 2012 21:23:17 +0000 From: =?ISO-8859-1?Q?Jo=E3o_Saleiro?= Organization: Webfuel.pt User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: flex-dev@incubator.apache.org Subject: Re: Flex modularity through composition and interfaces References: <20120104160346.14214ryrloryh4fm@www.teotigraphix.com> <4F04C070.6020401@webfuel.pt> <815DF771-823D-476E-B8BC-609AFA887442@rogeliocastillo.com> In-Reply-To: <815DF771-823D-476E-B8BC-609AFA887442@rogeliocastillo.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Checked: Checked by ClamAV on apache.org Rogelio, I am not saying that the Flex SDK should have a lib for DI (like Swiz or Mate). What I would like was to be able to configure the mappings between the interfaces and objects, so I could easily replace TabNavigator1 with TabNavigator2 touching in code as less as possible. Part of the DI could even be handled at compiler level. A similar approach was proposed at the Flex summit by Mike Labriola. Jo�o Saleiro On 04-01-2012 21:17, Rogelio Castillo Aqueveque wrote: > I agree on modularity, but I reckon dependency injection is a totally different thing which has lots of very good libs out there... not sure if that should be part of the SDK. > > I believe that the focus should be on splitting the SDK into several modules/libs, then think on interface design. > > R > > --- > Rogelio Castillo Aqueveque > rogelio@rogeliocastillo.com > > > > > On 4/01/2012, at 6:11 PM, Jo�o Saleiro wrote: > >> +1 >> >> I agree with reducing strong-coupled dependencies as the first priority. >> >> I would also complement the use of interfaces with: >> >> - using dependency injection when possible >> - splitting the SDK into several libraries >> - support and advocate the use of Maven for managing dependencies (or something similar) >> >> >> Jo�o Saleiro >> >> On 04-01-2012 21:03, Michael Schmalle wrote: >>> Continuing the thread from "Committer duties and information" >>> >>> about setting interface priority to #1 in the future development fo Flex. >>> >>> Mike >>> >>> >