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 98B04B6A6 for ; Wed, 4 Jan 2012 22:31:43 +0000 (UTC) Received: (qmail 22180 invoked by uid 500); 4 Jan 2012 22:31:43 -0000 Delivered-To: apmail-incubator-flex-dev-archive@incubator.apache.org Received: (qmail 22157 invoked by uid 500); 4 Jan 2012 22:31:43 -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 22149 invoked by uid 99); 4 Jan 2012 22:31:43 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jan 2012 22:31:43 +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 rick.winscot@gmail.com designates 209.85.216.175 as permitted sender) Received: from [209.85.216.175] (HELO mail-qy0-f175.google.com) (209.85.216.175) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 04 Jan 2012 22:31:37 +0000 Received: by qcqw6 with SMTP id w6so10160507qcq.6 for ; Wed, 04 Jan 2012 14:31:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=date:from:to:message-id:in-reply-to:references:subject:x-mailer :mime-version:content-type; bh=lvMJt+x6lgzKxeDkR3HJ+OiJ9rkOnV1hafVqtDCs8aI=; b=rm7uC7W4xFLCe5FIOHmnVh1C+8vukC/tT0dM6OP52HjInDERG/ol4Cl2yy7han5+ol Zu03BCG3gAU56TAYTtkF+DJKthG6wB6yuXezmvYhV1aTfI4jtfgqjWGyPLc9VgBZqBl1 ftu4KmaqVK6oBBin4otH2AtWFQsUIC61J3N1E= Received: by 10.224.188.137 with SMTP id da9mr64695094qab.29.1325716277222; Wed, 04 Jan 2012 14:31:17 -0800 (PST) Received: from Rick-Winscots-iMac.local (h78.184.101.208.static.ip.windstream.net. [208.101.184.78]) by mx.google.com with ESMTPS id t4sm31753097qal.17.2012.01.04.14.31.15 (version=SSLv3 cipher=OTHER); Wed, 04 Jan 2012 14:31:16 -0800 (PST) Date: Wed, 4 Jan 2012 17:31:14 -0500 From: Rick Winscot To: flex-dev@incubator.apache.org Message-ID: In-Reply-To: References: Subject: Re: Flex Text Formatting suggestion X-Mailer: sparrow 1.5 (build 1043.1) MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="4f04d332_7fdcc233_d14f" --4f04d332_7fdcc233_d14f Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Lionel, I have a functional example that does some rudimentary HTML parsing and uses AS3 instead of JavaScript for scripting. The example handles just about anything in script, dynamic css, etc. The only thing it doesn't do is declarative parsing. http://bit.ly/tRLTXF Cheers, Rick Winscot On Wednesday, January 4, 2012 at 5:21 PM, Alex Harui wrote: > Using Flex to render HTML/CSS as been thought to be a ton of work, but could > definitely happen with community support. I have an old prototype on my > blog that I've been refactoring in my spare time. > > > -- > Alex Harui > Flex SDK Team > Adobe Systems, Inc. > http://blogs.adobe.com/aharui > > > On 1/4/12 2:03 PM, "Lionel Andre Pierre" wrote: > > > Please forgive if this is out of turn or place, it seems people are making > > suggestions about the work they would like to see done on Flex and I would > > like to contribute. > > > > I've used Flex for about 5 years and always found text formatting to be > > difficult and limited. > > > > > > I would like to see as an alternative to TLF (Text Layout Framework). > > > > Flex could benefit from some development geared toward correctly displaying > > HTML/CSS formatted text. > > > > > > The reasons behind this are: > > > > 1. Flex applications could more easily tap into content that is being > > shared through traditional web pages. > > > > 2. HTML/CSS knowledge could be leveraged against Flex instead of the > > TLF approach which cannot be used anywhere else (AFAIK) > > > > 3. The MX Text Components were heading that way (with the HTMLText > > properties) but the implementation was never up to par, I hope something can > > be done there. > > > > Lionel > > --4f04d332_7fdcc233_d14f--