Mailing-List: contact flex-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: flex-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of aharui@adobe.com designates
 64.18.1.183 as permitted sender)
From: Alex Harui <aharui@adobe.com>
To: "flex-dev@incubator.apache.org" <flex-dev@incubator.apache.org>
Date: Wed, 4 Jan 2012 14:21:48 -0800
Subject: Re: Flex Text Formatting suggestion
Thread-Topic: Flex Text Formatting suggestion
Thread-Index: AczLLKUhnYSoN/ToQei+U7FWK5+OIwAApqag
Message-ID: <CB2A10FC.39100%aharui@adobe.com>
In-Reply-To: <00e901cccb2c$a8faf3c0$faf0db40$@pierresolutions.com>
Accept-Language: en-US
Content-Language: en-US
user-agent: Microsoft-Entourage/13.11.0.110726
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Using Flex to render HTML/CSS as been thought to be a ton of work, but coul=
d
definitely happen with community support.  I have an old prototype on my
blog that I've been refactoring in my spare time.


--=20
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui


On 1/4/12 2:03 PM, "Lionel Andre Pierre" <lionel@pierresolutions.com> wrote=
:

> Please forgive if this is out of turn or place, it seems people are makin=
g
> suggestions about the work they would like to see done on Flex and I woul=
d
> like to contribute.
>=20
> I've used Flex for about 5 years and always found text formatting to be
> difficult and limited.
>=20
> =20
>=20
> I would like to see as an alternative to TLF (Text Layout Framework).
>=20
> Flex could benefit from some development geared toward correctly displayi=
ng
> HTML/CSS formatted text.
>=20
>=20
> The reasons behind this are:
>=20
> 1.       Flex applications could more easily tap into content that is bei=
ng
> shared through traditional web pages.
>=20
> 2.      HTML/CSS knowledge could be leveraged against Flex instead of the
> TLF approach which cannot be used anywhere else (AFAIK)
>=20
> 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.=20
>=20
> Lionel=20
>=20
> =20
>=20