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 C753CB7B5 for ; Thu, 12 Jan 2012 16:27:34 +0000 (UTC) Received: (qmail 68783 invoked by uid 500); 12 Jan 2012 16:27:33 -0000 Delivered-To: apmail-incubator-flex-dev-archive@incubator.apache.org Received: (qmail 68190 invoked by uid 500); 12 Jan 2012 16:27:27 -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 68172 invoked by uid 99); 12 Jan 2012 16:27:26 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Jan 2012 16:27:26 +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 (athena.apache.org: domain of masuland@gmail.com designates 74.125.83.47 as permitted sender) Received: from [74.125.83.47] (HELO mail-ee0-f47.google.com) (74.125.83.47) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 12 Jan 2012 16:27:19 +0000 Received: by eekd17 with SMTP id d17so633947eek.6 for ; Thu, 12 Jan 2012 08:26:57 -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=kDHO0srKh8rB0tq08OwmRaqJ8gVmU9R5QeJsHucDgzY=; b=j5gOTnu0/GmWEnXY8lkR7EpZIuli6k8zTrimAmvdx/phJ67dkZZOv8wBhLdFKIrqFO yuwJU4f7buSMp3Bwq4KN2iTnp+j3zQOFflUxDFij1/L/3d04IVVm2bokwfol2dW3rZMp l5tIZNlMfVoCiqu8QFzd0iryklA1hTUi0gInw= Received: by 10.213.31.196 with SMTP id z4mr885363ebc.142.1326385617654; Thu, 12 Jan 2012 08:26:57 -0800 (PST) Received: from [192.168.1.37] (brln-4db81a3f.pool.mediaWays.net. [77.184.26.63]) by mx.google.com with ESMTPS id t59sm21248281eeh.10.2012.01.12.08.26.54 (version=TLSv1/SSLv3 cipher=OTHER); Thu, 12 Jan 2012 08:26:56 -0800 (PST) From: Sebastian Mohr Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: multipart/alternative; boundary=Apple-Mail-26-186062656 Subject: Re: What about Cairngorm 3? Date: Thu, 12 Jan 2012 17:26:53 +0100 In-Reply-To: To: flex-dev@incubator.apache.org References: <64a323d8$7a6079$1b70af7e$@com> <7CC09902-BB37-4A36-8225-A73620AAADE5@gmail.com> Message-Id: X-Mailer: Apple Mail (2.1084) --Apple-Mail-26-186062656 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=us-ascii @Nick ... Thx and sorry to disagree ... Please have a look for the word "best-practices" on this website: http://sourceforge.net/adobe/cairngorm/wiki/CairngormGuidelines/ @All ... sorry to bother you again :( -- Sebastian On Jan 12, 2012, at 5:20 PM, Nicholas Kwiatkowski wrote: > Sebastian/Rui, > > There is a reason why even Adobe never published a "Best Practices" > document when writing Flex (for small projects or even enterprise). Best > Practices, espically when you start to bring in frameworks are not a > "one-size fits-all" type of model. Patterns that I use for large apps that > use Fiber are /completely/ different than those that done. Patterns that I > use for apps that I share libraries with mobile or TV based apps are > /completely/ different than those enterprise apps that run in my 911 > centers. Some of these apps I've written use the popular frameworks -- > many do not. > > *Flex, itself is a framework*. It doesn't force you into any particular > coding convention, but in my eyes, that is for the better. It leaves it up > to the coder to best determine what is the best / most efficient / most > correct for their own situation. Sure, that will mean that we will have > developers who write bad code -- but chances are those will be the same > developers who don't understand WHY a recommendation is made -- only that > is is right and that they need to follow it. That helps nobody (they still > write 'bad' code, it is just formatted according to the guidelines). > > Right now, what the incubator really needs is to get this project off the > ground. Once we get the code we need to work on the deficiencies that we > identify for the SDK and framework to make it viable again for enterprises. > This is where our effort should be put rather than trying > to excerpt control over other developers, or make recommendations that > really don't help out many people right now. Right now the Flex SDK won't > be getting any new users due to the PR statements of its previous creator. > We need to turn that around before we tackle anything else. > > Now, a group like the Spoon Foundation (which is tasking itself with the > education and promotion aspect of Flex) may be a good group to help put > together recommendations. But I think we have much more important things > on our plat to busy ourselves with it. Plus, my notes of having an > 'official' document irks me the wrong way. > > -Nick > > On Thu, Jan 12, 2012 at 4:40 AM, Sebastian Mohr wrote: > >> @Rui >> >> Great that you've asked. I intended to cover this >> topic today ;) The situation can be boiled down >> to this question: >> >> Will Apache Flex only be responsible for managing >> the Flex SDK or will Apache Flex also be responsible >> to define "Best Coding Practices" to build sustainable >> Flex apps? >> >> Some guys on this list seem to dislike that Apache Flex >> should be responsible to define "Best Coding Practices" >> for Flex, which IMHO I think is wrong. >> >> When this debate has been clarified we will see if the >> "Best Coding Practices" discussions have to move to >> another mailing list, or not. >> >> >> -- Sebastian >> >> >> >> On Jan 12, 2012, at 10:02 AM, Rui Silva wrote: >> >>> I've been seeing some discussions around best practices for Flex >>> application development which led me to think about Cairngorm 3 which was >>> large that: Some architectural best practices and supporting code >>> libraries. Cairngorm is currently hosted on Sourceforge >>> (http://sourceforge.net/adobe/cairngorm/home/Home/). >>> >>> Could this be a starting point? >>> >>> Cheers, >>> Rui >>> >> >> --Apple-Mail-26-186062656--