localToGlobal

if you work in a team and use FDT 3.0. one of the most important things is, that you and your colleagues have the same core library settings.
you can find these preferences in
~workspace~/.metadata/.plugins/org.eclipse.core.runtime/.settings.

there you will find several files for eclipse preferences.
the important ones for FDT 3.0 are
com.powerflasher.fdt.core.formatter.prefs, com.powerflasher.fdt.core.prefs, com.powerflasher.fdt.core.problems.prefs, com.powerflasher.fdt.ui.prefs and org.eclipse.core.resources.prefs.

to save or share your core library settings just copy these two files com.powerflasher.fdt.core.prefs and org.eclipse.core.resources.prefs into the folder
~workspace~/.metadata/.plugins/org.eclipse.core.runtime/.settings
in the workspace of your co-worker. maybe you have to adjust the pathes for the pathvariables in the org.eclipse.core.resources.prefs -file.

today i started to migrate an old FDT 1.5 project to FDT 3.0 and
i like to share my experience with you. the only things you have to do are:

1.) add the ~com.powerflasher.fdt.core.prefs~ -file to your .settings folder (copy it from an other project)

2.) open the ~.as2_classpath~ -file, rename ~AS2Classpathes~ to ~AS2Classpath~ and add the attributes ~generateProblems=”true”~ and ~useAsSharedCode=”false”~ to the <AS2Classpath> -tags

3.) open the ~.project~ -file,
reneame ~com.pf.fdt.IncrementalProjectBuilder1~ to ~com.powerflasher.fdt.core.FlashBuilder~,
rename ~com.pf.fdt.FlashNature~ to ~com.powerflasher.fdt.core.FlashNature~,
rename ~location~ to ~locationURI~ and replace ~whatever~ with ~AS2_CORE_DEFAULT~ between the <locationURI> -tags

that’s it. i’ve created a small cheat-sheet for the migration.