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 1A03995B1 for ; Fri, 15 Jun 2012 18:29:47 +0000 (UTC) Received: (qmail 45067 invoked by uid 500); 15 Jun 2012 18:29:46 -0000 Delivered-To: apmail-incubator-flex-dev-archive@incubator.apache.org Received: (qmail 45023 invoked by uid 500); 15 Jun 2012 18:29:46 -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 45014 invoked by uid 99); 15 Jun 2012 18:29:46 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Jun 2012 18:29:46 +0000 X-ASF-Spam-Status: No, hits=2.2 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [209.85.160.175] (HELO mail-gh0-f175.google.com) (209.85.160.175) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Jun 2012 18:29:36 +0000 Received: by ghbz2 with SMTP id z2so2381194ghb.6 for ; Fri, 15 Jun 2012 11:29:16 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:from:date :message-id:subject:to:content-type:x-gm-message-state; bh=avvQfBuvd9OIIuynODIEK1kwvU+cY6PwqkcMPNhxQtA=; b=kcTF99XenXTyA/Oyw9DF2h4PLL0zoDudGtRyF6zwOv2S75wz/C9jkeyrvY31Nz/OoG yn2eZA9QFyYP0twzEatU2K2QWxcOgnDA6Z7LGXq6dxemZJ1VE78HyEmyUkIpz7qZMFg+ cu+oLsNwRcRBYUqAi6Az/qAdsGKH5Wi86x4ZCJH6SHsRCk/TWIL1yuzmSQMk/JI1xKbs Bj+EhUXuYYKRYXMqluIvT3RaAVCAumdNmtOflDwtDnExOe3SRs2671xCWEaOy5CgZu7l UzFdfU5uvB8Z4cegwvjT9WbslbgynDfJJu/WySMXCSDHpw9UbI8FkjC1EldulkD/jPTJ zrjw== Received: by 10.50.190.230 with SMTP id gt6mr2926227igc.48.1339784955880; Fri, 15 Jun 2012 11:29:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.50.129.98 with HTTP; Fri, 15 Jun 2012 11:28:45 -0700 (PDT) X-Originating-IP: [69.181.218.197] In-Reply-To: <4FDB7959.6000001@dot-com-it.com> References: <4FDB3B41.8000107@gmail.com> <4FDB4075.5070108@dot-com-it.com> <4FDB5599.2030609@dot-com-it.com> <4FDB7959.6000001@dot-com-it.com> From: Doug McCune Date: Fri, 15 Jun 2012 11:28:45 -0700 Message-ID: Subject: Re: Painful story... To: flex-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=14dae93406bb5ee4c104c286fefc X-Gm-Message-State: ALoCoQmbgeUNuPf3C0hbCl+/cDoA2SrKZ9lyYHSZrXQhA+FHtYIa0RCGknOPTc5mkGDb19X0uMoT --14dae93406bb5ee4c104c286fefc Content-Type: text/plain; charset=ISO-8859-1 > > I agree there is benefit to debating various options and alternatives. I > disagree that this list is the place for such discussions, as such > discussions are unrelated to the development of the Flex SDK. > I guess my concern is that the people contributing to the Flex SDK will essentially put heir head in the sand when it comes to alternative tech. So in this case, the topic was about the difficulty doing relatively simple box layout with HTML vs Flex. If anyone is going to try to do any kind of Flex -> HTML cross-compilation thing then an understanding of the differences and alternative frameworks (like Blueprint, which was brought up in the thread) is good to have. Additionally, I think the core SDK contributors should consider it part of their "job" to educate the wider community and be able to intelligently articulate the pros and cons of Flex (layout being one of those items), which inherently requires an understanding of the alternatives to Flex. As another semi-unrelated example, which I think is very appropriate for this list: Apple just announced a new layout model and list collection stuff in iOS 6. From what I understand, this is *very* much like using DataGroup and item renderers in Flex. It supports virtualized elements, custom layouts, etc. The way in which this is implemented should be well-understood by anyone working on the Flex SDK. I'd hope that this forum would be a good place to have that discussion. So sure, the original post may have been a bit too much "rant about HTML" and not enough about the "why" of why that's important to this project. But I really want to avoid any kind of blanket "this topic is inappropriate for this forum" response unless the topic *really* is inappropriate. A discussion (even a rant) about HTML's shortcomings compared to Flex passes my test for appropriateness, and based on others' responses here I think we've seen it passes others' test as well, so I'd just suggest we don't get too trigger-happy with the "take that topic elsewhere" type of reactions, otherwise people who want to bring up important topics (like my example of how Apple is doing layouts in iOS 6) will feel unwelcome in this forum. --14dae93406bb5ee4c104c286fefc--