Flex 4.5 Build Times

We are building a Flex 4.5 application using the pure MVC framework.  We use the Apache Subversion SVN server for source code control (and ant for building).  When we do a build of the project the build time can vary between 30 seconds and 15 minutes!  Can anyone cast any light on why this might be, as you can imagine it is having quite a negative impact on our productivity!  There does not seem to be any pattern to this and is common to all the machines on our network.  Any help would be hugely appreciated!

OK
I found it project>properties add a device
KBn

Similar Messages

  • Usage dependency is created at Build time and installation time

    Hi,
    The infrastructure guys have selected the usage dependency as Build time and Installation time, while creating software components.
    "Y" SWC is created as depedency for "X" software component.
    In SLD(software catalog),  we are able to view the Y component as dependency in X component(at both build time and installation time).  In usage dependency we are able to view Y component but when we click Y component in usage dependecy we are also able to view X component. Is there any problem with this ?
    There is another issue. we are able to view basis object(in IR) in Y component but not in X component.  Actually as per the above configuration basis object in IR should appear in X component.
    Please refer to another forum which may give you some more idea.("BPM - Message interfaces of one component are not appearing in another comp") pasted on 17 Nov,2006.
    Please could you provide us the inputs.
    Thanks,
    Ramesh

    hi,
    as you see per my weblog try choosing Installation Time
    /people/michal.krawczyk2/blog/2005/08/26/xi-are-you-independentfrom-your-dependencies
    more about it on:
    http://help.sap.com/saphelp_nw04s/helpdata/en/d4/8d784289b4de54e10000000a155106/content.htm
    Regards,
    michal
    <a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions"><b>XI / PI FAQ - Frequently Asked Questions</b></a>

  • How can you build time series measures in OBIEE without using TODATE AGO fu

    How can you build time series measures in OBIEE without using TODATE and AGO function?
    Please provide steps to build time series
    measures in OBIEE without using TODATE and
    AGO function. Dashboard results not storing
    in cache when using TODATE and AGO functions.
    eventhough its cached users queries not
    hitting cache because queries doesn't match
    exact date time when using TODATE and AGO
    functions. so I want to build queries using
    sysdate and some simple calculations. Please
    send your inputs/ideas for my questions..
    Thanks in Advance

    This can be using Msum function in answers. Use the following formula, here dollars is my metric. Change the formula based on your metric.
    Msum("Sales Measures".Dollars ,2) - "Sales Measures".Dollars
    the report will be cached and better performed compared with time series. check ti
    - Madan Thota

  • How can I change default build time from 1 sec to .5 sec?

    Whenever I create a build, the default time is 1 sec. I'd like it to be .5 sec. I use a blank master slide. How can I change the default build time for all slides? Or can I?

    I'm sorry, but Apple does not provide a downgrade path for iOS. Because downgrading is unsupported by Apple we cannot discuss it on these forums, but you can use Google to find information on how to install an older version of iOS on any iDevice.

  • Tips on how to speed up preview/debug build time?

    I am building an air2.5 application and I am still learning the finer details of Flash.
    Our project has a number of images and sounds, and the file size is starting to get up there, but nothing that we are worried about for our end product.
    However, every time I try to run the program by using CTRL+Enter or CTRL+SHIFT+Enter (which I use ALOT), it takes FOREVER to "exporting SWF movie" (like 3 minutes every time) and I suspect as the project continues to grow and more assets are added, it will get signfigantly worse.
    I've tried to disable the "compress move" option in the publish settings, but it made no difference.
    All my images and sounds have been setup as classes so i can reference them through my as files and flash code, I rarely do anything "on the stage". Alost all my sounds are wav files (for the moment) and the images are PNG's (as I need the alpha channels)
    The only thing that I was able to think of is making the graphics and sound assets in some kind of pre-compiled library that doesn't have to get compressed and compiled every tiem I try to debug, only I haven't a clue how to do that, or if it's possible.
    Does anyone know of any ways to improve the build time for debugging and such?
    Or anyone have any tips and tricks/do's and don'ts when it comes to this kind of thing?
    Thanks.

    the SWC thing may be exactly what I need.
    I read that link you gave me and I will definately do a little more research on SWC, even if it's not completely clear how to use them at this particular moment.
    let's say I have an image called MyImage.png which I have setup to export for actionscript on frame 1 and the class is called "MyImage"
    Assume I have the same thing setup in my library for a sound file called "MySound"
    Now, without doing any reading first, I would assume that I would create a new fla file, put those 2 assets in said fla's library and then compile that fla into an swc? And then access thoughs assets in my main project by importing the swc into it? or it is more simple than that?
    Cheers
    Dave

  • Minimize WLW build time?

    Hi!
    Is it possible to get Workshop only to build elements that actually has changed
    on the file system? In regular ant you typically achieve this by using the timestamp
    mechanisms.
    This would greatly decrease the build time, and thereby increase the WLW user
    experience significantly!
    Thanks in advance.
    Regards
    Vidar Moe

    hi,
    Thank you Dhanya, so if i get it right it's possible to have zero down time during setup and initialization with this method :
    1. delete data in infoprividers in BW
    2. Delete setup tables and delta queues in R/3.
    2. Run init from BW with no data transfer (supposition: this will setup delta queues).
    3. Run setup tables filling in R/3 (supposition: all documents posted while this operation is going on will be stored in delta queues)
    4. Run full repair load in BW
    5. Run delta load in BW.
    is this right?
    how about compression with and without marker update mentioned here? [https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328|https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f83be790-0201-0010-4fb0-98bd7c01e328]
    we are using first scenario : Inventory management with non-cumulative key figures.
    Thank you.

  • Which dc and sc should add in build time form sld when integration uwl

    hi
    i have to create a webdynpro to show info from uwl, like follow
    IUWLService uwlService=(IUWLService)PortalRuntime.getRuntimeResources().getService(IUWLService.ALIAS_KEY);
    but i don't know which dc and sc i should add in build time form sld and use it.
    i try add UWLJWF from sld, and ?
    i develop with nwce ehp1
    thank you

    1) tc/je/security/api
    2) tc/je/usermanagement/api
    from ENGFACADE.
    3) tc/kmc/bc.uwl/api
    from UWLJWF

  • How to start Flash Media Encoder 3.2 from Flex application with run time parameters?

    Hello ,
    I'm developing the application to stream High Quality video.While streming by default camera/microphone settings the qulaity of streaming is not upto my expected level.I want to stream through Flash Media Encoder.My aim is the user login to the application.Video/audio qulaity details are retrived from shared object stored in the client machine.The login user name only gathered at run time & it will be the streaming profile name to Encoder.Once the the Encoder started the outgoing video will be come into screen to client.Please guide me How to start Flash Media Encoder 3.2 from Flex application with run time parameters(User name as  streaming name) without manually start the FME?
    Thanks in advance.
    Regards
    Sasharyuva

    Hi MarcSaphiron,
    Could you please send the samples?It will be much helpful to complete my
    job within the deadline.
    Thanks in advance.
    Regards,
    Sasharyuva

  • Build time

    Is there a way to change the default build speed? All builds open with 1 second and I prefer .5 second.

    j.d.darcy wrote:
    Robert.Bossy wrote:
    This is a couple of yes/no questions to confirm that I got it right. I'm in the context of build-time annotation processing where the AnnotationProcessor analyses each specified annotated class as well as their ancestors.
    Let's assume barClassType is a com.sun.mirror.type.ClassType instance representing the type named foo.Bar.
    Would barClassType.getDeclaration() return a non-null ClassDeclaration instance,
    even though: foo.Bar was not specified when the annotation processing tool was invoked,
    provided that: foo.Bar can be found somewhere in the class path?Yes.
    If so, let's assume barDeclaration was assigned to the said return value and Qux is an annotation type.
    Would barDeclaration.getAnnotation(Qux.class) return a non-null Annotation instance,
    provided that: the Qux retention policy was set to either Retention.CLASS or Retention.RUNTIME?If the Bar type declaration included the Qux annotation (either directly or by annotation inheritance), yes.Yeah, that was implicit. Thanks a lot.

  • Reduce Flex application initial loading time

    Comparing to HTML, Flex's initial load time is very long. How
    to reduce the initial loading time to the level that is
    comparable to HTML's loading time for the page content? Any
    best practice or rules to follow?

    Ok, OK! What's the specs?
    How long is the load time? Please don't say "very long".
    Let's see the spec. Oh, and can you give me a load time for the
    mythologocal HTML page in question, just so I can compare?
    I gotta tell ya, I sometimes take a nap when I'm loading half
    the ASP pages I stumble across nowadays.
    Here's a page from the Los Angeles times--html--- coming in @
    6-7 seconds.
    http://latimesblogs.latimes.com/lanow/2009/02/los-angeles-pay.html
    Another example: from CNN.com, coming in at about 10-11
    seconds. Unbelievable.
    http://www.cnn.com/video/#/video/showbiz/2009/02/03/wynter.simpson.scientology.cnn
    I've got a 350Kb Flex app using RSLs which loads in about 5
    seconds. I'm kicking @ss compared to a lot of professional web
    sites out there. Think that's too slow? Compared to what???

  • Extremely long build times using object oriented code

    We have a LabVIEW application that we need to build an .exe for distrubution purposes.  The application relies on several object-oriented classes for data handling and dynamic dispatch type casting and function selection.  Currently it takes approximately 1.5 hours to build the application and it seems that most of the time is spent processing the object oriented files.  Has anyone else seen this issue and are there any creative ways to improve the build times?

    Hi again.  We are still having issues using LVOOP due to extrmely long .exe build times as well as long labview loading times.  I traced the source of this to one class hierarchy, shown below.  This hierarchy also relies heavily on overriding top-level functions, declared as virtual VIs in the top level class, which I suspect contributes to this problem.  While debugging another issue, I was trying to build a small piece of my main code into an .exe to verify its functionality and experienced the same extremely long build times.  When I removed this class hierarchy from the VI, it built extremely fast.  Also to be clear, I am using neither the mean function or Mean.vi anywhere in this set of code.  To date we have been delighted with LVOOP and how it has made our code cleaner, mroe robust, and more maintanable.  However, when creating new functionality in the code we often elect NOT to create new objects (even though they would be beneficial) because we are hesitant to introduce the extra time (load and build) required for LabVIEW to handle these classes.  If our entire system was rewritten in LVOOP, I would suspect that it would become unmaintainable and unbuildable due to the LVOOP overhead.  I was hoping that LV2009 would address some of these issues but, alas, it did not. Still looking for a way to improve this and thanks in advance for all of the replies.

  • Build-time access to declarations and annotations

    This is a couple of yes/no questions to confirm that I got it right. I'm in the context of build-time annotation processing where the AnnotationProcessor analyses each specified annotated class as well as their ancestors.
    Let's assume barClassType is a com.sun.mirror.type.ClassType instance representing the type named foo.Bar.
    Would barClassType.getDeclaration() return a non-null ClassDeclaration instance,
    even though: foo.Bar was not specified when the annotation processing tool was invoked,
    provided that: foo.Bar can be found somewhere in the class path?
    If so, let's assume barDeclaration was assigned to the said return value and Qux is an annotation type.
    Would barDeclaration.getAnnotation(Qux.class) return a non-null Annotation instance,
    provided that: the Qux retention policy was set to either Retention.CLASS or Retention.RUNTIME?

    j.d.darcy wrote:
    Robert.Bossy wrote:
    This is a couple of yes/no questions to confirm that I got it right. I'm in the context of build-time annotation processing where the AnnotationProcessor analyses each specified annotated class as well as their ancestors.
    Let's assume barClassType is a com.sun.mirror.type.ClassType instance representing the type named foo.Bar.
    Would barClassType.getDeclaration() return a non-null ClassDeclaration instance,
    even though: foo.Bar was not specified when the annotation processing tool was invoked,
    provided that: foo.Bar can be found somewhere in the class path?Yes.
    If so, let's assume barDeclaration was assigned to the said return value and Qux is an annotation type.
    Would barDeclaration.getAnnotation(Qux.class) return a non-null Annotation instance,
    provided that: the Qux retention policy was set to either Retention.CLASS or Retention.RUNTIME?If the Bar type declaration included the Qux annotation (either directly or by annotation inheritance), yes.Yeah, that was implicit. Thanks a lot.

  • Flex sdk incremental build will lose swc information

    I have a mxmlc ant task job like this
            <mxmlc 
            file="${trunk_dir}/main/src/main.mxml"
            output="${local_tmp}/app/bin/main.swf"
                      >    
                <load-config filename="${basedir}/flex-config-sea.xml"/>
                <source-path path-element="${FLEX_HOME}/frameworks"/>
            </mxmlc>
    in flex-config-sea.xml I put this in for incremental compile and swc build
          <include-libraries>
             <library>/opt/cruisecontrol-bin-2.8.4/projects/sea_client/trunk/main/libs/Mate_08_9.swc</library>
             <library>/opt/cruisecontrol-bin-2.8.4/projects/sea_client/trunk/main/libs/xprogress.swc</library>
             <library>/opt/cruisecontrol-bin-2.8.4/projects/sea_client/trunk/main/libs/component.swc</library>
          </include-libraries>
          <incremental>true</incremental>
    the first time build is ok, but the second time after I changed one single file, the output is
    [mxmlc] Loading configuration file /opt/cruisecontrol-bin-2.8.4/projects/cc/flex-config-sea.xml
        [mxmlc] Recompile: /opt/cruisecontrol-bin-2.8.4/projects/sea_client/trunk/main/src/C.as
        [mxmlc] Reason: The source file or one of the included files has been updated.
        [mxmlc] Files changed: 1 Files affected: 0
        [mxmlc] Required RSLs:
        [mxmlc]     textLayout_2.0.0.232.swz with 1 failover.
        [mxmlc]     framework_4.6.0.23201.swz with 1 failover.
        [mxmlc]     rpc_4.6.0.23201.swz with 1 failover.
        [mxmlc]     mx_4.6.0.23201.swz with 1 failover.
        [mxmlc]     spark_4.6.0.23201.swz with 1 failover.
        [mxmlc]     sparkskins_4.6.0.23201.swz with 1 failover.
        [mxmlc] /tmp/sea_local/app/bin/main.swf (426617 bytes)
    but the output swf is complaining lack of some swc when running, which didn't show up in the first time
    ReferenceError: Error #1065: Variable _shared_maps_GlobalMapWatcherSetupUtil is not defined.
              at global/flash.utils::getDefinitionByName()
              at shared.maps::GlobalMap()
              at main/_main_GlobalMap1_i()
              at main()
              at _main_mx_managers_SystemManager/create()
              at mx.managers.systemClasses::ChildManager/initializeTopLevelWindow()
              at mx.managers::SystemManager/initializeTopLevelWindow()
              at mx.managers::SystemManager/http://www.adobe.com/2006/flex/mx/internal::kickOff()
              at mx.managers::SystemManager/http://www.adobe.com/2006/flex/mx/internal::preloader_completeHandler()
              at flash.events::EventDispatcher/dispatchEventFunction()
              at flash.events::EventDispatcher/dispatchEvent()
              at mx.preloaders::Preloader/timerHandler()
              at flash.utils::Timer/_timerDispatch()
              at flash.utils::Timer/tick()
    this message normally shows up when there's no Mate_08_9.swc found at runtime. but this shouldn't happen.
    is there anyway to work around this? thanks a lot
    here is the full flex-config-sea.xml:
    <flex-config>
       <!-- benchmark: output performance benchmark-->
       <!-- benchmark usage:
       <benchmark>boolean</benchmark>
       -->
       <compiler>
          <!-- compiler.accessible: generate an accessible SWF-->
          <accessible>true</accessible>
          <!-- compiler.actionscript-file-encoding: specifies actionscript file encoding. If there is no BOM in the AS3 source files, the compiler will use this file encoding.-->
          <!-- compiler.actionscript-file-encoding usage:
          <actionscript-file-encoding>string</actionscript-file-encoding>
          -->
          <!-- compiler.allow-source-path-overlap: checks if a source-path entry is a subdirectory of another source-path entry. It helps make the package names of MXML components unambiguous.-->
          <allow-source-path-overlap>false</allow-source-path-overlap>
          <!-- compiler.as3: use the ActionScript 3 class based object model for greater performance and better error reporting. In the class based object model most built-in functions are implemented as fixed methods of classes.-->
          <as3>true</as3>
          <!-- compiler.compress usage:
          <compress>boolean</compress>
          -->
          <!-- compiler.context-root: path to replace {context.root} tokens for service channel endpoints-->
          <!-- compiler.context-root usage:
          <context-root>context-path</context-root>
          -->
          <!-- compiler.debug: generates a movie that is suitable for debugging-->
          <debug>false</debug>
          <!-- compiler.defaults-css-files usage:
          <defaults-css-files>
             <filename>string</filename>
             <filename>string</filename>
          </defaults-css-files>
          -->
          <!-- compiler.defaults-css-url: defines the location of the default style sheet. Setting this option overrides the implicit use of the defaults.css style sheet in the framework.swc file.-->
          <!-- compiler.defaults-css-url usage:
          <defaults-css-url>string</defaults-css-url>
          -->
          <!-- compiler.define: define a global AS3 conditional compilation definition, e.g. -define=CONFIG::debugging,true or -define+=CONFIG::debugging,true (to append to existing definitions in flex-config.xml) -->
          <!-- compiler.define usage:
          <define>
             <name>string</name>
             <value>string</value>
             <value>string</value>
          </define>
          -->
          <!-- compiler.enable-runtime-design-layers usage:
          <enable-runtime-design-layers>boolean</enable-runtime-design-layers>
          -->
          <!-- compiler.es: use the ECMAScript edition 3 prototype based object model to allow dynamic overriding of prototype properties. In the prototype based object model built-in functions are implemented as dynamic properties of prototype objects.-->
          <es>false</es>
          <extensions>
             <!-- compiler.extensions.extension usage:
             <extension>
                <extension>string</extension>
                <parameters>string</parameters>
             </extension>
             -->
          </extensions>
          <!-- compiler.external-library-path: list of SWC files or directories to compile against but to omit from linking-->
          <external-library-path>
             <path-element>/opt/flexsdk/4.6.0/frameworks/libs/player/11.1/playerglobal.swc</path-element>
          </external-library-path>
          <fonts>
             <!-- compiler.fonts.advanced-anti-aliasing: enables advanced anti-aliasing for embedded fonts, which provides greater clarity for small fonts.-->
             <advanced-anti-aliasing>true</advanced-anti-aliasing>
             <!-- compiler.fonts.flash-type: enables FlashType for embedded fonts, which provides greater clarity for small fonts.-->
             <!-- compiler.fonts.flash-type usage:
             <flash-type>boolean</flash-type>
             -->
             <languages>
                <!-- compiler.fonts.languages.language-range: a range to restrict the number of font glyphs embedded into the SWF-->
                <!-- compiler.fonts.languages.language-range usage:
                <language-range>
                   <lang>string</lang>
                   <range>string</range>
                   <range>string</range>
                </language-range>
                -->
             </languages>
             <!-- compiler.fonts.local-font-paths usage:
             <local-font-paths>
                <path-element>string</path-element>
                <path-element>string</path-element>
             </local-font-paths>
             -->
             <!-- compiler.fonts.local-fonts-snapshot: File containing system font data produced by flex2.tools.FontSnapshot.-->
             <!-- compiler.fonts.managers: Compiler font manager classes, in policy resolution order-->
             <managers>
                <manager-class>flash.fonts.JREFontManager</manager-class>
                <manager-class>flash.fonts.BatikFontManager</manager-class>
                <manager-class>flash.fonts.AFEFontManager</manager-class>
                <manager-class>flash.fonts.CFFFontManager</manager-class>
             </managers>
             <!-- compiler.fonts.max-cached-fonts: sets the maximum number of fonts to keep in the server cache.  The default value is 20.-->
             <max-cached-fonts>20</max-cached-fonts>
             <!-- compiler.fonts.max-glyphs-per-face: sets the maximum number of character glyph-outlines to keep in the server cache for each font face. The default value is 1000.-->
             <max-glyphs-per-face>1000</max-glyphs-per-face>
          </fonts>
          <!-- compiler.headless-server: a flag to set when Flex is running on a server without a display-->
          <!-- compiler.headless-server usage:
          <headless-server>boolean</headless-server>
          -->
          <!-- compiler.include-libraries: a list of libraries (SWCs) to completely include in the SWF-->
          <!-- compiler.include-libraries usage:
          <include-libraries>
             <library>string</library>
             <library>string</library>
          </include-libraries>
          -->
          <include-libraries>
             <library>/opt/cruisecontrol-bin-2.8.4/projects/sea_client/trunk/main/libs/Mate_08_9.swc</library>
             <library>/opt/cruisecontrol-bin-2.8.4/projects/sea_client/trunk/main/libs/xprogress.swc</library>
             <library>/opt/cruisecontrol-bin-2.8.4/projects/sea_client/trunk/main/libs/component.swc</library>
          </include-libraries>
          <!-- compiler.incremental: enables incremental compilation-->
          <!-- compiler.incremental usage:
          <incremental>boolean</incremental>
          -->
          <incremental>true</incremental>
          <!-- compiler.isolate-styles: enables the compiled application or module to set styles that only affect itself and its children-->
          <!-- compiler.isolate-styles usage:
          <isolate-styles>boolean</isolate-styles>
          -->
          <!-- compiler.keep-all-type-selectors: disables the pruning of unused CSS type selectors-->
          <!-- compiler.keep-all-type-selectors usage:
          <keep-all-type-selectors>boolean</keep-all-type-selectors>
          -->
          <!-- compiler.keep-as3-metadata: keep the specified metadata in the SWF-->
          <!-- compiler.keep-as3-metadata usage:
          <keep-as3-metadata>
             <name>string</name>
             <name>string</name>
          </keep-as3-metadata>
          -->
          <!-- compiler.keep-generated-actionscript: save temporary source files generated during MXML compilation-->
          <keep-generated-actionscript>false</keep-generated-actionscript>
          <!-- compiler.library-path: list of SWC files or directories that contain SWC files-->
          <library-path>
             <path-element>/opt/flexsdk/4.6.0/frameworks/libs/flash-integration.swc</path-element>
             <path-element>/opt/flexsdk/4.6.0/frameworks/libs/authoringsupport.swc</path-element>
             <path-element>/opt/flexsdk/4.6.0/frameworks/locale/{locale}</path-element>
          </library-path>
          <!-- compiler.locale: specifies the locale for internationalization-->
          <locale>
             <locale-element>en_US</locale-element>
          </locale>
          <!-- compiler.minimum-supported-version usage:
          <minimum-supported-version>string</minimum-supported-version>
          -->
          <!-- compiler.mobile: specifies the target runtime is a mobile device-->
          <mobile>false</mobile>
          <mxml>
             <!-- compiler.mxml.compatibility-version: specifies a compatibility version. e.g. -compatibility-version=2.0.1-->
             <!-- compiler.mxml.compatibility-version usage:
             <compatibility-version>version</compatibility-version>
             -->
             <!-- compiler.mxml.minimum-supported-version usage:
             <minimum-supported-version>string</minimum-supported-version>
             -->
             <!-- compiler.mxml.qualified-type-selectors usage:
             <qualified-type-selectors>boolean</qualified-type-selectors>
             -->
          </mxml>
          <namespaces>
             <!-- compiler.namespaces.namespace: Specify a URI to associate with a manifest of components for use as MXML elements-->
             <namespace>
                <uri>http://ns.adobe.com/mxml/2009</uri>
                <manifest>/opt/flexsdk/4.6.0/frameworks/mxml-2009-manifest.xml</manifest>
             </namespace>
             <namespace>
                <uri>library://ns.adobe.com/flex/spark</uri>
                <manifest>/opt/flexsdk/4.6.0/frameworks/spark-manifest.xml</manifest>
             </namespace>
             <namespace>
                <uri>library://ns.adobe.com/flex/mx</uri>
                <manifest>/opt/flexsdk/4.6.0/frameworks/mx-manifest.xml</manifest>
             </namespace>
             <namespace>
                <uri>http://www.adobe.com/2006/mxml</uri>
                <manifest>/opt/flexsdk/4.6.0/frameworks/mxml-manifest.xml</manifest>
             </namespace>
          </namespaces>
          <!-- compiler.omit-trace-statements: toggle whether trace statements are omitted-->
          <omit-trace-statements>true</omit-trace-statements>
          <!-- compiler.optimize: Enable post-link SWF optimization-->
          <optimize>true</optimize>
          <!-- compiler.preloader: Specifies the default value for the Application's preloader attribute. If not specified, the default preloader value is mx.preloaders.SparkDownloadProgressBar when -compatibility-version >= 4.0 and mx.preloaders.DownloadProgressBar when -compatibility-version < 4.0.-->
          <!-- compiler.preloader usage:
          <preloader>string</preloader>
          -->
          <!-- compiler.report-invalid-styles-as-warnings: enables reporting of invalid styles as warnings-->
          <!-- compiler.report-invalid-styles-as-warnings usage:
          <report-invalid-styles-as-warnings>boolean</report-invalid-styles-as-warnings>
          -->
          <!-- compiler.report-missing-required-skin-parts-as-warnings: Use this option to generate a warning instead of an error when a missing required skin part is detected.-->
          <!-- compiler.report-missing-required-skin-parts-as-warnings usage:
          <report-missing-required-skin-parts-as-warnings>boolean</report-missing-required-skin-parts-as-warnings>
          -->
          <!-- compiler.services: path to Flex Data Services configuration file-->
          <!-- compiler.services usage:
          <services>filename</services>
          -->
          <!-- compiler.show-actionscript-warnings: runs the AS3 compiler in a mode that detects legal but potentially incorrect code-->
          <show-actionscript-warnings>true</show-actionscript-warnings>
          <!-- compiler.show-binding-warnings: toggle whether warnings generated from data binding code are displayed-->
          <show-binding-warnings>true</show-binding-warnings>
          <!-- compiler.show-invalid-css-property-warnings: toggle whether invalid css property warnings are reported-->
          <!-- compiler.show-invalid-css-property-warnings usage:
          <show-invalid-css-property-warnings>boolean</show-invalid-css-property-warnings>
          -->
          <!-- compiler.show-shadowed-device-font-warnings: toggles whether warnings are displayed when an embedded font name shadows a device font name-->
          <show-shadowed-device-font-warnings>false</show-shadowed-device-font-warnings>
          <!-- compiler.show-unused-type-selector-warnings: toggle whether warnings generated from unused CSS type selectors are displayed-->
          <show-unused-type-selector-warnings>true</show-unused-type-selector-warnings>
          <!-- compiler.source-path: list of path elements that form the roots of ActionScript class hierarchies-->
          <source-path>
          </source-path>
          <!-- compiler.strict: runs the AS3 compiler in strict error checking mode.-->
          <strict>true</strict>
          <!-- compiler.theme: list of CSS or SWC files to apply as a theme-->
          <!-- compiler.use-resource-bundle-metadata: determines whether resources bundles are included in the application.-->
          <use-resource-bundle-metadata>true</use-resource-bundle-metadata>
          <!-- compiler.verbose-stacktraces: save callstack information to the SWF for debugging-->
          <verbose-stacktraces>false</verbose-stacktraces>
          <!-- compiler.warn-array-tostring-changes: Array.toString() format has changed.-->
          <warn-array-tostring-changes>false</warn-array-tostring-changes>
          <!-- compiler.warn-assignment-within-conditional: Assignment within conditional.-->
          <warn-assignment-within-conditional>true</warn-assignment-within-conditional>
          <!-- compiler.warn-bad-array-cast: Possibly invalid Array cast operation.-->
          <warn-bad-array-cast>true</warn-bad-array-cast>
          <!-- compiler.warn-bad-bool-assignment: Non-Boolean value used where a Boolean value was expected.-->
          <warn-bad-bool-assignment>true</warn-bad-bool-assignment>
          <!-- compiler.warn-bad-date-cast: Invalid Date cast operation.-->
          <warn-bad-date-cast>true</warn-bad-date-cast>
          <!-- compiler.warn-bad-es3-type-method: Unknown method.-->
          <warn-bad-es3-type-method>true</warn-bad-es3-type-method>
          <!-- compiler.warn-bad-es3-type-prop: Unknown property.-->
          <warn-bad-es3-type-prop>true</warn-bad-es3-type-prop>
          <!-- compiler.warn-bad-nan-comparison: Illogical comparison with NaN. Any comparison operation involving NaN will evaluate to false because NaN != NaN.-->
          <warn-bad-nan-comparison>true</warn-bad-nan-comparison>
          <!-- compiler.warn-bad-null-assignment: Impossible assignment to null.-->
          <warn-bad-null-assignment>true</warn-bad-null-assignment>
          <!-- compiler.warn-bad-null-comparison: Illogical comparison with null.-->
          <warn-bad-null-comparison>true</warn-bad-null-comparison>
          <!-- compiler.warn-bad-undefined-comparison: Illogical comparison with undefined.  Only untyped variables (or variables of type *) can be undefined.-->
          <warn-bad-undefined-comparison>true</warn-bad-undefined-comparison>
          <!-- compiler.warn-boolean-constructor-with-no-args: Boolean() with no arguments returns false in ActionScript 3.0.  Boolean() returned undefined in ActionScript 2.0.-->
          <warn-boolean-constructor-with-no-args>false</warn-boolean-constructor-with-no-args>
          <!-- compiler.warn-changes-in-resolve: __resolve is no longer supported.-->
          <warn-changes-in-resolve>false</warn-changes-in-resolve>
          <!-- compiler.warn-class-is-sealed: Class is sealed.  It cannot have members added to it dynamically.-->
          <warn-class-is-sealed>true</warn-class-is-sealed>
          <!-- compiler.warn-const-not-initialized: Constant not initialized.-->
          <warn-const-not-initialized>true</warn-const-not-initialized>
          <!-- compiler.warn-constructor-returns-value: Function used in new expression returns a value.  Result will be what the function returns, rather than a new instance of that function.-->
          <warn-constructor-returns-value>false</warn-constructor-returns-value>
          <!-- compiler.warn-deprecated-event-handler-error: EventHandler was not added as a listener.-->
          <warn-deprecated-event-handler-error>false</warn-deprecated-event-handler-error>
          <!-- compiler.warn-deprecated-function-error: Unsupported ActionScript 2.0 function.-->
          <warn-deprecated-function-error>true</warn-deprecated-function-error>
          <!-- compiler.warn-deprecated-property-error: Unsupported ActionScript 2.0 property.-->
          <warn-deprecated-property-error>true</warn-deprecated-property-error>
          <!-- compiler.warn-duplicate-argument-names: More than one argument by the same name.-->
          <warn-duplicate-argument-names>true</warn-duplicate-argument-names>
          <!-- compiler.warn-duplicate-variable-def: Duplicate variable definition -->
          <warn-duplicate-variable-def>true</warn-duplicate-variable-def>
          <!-- compiler.warn-for-var-in-changes: ActionScript 3.0 iterates over an object's properties within a "for x in target" statement in random order.-->
          <warn-for-var-in-changes>false</warn-for-var-in-changes>
          <!-- compiler.warn-import-hides-class: Importing a package by the same name as the current class will hide that class identifier in this scope.-->
          <warn-import-hides-class>true</warn-import-hides-class>
          <!-- compiler.warn-instance-of-changes: Use of the instanceof operator.-->
          <warn-instance-of-changes>true</warn-instance-of-changes>
          <!-- compiler.warn-internal-error: Internal error in compiler.-->
          <warn-internal-error>true</warn-internal-error>
          <!-- compiler.warn-level-not-supported: _level is no longer supported. For more information, see the flash.display package.-->
          <warn-level-not-supported>true</warn-level-not-supported>
          <!-- compiler.warn-missing-namespace-decl: Missing namespace declaration (e.g. variable is not defined to be public, private, etc.).-->
          <warn-missing-namespace-decl>true</warn-missing-namespace-decl>
          <!-- compiler.warn-negative-uint-literal: Negative value will become a large positive value when assigned to a uint data type.-->
          <warn-negative-uint-literal>true</warn-negative-uint-literal>
          <!-- compiler.warn-no-constructor: Missing constructor.-->
          <warn-no-constructor>false</warn-no-constructor>
          <!-- compiler.warn-no-explicit-super-call-in-constructor: The super() statement was not called within the constructor.-->
          <warn-no-explicit-super-call-in-constructor>false</warn-no-explicit-super-call-in-constructor>
          <!-- compiler.warn-no-type-decl: Missing type declaration.-->
          <warn-no-type-decl>true</warn-no-type-decl>
          <!-- compiler.warn-number-from-string-changes: In ActionScript 3.0, white space is ignored and '' returns 0. Number() returns NaN in ActionScript 2.0 when the parameter is '' or contains white space.-->
          <warn-number-from-string-changes>false</warn-number-from-string-changes>
          <!-- compiler.warn-scoping-change-in-this: Change in scoping for the this keyword.  Class methods extracted from an instance of a class will always resolve this back to that instance.  In ActionScript 2.0 this is looked up dynamically based on where the method is invoked from.-->
          <warn-scoping-change-in-this>false</warn-scoping-change-in-this>
          <!-- compiler.warn-slow-text-field-addition: Inefficient use of += on a TextField.-->
          <warn-slow-text-field-addition>true</warn-slow-text-field-addition>
          <!-- compiler.warn-unlikely-function-value: Possible missing parentheses.-->
          <warn-unlikely-function-value>true</warn-unlikely-function-value>
          <!-- compiler.warn-xml-class-has-changed: Possible usage of the ActionScript 2.0 XML class.-->
          <warn-xml-class-has-changed>false</warn-xml-class-has-changed>
       </compiler>
       <!-- debug-password: the password to include in debuggable SWFs-->
       <!-- debug-password usage:
       <debug-password>string</debug-password>
       -->
       <!-- default-background-color: default background color (may be overridden by the application code)-->
       <default-background-color>0xFFFFFF</default-background-color>
       <!-- default-frame-rate: default frame rate to be used in the SWF.-->
       <default-frame-rate>24</default-frame-rate>
       <!-- default-script-limits: default script execution limits (may be overridden by root attributes)-->
       <default-script-limits>
          <max-recursion-depth>1000</max-recursion-depth>
          <max-execution-time>60</max-execution-time>
       </default-script-limits>
       <!-- default-size: default application size (may be overridden by root attributes in the application)-->
       <default-size>
          <width>500</width>
          <height>375</height>
       </default-size>
       <!-- externs: a list of symbols to omit from linking when building a SWF-->
       <!-- externs usage:
       <externs>
          <symbol>string</symbol>
          <symbol>string</symbol>
       </externs>
       -->
       <frames>
          <!-- frames.frame: A SWF frame label with a sequence of classnames that will be linked onto the frame.-->
          <!-- frames.frame usage:
          <frame>
             <label>string</label>
             <classname>string</classname>
          </frame>
          -->
       </frames>
       <framework>halo</framework>
       <!-- include-inheritance-dependencies-only: only include inheritance dependencies of classes specified with include-classes -->
       <!-- include-inheritance-dependencies-only usage:
       <include-inheritance-dependencies-only>boolean</include-inheritance-dependencies-only>
       -->
       <!-- include-resource-bundles: a list of resource bundles to include in the output SWC-->
       <!-- include-resource-bundles usage:
       <include-resource-bundles>
          <bundle>string</bundle>
          <bundle>string</bundle>
       </include-resource-bundles>
       -->
       <!-- includes: a list of symbols to always link in when building a SWF-->
       <!-- includes usage:
       <includes>
          <symbol>string</symbol>
          <symbol>string</symbol>
       </includes>
       -->
       <!-- link-report: Output a XML-formatted report of all definitions linked into the application.-->
       <!-- link-report usage:
       <link-report>filename</link-report>
       -->
       <!-- load-config: load a file containing configuration options-->
       <!-- load-externs: an XML file containing <def>, <pre>, and <ext> symbols to omit from linking when building a SWF-->
       <!-- load-externs usage:
       <load-externs>filename</load-externs>
       -->
       <metadata>
          <!-- metadata.contributor: A contributor's name to store in the SWF metadata-->
          <!-- metadata.contributor usage:
          <contributor>name</contributor>
          -->
          <!-- metadata.creator: A creator's name to store in the SWF metadata-->
          <creator>darkhutgme</creator>
          <!-- metadata.date: The creation date to store in the SWF metadata-->
          <!-- metadata.date usage:
          <date>text</date>
          -->
          <!-- metadata.description: The default description to store in the SWF metadata-->
          <description></description>
          <!-- metadata.language: The language to store in the SWF metadata (i.e. EN, FR)-->
          <language>EN</language>
          <!-- metadata.localized-description: A localized RDF/XMP description to store in the SWF metadata-->
          <!-- metadata.localized-description usage:
          <localized-description>
             <text>string</text>
             <lang>string</lang>
             <lang>string</lang>
          </localized-description>
          -->
          <!-- metadata.localized-title: A localized RDF/XMP title to store in the SWF metadata-->
          <!-- metadata.localized-title usage:
          <localized-title>
             <title>string</title>
             <lang>string</lang>
             <lang>string</lang>
          </localized-title>
          -->
          <!-- metadata.publisher: A publisher's name to store in the SWF metadata-->
          <publisher>darkhutgame</publisher>
          <!-- metadata.title: The default title to store in the SWF metadata-->
          <title>GAME</title>
       </metadata>
       <!-- raw-metadata: XML text to store in the SWF metadata (overrides metadata.* configuration)-->
       <!-- raw-metadata usage:
       <raw-metadata>text</raw-metadata>
       -->
       <!-- remove-unused-rsls: remove RSLs that are not being used by the application-->
       <remove-unused-rsls>true</remove-unused-rsls>
       <!-- resource-bundle-list: prints a list of resource bundles to a file for input to the compc compiler to create a resource bundle SWC file. -->
       <!-- resource-bundle-list usage:
       <resource-bundle-list>filename</resource-bundle-list>
       -->
       <!-- runtime-shared-libraries: a list of runtime shared library URLs to be loaded before the application starts-->
       <!-- runtime-shared-libraries usage:
       <runtime-shared-libraries>
          <url>string</url>
          <url>string</url>
       </runtime-shared-libraries>
       -->
       <!-- runtime-shared-library-path: specifies a SWC to link against, an RSL URL to load, with an optional policy file URL and optional failover URLs -->
       <runtime-shared-library-path>
          <path-element>/opt/flexsdk/4.6.0/frameworks/libs/textLayout.swc</path-element>
          <rsl-url>textLayout_2.0.0.232.swz</rsl-url>
          <policy-file-url></policy-file-url>
          <rsl-url>http://fpdownload.adobe.com/pub/swz/tlf/2.0.0.232/textLayout_2.0.0.232.swz</rsl-url>
          <policy-file-url>http://fpdownload.adobe.com/pub/swz/crossdomain.xml</policy-file-url>
       </runtime-shared-library-path>
       <runtime-shared-library-path>
          <path-element>/opt/flexsdk/4.6.0/frameworks/libs/osmf.swc</path-element>
          <rsl-url>osmf_1.0.0.16316.swz</rsl-url>
          <policy-file-url></policy-file-url>
          <rsl-url>http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23201/osmf_1.0.0.16316.swz</rsl-url>
          <policy-file-url>http://fpdownload.adobe.com/pub/swz/crossdomain.xml</policy-file-url>
       </runtime-shared-library-path>
       <runtime-shared-library-path>
          <path-element>/opt/flexsdk/4.6.0/frameworks/libs/framework.swc</path-element>
          <rsl-url>framework_4.6.0.23201.swz</rsl-url>
          <policy-file-url></policy-file-url>
          <rsl-url>http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23201/framework_4.6.0.23201.swz</rsl-url>
          <policy-file-url>http://fpdownload.adobe.com/pub/swz/crossdomain.xml</policy-file-url>
       </runtime-shared-library-path>
       <runtime-shared-library-path>
          <path-element>/opt/flexsdk/4.6.0/frameworks/libs/charts.swc</path-element>
          <rsl-url>charts_4.6.0.23201.swz</rsl-url>
          <policy-file-url></policy-file-url>
          <rsl-url>http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23201/charts_4.6.0.23201.swz</rsl-url>
          <policy-file-url>http://fpdownload.adobe.com/pub/swz/crossdomain.xml</policy-file-url>
       </runtime-shared-library-path>
       <runtime-shared-library-path>
          <path-element>/opt/flexsdk/4.6.0/frameworks/libs/rpc.swc</path-element>
          <rsl-url>rpc_4.6.0.23201.swz</rsl-url>
          <policy-file-url></policy-file-url>
          <rsl-url>http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23201/rpc_4.6.0.23201.swz</rsl-url>
          <policy-file-url>http://fpdownload.adobe.com/pub/swz/crossdomain.xml</policy-file-url>
       </runtime-shared-library-path>
       <runtime-shared-library-path>
          <path-element>/opt/flexsdk/4.6.0/frameworks/libs/mx/mx.swc</path-element>
          <rsl-url>mx_4.6.0.23201.swz</rsl-url>
          <policy-file-url></policy-file-url>
          <rsl-url>http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23201/mx_4.6.0.23201.swz</rsl-url>
          <policy-file-url>http://fpdownload.adobe.com/pub/swz/crossdomain.xml</policy-file-url>
       </runtime-shared-library-path>
       <runtime-shared-library-path>
          <path-element>/opt/flexsdk/4.6.0/frameworks/libs/advancedgrids.swc</path-element>
          <rsl-url>advancedgrids_4.6.0.23201.swz</rsl-url>
          <policy-file-url></policy-file-url>
          <rsl-url>http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23201/advancedgrids_4.6.0.23201.swz</rsl-url>
          <policy-file-url>http://fpdownload.adobe.com/pub/swz/crossdomain.xml</policy-file-url>
       </runtime-shared-library-path>
       <runtime-shared-library-path>
          <path-element>/opt/flexsdk/4.6.0/frameworks/libs/spark.swc</path-element>
          <rsl-url>spark_4.6.0.23201.swz</rsl-url>
          <policy-file-url></policy-file-url>
          <rsl-url>http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23201/spark_4.6.0.23201.swz</rsl-url>
          <policy-file-url>http://fpdownload.adobe.com/pub/swz/crossdomain.xml</policy-file-url>
       </runtime-shared-library-path>
       <runtime-shared-library-path>
          <path-element>/opt/flexsdk/4.6.0/frameworks/libs/spark_dmv.swc</path-element>
          <rsl-url>spark_dmv_4.6.0.23201.swz</rsl-url>
          <policy-file-url></policy-file-url>
          <rsl-url>http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23201/spark_dmv_4.6.0.23201.swz</rsl-url>
          <policy-file-url>http://fpdownload.adobe.com/pub/swz/crossdomain.xml</policy-file-url>
       </runtime-shared-library-path>
       <runtime-shared-library-path>
          <path-element>/opt/flexsdk/4.6.0/frameworks/libs/sparkskins.swc</path-element>
          <rsl-url>sparkskins_4.6.0.23201.swz</rsl-url>
          <policy-file-url></policy-file-url>
          <rsl-url>http://fpdownload.adobe.com/pub/swz/flex/4.6.0.23201/sparkskins_4.6.0.23201.swz</rsl-url>
          <policy-file-url>http://fpdownload.adobe.com/pub/swz/crossdomain.xml</policy-file-url>
       </runtime-shared-library-path>
       <runtime-shared-library-settings>
          <!-- runtime-shared-library-settings.application-domain: override the application domain an RSL is loaded into. The supported values are 'current', 'default', 'parent', or 'top-level'.-->
          <application-domain>
             <path-element>/opt/flexsdk/4.6.0/frameworks/libs/textLayout.swc</path-element>
             <application-domain-target>default</application-domain-target>
             <path-element>/opt/flexsdk/4.6.0/frameworks/libs/osmf.swc</path-element>
             <application-domain-target>default</application-domain-target>
             <path-element>/opt/flexsdk/4.6.0/frameworks/libs/framework.swc</path-element>
             <application-domain-target>default</application-domain-target>
             <path-element>/opt/flexsdk/4.6.0/frameworks/libs/charts.swc</path-element>
             <application-domain-target>default</application-domain-target>
             <path-element>/opt/flexsdk/4.6.0/frameworks/libs/rpc.swc</path-element>
             <application-domain-target>default</application-domain-target>
             <path-element>/opt/flexsdk/4.6.0/frameworks/libs/mx/mx.swc</path-element>
             <application-domain-target>default</application-domain-target>
             <path-element>/opt/flexsdk/4.6.0/frameworks/libs/advancedgrids.swc</path-element>
             <application-domain-target>default</application-domain-target>
             <path-element>/opt/flexsdk/4.6.0/frameworks/libs/spark.swc</path-element>
             <application-domain-target>default</application-domain-target>
             <path-element>/opt/flexsdk/4.6.0/frameworks/libs/spark_dmv.swc</path-element>
             <application-domain-target>default</application-domain-target>
             <path-element>/opt/flexsdk/4.6.0/frameworks/libs/sparkskins.swc</path-element>
             <application-domain-target>default</application-domain-target>
          </application-domain>
          <!-- runtime-shared-library-settings.force-rsls: force an RSL to be loaded, overriding the removal caused by using the remove-unused-rsls option-->
          <!-- runtime-shared-library-settings.force-rsls usage:
          <force-rsls>
             <path-element>string</path-element>
             <path-element>string</path-element>
          </force-rsls>
          -->
       </runtime-shared-library-settings>
       <!-- size-report: Output an XML-formatted report detailing the size of all code and data linked into the application.-->
       <!-- size-report usage:
       <size-report>filename</size-report>
       -->
       <!-- static-link-runtime-shared-libraries: statically link the libraries specified by the -runtime-shared-libraries-path option.-->
       <static-link-runtime-shared-libraries>false</static-link-runtime-shared-libraries>
       <!-- swf-version: specifies the version of the compiled SWF file.-->
       <swf-version>14</swf-version>
       <!-- target-player: specifies the version of the player the application is targeting. Features requiring a later version will not be compiled into the application. The minimum value supported is "9.0.0".-->
       <target-player>11.1.0</target-player>
       <!-- tools-locale: specifies the locale used by the compiler when reporting errors and warnings.-->
       <!-- tools-locale usage:
       <tools-locale>string</tools-locale>
       -->
       <!-- use-direct-blit: Use hardware acceleration to blit graphics to the screen, where such acceleration is available.-->
       <!-- use-direct-blit usage:
       <use-direct-blit>boolean</use-direct-blit>
       -->
       <!-- use-gpu: Use GPU compositing features when drawing graphics, where such acceleration is available.-->
       <!-- use-gpu usage:
       <use-gpu>boolean</use-gpu>
       -->
       <!-- use-network: toggle whether the SWF is flagged for access to network resources-->
       <use-network>true</use-network>
       <!-- verify-digests: verifies the libraries loaded at runtime are the correct ones.-->
       <verify-digests>true</verify-digests>
       <!-- warnings: toggle the display of warnings-->
       <!-- warnings usage:
       <warnings>boolean</warnings>
       -->
    </flex-config>

    Somewhere in your pom.xml where you are configuring your build dependancies there will be a line <scope>caching</scope> this line is configuring the build to use a flex runtime shared library. This line is generating the error because caching is not a valid dependancy scope in maven 3 however mojos uses it anyway. There was a defect opened against flexmojos; I've linked it below. Froeder's response to the issue was that it was not fixable, that the warning is expected and that we'll have to live with it for now.
    https://issues.sonatype.org/browse/FLEXMOJOS-363?page=com.atlassian.jira.plugin.system.iss uetabpanels%3Achangehistory-tabpanel

  • Is Adobe Flex suitable to build a Multimedia Presentation?

    I am looking for some advice on the suitability of using
    Adobe Flex for building a Multimedia presentation system. I have
    watched numerous videos about Flex and even tried some tutorials
    but before I make a decision on Technologies for a project I am
    working on, I wanted to consult the Flex community for some advice.
    I have to take Multimedia Presentation made using PowerPoint
    and build it into a custom made Multimedia Presentation that has
    similar functionality. Would Adobe Flex would be a suitable tool?
    The Presentation must be viewable on the Internet and be deployed
    to the Desktop so combining Flex with Adobe AIR would be needed to
    meet this requirement.
    I guess the general requirements are as follows:-
    The user must be able to navigate forward and backward
    through pages of the presentation.
    The Presentation must be able to display Flash video's. When
    video is played, the video must open in a new window infront of the
    main application. Images and animated GIF'S must have the same
    functionality.
    Based on these requirements, would Flex be suitable?
    Thanks in advance for you help and advice.

    I think Flex would be very suitable for building a multimedia
    presentation system. Once you create your Flex app and generate the
    SWF file, you can post it on the web, or view it on the desltop,
    even without AIR. You could use view states to transition between
    pages, though you would have other options as well. You could
    display Flash videos easily, and I believe you could have the video
    open in a new top window. Same with images and gifs. Flex would be
    a very good choice I believe.

  • Flex 4 Release Build breaks text editor

    I was working on an editor using FB4 beta 2. Fonts were loaded at runtime ... CFF is being used.
    In Flex 4 SDK that comes with FB4 beta 2, my spark rich text field sitting in a group in my application looks fine - proper font families applied and renders correctly. My font + style drop down lists are all fine as well.
    As soon as I switch to the release SDK, or any SDK later than FB4 beta 2 (well, major releases) the font styles are not longer properly applied to the field. Changes to the family no longer apply to the rich text field.
    The rich editable text that I'm using is basically as follows:
                    <s:RichEditableText id="editor" fontLookup="embeddedCFF" renderingMode="cff"
                                        focusEnabled="false" x="100" y="50" focusIn="focusInEditor(event)" focusOut="focusOutEditor(event)"
                                        width="300" height="200">
                        <s:textFlow>
                            <s:TextFlow fontFamily="HelveticaNeueLTStd-MdCn">
                                <s:p fontFamily="HelveticaNeueLTStd-MdCn" fontSize="14" color="0x999999">Test first line of text</s:p>
                                <s:p fontFamily="HelveticaNeueLTStd-Blk" fontSize="18" color="0xFFFFFF">Test second line of text</s:p>
                            </s:TextFlow>
                        </s:textFlow>
                    </s:RichEditableText>
    That probably isn't too important but I figured I would paste it anyway. I'm using setFormatOfRange primarily and this block of textFlow was only to get some initial content into the text area.
    There is a ton of other related code for editing, selection, etc. It seems any font family related change does not get applied.
    I know there have been a ton of changes and this may be difficult to pin down. However, this is pretty awkward. The application I was building loaded up fine, fonts loaded up all fine and all editing worked perfectly until going to release SDK.
    Is there any change that would cause this to happen?

    Ok, so I finally got it working but this is not ideal at all. Adobe really needs to give us some direction on how to properly deal with font embedding and TLF now that the release build breaks all functionality with loading runtime fonts and TLF.
    Problem:
    I am embedding collections of fonts (faces) into single family classes. Each individual face is registered with Font.registerFont(). I need to do this because I have to have mixed fonts within text flows - at least according to Alex H's recent blog post.
    Fonts do not display in TLF without doing the following:
    1. GlobalSettings.resolveFontLookupFunction = null;
    2. editor.textFlow.flowComposer.swfContext = ISWFContext(this.getFontContext("AnyFamilyNameFromAnyFontEmbedded", false, false, FontLookup.EMBEDDED_CFF));
    3. Instead of #2, use editor.textFlow.invalidateAllFormats();
    Either #2 or #3 need to be performed. If I have a spark richEditableText control in MXML with defined familes from the loaded fonts. I even tried placing the control into a separate state so it wasn't created until after the fonts were loaded... I still needed to invalidate the formats or set the context.
    The "AnyFamilyNameFromAnyFontEmbedded" does not need to be all of the embedded family names. It only needs to be one of them. Once one is used, all embedded fonts work. Also, I have to use the internal namespace to even get access to getFontContext, another oddity that, in my humble opinion, should never be necessary to create mixed style TLF content.
    My questions are then:
    1. Why am I required to use ISWFContext if I am using Font.registerFont()?
    2. Why is GlobalSettings.resolveFontLookupFunction = null; also required for this to work?
    3. What is the recommended workflow to embed fonts from multiple SWF files into the release build and have it work without having to jump through all these hoops?

Maybe you are looking for

  • Tutorial filter

    Hi, I just purchased LabVIEW 8.2 Base development System Win 2000/XP.  I am already stuck in the 'Getting Started with LabVIEW Version 8.20' booklet of tutorials. I cannot work the Chapter 3 tutorial. In the subsection 'Modifying a VI created from a

  • Converting files to be iPod compatible

    Hi, I ripped some of my DVDs to my computer, but I'd like them to be also played on my iPod too, so can anyone suggest any (free would be nice) programs that can convert .avi to .mp4, but won't affect the size/quality of the file whenever it gets con

  • The trash file in my email empties by itself every few days. how do i set it so that the emptiing of the trash is left up to me?

    the trash file in my email empties by itself every 3 or 4 days. How can i empty if myself manually?

  • Getting error in FBCJ for tax codes

    Hi Gurus I have to make payment in the GL account for which in GL master data all tax types are allowed. I am getting following error in FBCJ posting You cannot enter tax code for business transaction Payments. Please advise urgently. REgards Ajay

  • Another export workflow option? A shortcut?

    Greetings. First, thanks to everyone on this and the FCE discussion for all the information and help that I've received. So now a question about our old friend export. I exported to my desktop a project from FC (AIC 1080/60 timeline-project) using th