Harbs is correct for a potential longer-term usage. It might be easier to mimic the Flash dependencies it has in HTML/JS. The vast majority of the code is computation of glyph positions.
For the short-term, since we're trying to emulate what you'll get in the browser when running in Flash, we may use TLF to take html markup and display it. On 3/12/13 2:11 PM, "Harbs" <harbs.li...@gmail.com> wrote: > Eventually, there will need to be a comparable text engine for JS. Having a > single interface for Flash TLF and Javascript TLF could be valuable. > > On Mar 12, 2013, at 10:33 PM, Om wrote: > >>> >>> TLF has no Flex SDK dependencies so it is probably best kept separate and >>> available for those not using the main Flex SDK. It might even get used by >>> FlexJS users, for example. >>> >>> >> How will FlexJS use it? Isnt TLF based on Flash Text Engine? I thought >> the goal of FlexJS is to eliminate dependency on Flash? > -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
