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 9CC929A74 for ; Thu, 19 Jan 2012 11:56:36 +0000 (UTC) Received: (qmail 26748 invoked by uid 500); 19 Jan 2012 11:56:36 -0000 Delivered-To: apmail-incubator-flex-dev-archive@incubator.apache.org Received: (qmail 26656 invoked by uid 500); 19 Jan 2012 11:56:35 -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 26648 invoked by uid 99); 19 Jan 2012 11:56:35 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Jan 2012 11:56:35 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of masuland@gmail.com designates 74.125.82.43 as permitted sender) Received: from [74.125.82.43] (HELO mail-ww0-f43.google.com) (74.125.82.43) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Jan 2012 11:56:25 +0000 Received: by wgbdt11 with SMTP id dt11so79846wgb.0 for ; Thu, 19 Jan 2012 03:56:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=from:mime-version:content-type:subject:date:in-reply-to:to :references:message-id:x-mailer; bh=+cFXjb8ts7tH9RNyrTl57gjiYuf3e+kWeT0LJbj1cuU=; b=WY4jp01b2shj481NijIi+nKe09vRrXa/aqd5yszyOJ/CeQ1zzfrBanhdS93GdEFWA7 MgLC7Z6y9bY/TVMHl1vpwDVqC4RyclqQcOTesr5Cy3fbVTPrOtiWGHkmc4g3KtiKlXRU In/uUFGmhYfkQjSTwVu+IgYWVO7XiZMJ5p3oQ= Received: by 10.180.95.199 with SMTP id dm7mr43608289wib.9.1326974165343; Thu, 19 Jan 2012 03:56:05 -0800 (PST) Received: from [192.168.1.37] (brln-4dbc3d42.pool.mediaWays.net. [77.188.61.66]) by mx.google.com with ESMTPS id eq5sm17717547wib.2.2012.01.19.03.56.02 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 19 Jan 2012 03:56:04 -0800 (PST) From: Sebastian Mohr Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: multipart/alternative; boundary=Apple-Mail-4-774610309 Subject: Proposal: Code Example / Application Development Procedure (was: Re: Non-core code, contrib and samples (was: Goal for Flex: Strengthening large-scale Flex applications...)) Date: Thu, 19 Jan 2012 12:56:01 +0100 In-Reply-To: To: flex-dev@incubator.apache.org References: Message-Id: <6B0DD3B4-E307-46C1-8498-8EF2DA251965@gmail.com> X-Mailer: Apple Mail (2.1084) X-Virus-Checked: Checked by ClamAV on apache.org --Apple-Mail-4-774610309 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Due to our last discussion about code examples, I would like=20 to discuss the procedure we should follow when writing these=20 code examples.=20 I also would like to point out that there is a difference between=20 writing Component Code Examples which should illustrate the=20 functionality of a component (Spark-DropDownList or MX- ColorPicker), and, Application Code Examples which should=20 illustrate how to build (large-scale) Flex applications. I am personally more interested on writing Application Code Examples with or without the use of Microarchitectures, because I think the = community=20 and Adobe already created lots of Component Code Examples: Flex 3, http://livedocs.adobe.com/flex/3/html/index.html Flex 4.6, http://help.adobe.com/en_US/flex/using/index.html ... Proposal: Code Example / Application Development Procedure This is the proposal for writing (large-scale) Application Code = Examples: 'Before working on your Application Code make sure you have specified = the requirements of the application in a Specification Document, and, = you have defined an Application Coding Standard. An "Application Coding = Standard" consists of a set of Nanoarchitectures / Architectural = Patterns which describe the structure of your application, and, some = coding guidelines collected in a Coding Conventions document.' For more information please check out the diagram on this site: http://code.google.com/p/masuland/wiki/ApplicationDevelopmentProcedure I would be happy to find some kind of consensus on this topic here in = Apache Flex. -- Sebastian On Jan 16, 2012, at 8:37 AM, Peter Elst wrote: >> And thus, we should probably not use application frameworks in our = examples >> on the project website. The application framework vendors should = have >> their >> own examples on their website. >=20 >=20 > Maybe we could have a wiki with references to those application = framework > vendor examples, and other Apache Flex specific articles, tutorials, = sample > code. >=20 > I'd be happy to work on that if it there is no objection to that = getting > set up. >=20 > - Peter --Apple-Mail-4-774610309--