Tree [r2492] / osmf / trunk / framework / OSMF / Download Snapshot History



File Date Author Commit
org 2010-02-18 briggs@adobe.com [r1109] PARB changes: Remove targetBufferTime from the ...
.actionScriptProperties 2010-02-05 evrijkom@adobe.com [r1004] PARB feedback: rename LayoutRenderer to LayoutR...
.flexLibProperties 2010-02-18 briggs@adobe.com [r1105] PARB changes: Move the dynamicstreaming classes...
.project 2010-01-18 briggs@adobe.com [r828] Update OSMF project files.
OSMF-build-config.xml 2011-03-02 svergoti [r2011] Rename a file
build.xml 2011-09-07 pmelania [r2341] update files for build system
readme.txt 2010-01-19 briggs@adobe.com [r853] Update build-config files for framework projects.

Read Me

1. Logging and Conditional Compilation

Along with the introduction of the logging framework, the media framework also starts to use conditional employee. Currently, CONFIG::LOGGING is defined to include or exclude the TraceLogger as the default logger for the Log class. The rationale is that when an OSMF developer is developing a media player, the developer may need to have a logger by default, and when the development work is done, the default logger may become unnecessary. Excluding a default logger can decrease the size of the media player. 

By default, CONFIG::LOGGING is defined to be false for the downloadable binary. This can be considered a release version of the media framework. One may choose to set CONFIG::LOGGING to be true and build a debug version.

There are two ways to use the media framework. One is to include the OSMF.swc in the project. In this case, no special handling is needed for the OSMF application project. The other way is to include the source code of the media framework in the project. In this case, the developer needs to define CONFIG::LOGGING to be either true or false in the project setting. This must be done with both Flex Builder and Flash Authoring tool. Otherwise, a compilation error will occur.