BTW, I get a number of build warnings when building tlf: 1) ParagraphElement has two places where currentAtomIndex has no type declaration. 2) A bunch of calls to TextLine.flushAtomData() does nothing. 3) A couple of these warnings: ApplyElementStyleNameOperation' has been deprecated. Please use 'ApplyFormatToElementOperation' These warnings are in EditClasses.
I see no reason to not correct #1. I'm not sure about #2 and #3. On Sep 2, 2013, at 3:26 PM, Harbs wrote: > Okie Dokie! > > I'm finally up and running. Here's what I did in case it's useful to someone > else having trouble with this: > > 1) Make sure your local repro names match the origin repro names exactly. > (i.e. they should be called "flex-sdk" and "flex-tlf"). > 2) Makes sure the repros are both in the same parent folder. > 3) Download the dependencies and put them somewhere on your machine. > 4) In the flex-sdk copy the env-template.properties file and rename it to > env.properties. > 5) Set the environment variables in that file. Here's what mine look like: > env.AIR_HOME=/Users/harbs/Documents/ApacheFlex/Dependencies/AdobeAIRSDK/ > env.TLF_HOME=/Users/harbs/Documents/ApacheFlex/git/flex-tlf/ > > env.PLAYERGLOBAL_HOME=/Users/harbs/Documents/ApacheFlex/Dependencies/player/ > env.PIXELBENDER_HOME=/Applications/Utilities/Adobe > Utilities-CS5.localized/Pixel Bender Toolkit 2/ > 6) Build the flex-sdk (cd [your sdk path] and then just run ant) > 7) Once the flex sdk is built, you should be able to build the tlf sdk by > itself (that takes between 10 and 20 seconds rather than that amount of time > in minutes…) > 8) In Flash Builder set the SDK or your project to "Flex Develop" or whatever > you want to call the SDK that you just built. > 9) Remove the playerglobal reference because it will likely not be linked > correctly, and link a valid one on your machine. > 10 Remove the reference in the project to textLayout.swc in the "Flex > Develop" sdk and add the one in flex-tlf/bin. > 11) Select the textLayout.swc file that you linked to in the flex-tlf repro > and set the properties of that (project) reference to flex-tlf/textLayout/src > > You should now be able to edit and debug the TLF source. When you rebuild the > swc after editing the source, the correct swc should be linked. > > You will need to repeat steps 8-11 for every project you want to debug tlf > code with. > > HTH, > Harbs > > P.S. Should I write these steps up on the wiki or something? > > On Sep 2, 2013, at 9:53 AM, Harbs wrote: > >> Okay. Thanks. >> >> I'll give it another go later today… >> >> On Sep 2, 2013, at 9:22 AM, Alex Harui wrote: >> >>> >>> >>> On 9/1/13 10:57 PM, "Harbs" <harbs.li...@gmail.com> wrote: >>> >>>> I'm going around in circles hereŠ >>>> >>>> I have two problems. One with playerglobal.swc and another with >>>> textLayout.swc >>>> >>>> 1) When I link the develop SDK to a project, I get two swc links: >>>> playerglobal.swc and "11.1". It can't find either of those. I can manage >>>> to get the SDK to work by unlinking those and linking to a valid copy of >>>> playerglobal on my machine. This is workable, but I'm concerned by why I >>>> need to do that. It's also a pain to do this every time I want to use the >>>> dev sdkŠ >>> I just realized that this sort of thing is why we don't use the git repo >>> folders as-is in FB. That's why we have the Installer and those scripts >>> like makeApacheFlexForFLexBuilder. And why I don't use FB and just use >>> the command line for MXMLC and FDB. >>> >>> I guess I'd suggest using the Installer to set up a working SDK then copy >>> textLayout.swc into the working SDK's frameworks/libs folder. But even >>> then, I think you have to worry about FB caching the SWC. >>> >>> HTH, >>> -Alex >>> >>> >> >
