Mailing-List: contact dev-help@flex.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@flex.apache.org
Received-SPF: pass (athena.apache.org: domain of harbs.lists@gmail.com
 designates 209.85.212.181 as permitted sender)
Content-Type: text/plain; charset=windows-1252
Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\))
Subject: Re: To FlexJS or not to FlexJS
From: Harbs <harbs.lists@gmail.com>
In-Reply-To: 
 <CACK5iZdoyZEpyy+ewUySLunqyM+Xx4LREVQnDnCBLNybwkhwfg@mail.gmail.com>
Date: Sun, 2 Nov 2014 14:24:31 +0200
Content-Transfer-Encoding: quoted-printable
Message-Id: <ECD4B238-F06C-4C16-B90D-8D6C827F5561@gmail.com>
References: <D9541034-FD33-4816-84DC-692A89389D2C@gmail.com>
 <CACK5iZdoyZEpyy+ewUySLunqyM+Xx4LREVQnDnCBLNybwkhwfg@mail.gmail.com>
To: dev@flex.apache.org

I=92d never seen that talk before. I just watched about a third of it, =
and it=92s really interesting. I=92ll finish it later=85

Thanks!
Harbs

> One approach uses EaselJS with TypeScript and they pretty much wrote =
the
> entire front end text engine from scratch.  They use InDesign in the
> backend.  There was a presentation by Ted Patrick at the 360Flex =
conference
> this year on this exact topic[2]  And he says this engine would be =
open
> sourced soon [3]
>=20