On Tue, Mar 12, 2013 at 1:18 PM, Alex Harui <aha...@adobe.com> wrote:
> > > > On 3/12/13 1:03 PM, "Om" <bigosma...@gmail.com> wrote: > > > On Tue, Mar 12, 2013 at 12:58 PM, Alex Harui <aha...@adobe.com> wrote: > > > >> > >> > >> > >> On 3/12/13 12:26 PM, "Harbs" <harbs.li...@gmail.com> wrote: > >> > >>> Why is TLF a separate repro at all? Why isn't it just part of the sdk > >> repro? > >>> > >> Might be possible, but TLF came late and had its own set of branches > and no > >> SVN history so we kept it external. > >> > >> > > I think we should just copy the TLF project into the appropriate > directory > > path under the sdk. I dont see any value keeping it as separate top > level > > project. > > > > And this is probably the best time to do this. > > > I think it is best if we learn to deal with "external" repos. When we make > Falcon the default compiler, we won't copy it into SDK will we? And > BlazeDS, and Squiggly, etc. > > I agree with the general principle about having to deal with externals. But I am not very sure what plans we have for TLF though. > 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? Thanks, Om
