[support for multiple tracking libraries]
As mentioned above, FLARManager has a new structure that grants it compatibility with any number of tracking libraries. Currently, support exists for flare*tracker, flare*NFT, and FLARToolkit (v2.5.4). The classes used to make the connection between FLARManager and these tracking libraries live in the flar.tracker package, and FLARManager should now be instantiated with one of these tracker managers as a parameter.
Note: if you’re using flare*tracker or flare*NFT, you must have the .lic license files in the same folder as your swfs. These files are included in the FLARManager distro, in the /bin-debug/ folder. These are evaluation versions of the flare* licenses, and tracking stops functioning after one minute.
Stay tuned for support for more tracking libraries in the future…
[native flash 3D]
Thanks to nutsu of libspark, FLARManager finally supports output to native Flash 3D. This is particularly useful for applications that just want to display a plane over the detected target — no more need to map a texture to a plane in a 3D engine. Think images, video, swfs. In the palm of your users’ hands.
[full documentation]
All of the changes did not go undocumented. Full html documentation of FLARManager’s source is available in ASDoc format (thanks to Grant Skinner’s handy ASDocr tool).
Additionally, all examples and tutorials are updated, both in the code and online. Online walkthroughs are available via the FLARMANAGER link in the nav bar above.
[alternative interface examples]
For my talk at FITC this spring, I put together a series of examples that show how markers can be used to craft alternative interfaces for games, digital tools, and artistic experiences. These can be found in the /apps package, and launched via the application class FLARManagerAppLauncher.as, both included in the FLARManager distro.
[support for FLARToolkit 2.5.4]
FLARManager v1.0 offers compatibility with the latest release of FLARToolkit, v2.5.4, and most of the goodies it provides. Support for ID-markers will follow in a later release.
[full-resolution video]
The default video resolution is now 640×480 in flarConfig.xml. This takes advantage of flare*tracker and flare*NFT’s superior framerate, and also works quite well with the recent improvements in FLARToolkit.
[flar.camera package]
Camera setup for various 3D frameworks is now abstracted into classes within the flar.camera package, which simplifies scene setup in application code. Each class within the flar.camera package sets up the projection matrix for a given 3D framework, regardless of the selected tracking library.
via words.transmote.com
http://words.transmote.com/wp/20100807/flarmanager-v1-0-augmented-reality-with-flash/