Flash Builder compiling

Will Flash Builder 4 also be able to publish AS3 based projects -> iPhone native apps as well or is this only going to be limited to Flash CS5.

Creating iPhone apps in ActionScript is on the Flex Builder roadmap, however it's not known at this point what version of Flash Builder will get that support.
However, as was shown in the MAX keynote and in other places e.g. Flash on the Beach, Flash Builder 4 and Flash Pro CS5 can be used together much more closely, editing in Flash Builder and having it publish/compile using Flash Pro, for example. So even if it's not directly supported in Flash Builder 4, you can use Flash Builder 4 as your editor and create an all-ActionScript project, and publish it using Flash Pro.

Similar Messages

  • Any clues on this error trace? Flash Builder compiling for iOS...

    Hi,
    All of a sudden, I am seeing the following when I try to compile an app for iOS:
    [code]
      Error occurred while packaging the application:
    # A fatal error has been detected by the Java Runtime Environment:
    # Internal Error (0xe06d7363), pid=3736, tid=7512
    # JRE version: 6.0_16-b01
    # Java VM: Java HotSpot(TM) Client VM (14.2-b01 mixed mode windows-x86 )
    # Problematic frame:
    # C [KERNELBASE.dll+0xc41f]
    # An error report file with more information is saved as:
    # C:\Users\GAIUSC~1\AppData\Local\Temp\AOT1351170957959\hs_err_pid3736.log
    [/code]
    The error log has been deleted by the time I get to it and there is no other clue, not aware of making any other changes that could affect it.
    Will try restarting but...
    Any clues or ideas would be welcome!
    Thanks,
    G

    Hmm.
    I have googled the error code C [KERNELBASE.dll+0xc41f] and it is suggesting an incompatibility with 64-bit versus 32-bit systems. I did previously install the 64-bit Flash Builder 4.7 trial, and then uninstall it again because it gave too many bugs on my machine and played havoc with FB 4.6.
    I will try in the 4.7 forum to see if they have any ideas.
    G

  • Flash Builder 4.5 + AIR 3.0 RC1 does not output modules to correct location

    Hello
    I'm having some trouble with Flash Builder 4.5 and Flex SDK 4.5.1.21328 with AIR 3.0 RC1. Flash Builder does not appear to compile modules into the location set in the "Edit module" dialog.
    The screenshots below show that the output path of a module is set to a specific folder, yet Flash Builder compiles the module into the default sub-folder.
    #1. Project properties showing application modules
    #2. Dialog showing the path to the module. Not the "Output SWF" location. The default location is the same as the package namespaces, eg: "d6/v3/banners/Banners.swf". After removing the path the module should compile into the output folder (set to bin/debug), however as the next screenshot shows, the module still compiles into the default sub-folder.
    #3. The module is compiled into a sub-folder of the output folder, instead of into the "root" of the output folder.
    #4. The output folder contains only the main application, with a sub-folder for the module.
    #5. Project pproperties showing the output folder.
    There is a workaround - move the module source file into the "Default package" in the package explorer.

    I experienced this problem today, and kind of "solved" it. There may be an underlying bug, though.
    My project compiled fine last Thursday, but I opened it up on Monday (unchanged) and this error showed up in several files. I tried quitting and restarting Flash Builder to no avail. I could not replicate the problem in a new project.
    For me, each occurence of the error was at a private function definition, so I thought I would try changing "private" to "public" on one of the functions. The error immediately went away in all 3 locations (not just the one I edited). I then changed it back to "private" with no error.
    I hope that will help the Adobe team track down the problem.

  • Flash Builder and Flex4 SDK 9731+ issue

    Hello everyone. I've been working with Flash Builder Beta and latest Flex4 SDK nightly builds for some time now and did not have any major obsticles.
    That was until I downloaded 9731 build. Flash Builder compiled my project without any problem, however, when I tried to launch the application in my browser I've got these errors:
    VerifyError: Error #1014: Class IVisualElement could not be found.
    (after I click continue)
    ReferenceError: Error #1065: Variable CrossFade_CrossFadeShaderClass is not defined.
    (after that)
    ReferenceError: Error #1065: Variable Wipe_WipeShaderClass is not defined.
    (and after that)
    ReferenceError: Error #1065: Variable _cfdd017153b35cc39170086d5b82e02ae917ac7c68abee5c5b64ce1a052a4aac_flash_display_Sprite is not defined.
    Of course when I click "Continue" nothing shows up on the screen.
    The only similar issue I've managed to find is related with Flexmojos (http://code.google.com/p/flex-mojos/issues/detail?id=163) which, I think, has nothing to do neither with Flex4 SDK nor Flash Builder in this case.
    Maybe anyone has ideas about this? Does this have something to do with Flash Builder incompatibility with nightly SDK builds? Or maybe the new SDK
    has not been built correctly?
    By the way, I've decided to stick with 9674 built and wait for more nightly builds when I first encautered this problem. Today I've downloaded 10008 built of
    Flex4 SDK and the problem is still there.

    Hello ThinkLoop;
    I have .10339 now working with no new issues.  If this helps I started a discussion (below) in which I was getting an error, the error given seemed unrelated to the fix but... essentially when recreating the project, which seems to be a common event when updating the SDK, I have to re-attach the modules to the project.
    Author
    Subject
    Views
    Replies
    Last Post
    jdesko
    Nightly SDK and Flash Builder Betain Flash Builder and Flex SDK
    121
    8
    35 minutes agoby jdesko

  • How can I get to the compiler arguments in Flash Builder 4.6?

    Howdy!
    So far I've been unable to locate any information that could help me with my task. The ultimate goal is to build my project's SWF with mxmlc. I was not able to figure it out and thought I'd install Flash Builder in the hopes of being able to get to the compiler arguments. No luck.
    First, I'm not the lead on the building of the SWF. This is done by another person via the Eclipse plugin; her hard drive crashed last night too. In fact I'm not a Flash developer. I'm coming at this from a Build Infrastructure perspective.
    Any help would be greatly appreciated.
    Cheers,
    Mel Riffe

    Mel Riffe,
    Here's a Help topic about compiler options in Flash Builder: http://help.adobe.com/en_US/flashbuilder/using/WSe4e4b720da9dedb524b8220812e5611f28f-7fe7. html
    For information on using mxmlc, the application compiler, to compile SWF files from your ActionScript and MXML source files, you can see: http://help.adobe.com/en_US/flex/using/WS2db454920e96a9e51e63e3d11c0bf69084-7fcc.html
    Hope this helps,
    Mallika Yelandur
    Flash Builder Community Help & Learning
    Adobe Systems Incorporated

  • Flash builder 4.7 air 3.6 new adt compiler

    Hi. Ive been having serious issues when i tried to "Export release build" using air 3.4 and/or air 3.5 on Flash builder 4.7. Goit a lot of nonsense java.lan.nullpinter exceptions and similar errrors.
    When i tried to debug or run, even on device generating the ipa, everything ok. But when i tried to export the project, and it tried to re-compile it, always got absurd java errors.
    Ive tried everything: downgrade the java virtual machine, reinstalling flash builder, air, even windows!!! Nothing worked. Even recovering previous stages of the project where I originally could export it (its even published on the appstore!). No use. The app that was working no problem, now when trying to export returns a lot of javanull pointers or similar crap.
    BUT, when trying to generate the ipa through via command lines  on the ms dos console it works!! So... its obvious the problem was on the adl+java duo.
    Thing is, I updated to the just released AIR 3.6 (not the beta, the release version). It uses .exes(on windows, which is the system im using)  instead of java, so it showed promise.
    I overlayed the air version on the flash builder following this instructions:
    http://forums.adobe.com/message/4797974
    Well, not exaclty, because then flash builder throws a lot of errors and dosent show me the package explorer for instance.
    I made a copy of the AIR folder, but not deleted the content, just copied the new air version files over and substitute the replicas, but kept the originals where no new file substituted them (dont know if im explaining it ok, sorry for my english).
    It worked... except for the damn "Export release build" option. It keeps trying to debug it using java instead of using the new adt. And I cant find how to change that.
    The adt on the other hand is being used ok, as i can check it when I try to run or debug the project targetting a device. Before I could check the command used and now Im not, so Im pretty sure its using the new .exe instead of the java version. But now I dont know how to generate the ipa targetting the app store, for instance via command line using the new adt nor can i do it exporting the project from the flash builder IDE.
    SO...
    is there anyone having similar problems?
    How can I correctly overlay air 3.6 over Flash Builder 4.7 and force it to use the new air adt and adl?
    Anyone tried?
    Thanks in advance folks!!!

    Thanks everyone for your collaboration.
    Hey Nabren, What do you mean by "as well"?
    Just to make it clear. I already followed the instructions here:
    http://helpx.adobe.com/flash-builder/kb/overlay-air-sdk-flash-builder. html
    to overlay the air sdk. And the folder you are pointing me is the ONLY ONE the instructions tell me to replace. BUT when you say "as well" I understand something else have to be done.
    Ill explain the whole process Ive followed and the consequences:
    As I said I replaced the content on the AIRSDK placed in the fodler C:\Program Files\Adobe\Adobe Flash Builder 4.7 (64 Bit)\eclipse\plugins\com.adobe.flash.compiler_4.7.0.349722 (or similar), for the content of the new SDK.
    The result is that flash builder throws me a lot of errors and is unable  to show even the package explorer, for instance or create a mobile project, so I went back to the original AIR folder. No problem there.
    When I was using flash builder 4.6 I overlayed the sdks in this way: made a copy of the last flex SDK (which already had the air sdk inside), and copied the content of the  latest AIR SDK over the current sdk, replacing only new files, keeping those not includded on the air sdk. That way I could keep several flex+air sdks, and could select wich sdk to use for each library/project. Now this doesnt work anymor on flahs builder 4.7.
    So I tried this:
    I made a copy of the AIR sdk under C:\Program Files\Adobe\Adobe Flash Builder 4.7 (64 Bit)\eclipse\plugins\com.adobe.flash.compiler_4.7.0.349722 and copied over the new sdk ont he folder overwritting new files,keeping those not included on the new sdk... and this works! Everythings fine. I can debug complex projects on air simulator even launch it on an iphone or ipad...
    BUT it keeps throwing me JAVA errors (null pointer exceptions and things like that) when exporting that makes no sense at all (different errrors without making any change, now no error now another one...).
    More info on the projects provoking this behaviour:
    They are mobile projects (ios mainly). They use several libraries. Some of them come from compiled swcs from flash cs6 (wich contains classes we are using as views). All libraries have been double checked. They are fine. The problems emerge when trying to export targetting the apple store. Weve double checked the provisioning and the certificate. They are correct. In fact, when we try to generate the ipa using adt via command lines on ms-dos it works!
    Weve tried to remake and the rebuild the project class by class, even recreate the flas we are using to generate the swcs to be used as libraries on the project... it only works when the project is almost empty. As soon as some content is added.. bumm! Java errrors all over when trying to export.
    Our main machine is an i7 2.93 Ghz, 8 GB ram, 64 bits. Windows 7 Ultimate 64 bits, using Flash builder 4.7 64 bits and flash cs6 64 bits. But we have checked on other mahines and sme thing happens.
    Doesnt anyone else have these problems? Is there any other way to overlay the air sdk?
    Thanks again.

  • Flash builder 4.7 AIR 17 compile-abc-64 fail on x32 OS

    Ls,
    Since AIR 16 I cant compile to iOs on my x32 Os (windows vista ultimate)
    On my laptop its fine, uses x64 windows 7.
    Failure because of compile-bc-64.exe not working on x32 (makes sense sure)
    So: Is there a way to not have it use the -64.exe but only the normal compile-abc.exe?
    Flash builder: 4.7
    AIR sdk: latest two 16. & 17
    OS: windows Vista ultimate x32
    Highest regards,
    Mac

    I finally found what probelem i have. Visual studio has corrupted one dll. Flahs is crashing due to my browser in 64bits which has problem. I found that it could be a probleme while installing a .net framework. But unfortunately i can't delete or uninstall this framework, i had no option to uninstall it. I guess the best way is to format my computer. But as i am waiting for a new worksatation dedicated to your tool and zbrush of course(for stage3d is a real improvment), i won't format it now it would take too much time to resintall everything and i would have to do this again when i will received my workstation
    If someone has problem like that there might be a solution(not the best but at least it works)
    To solve my problem as i have to make an app in flash builder. I downloaded the 32 bits version of flash builder 4.7. And i will resintall the 64 bits as soon as i received my workstation.

  • Flash Builder 4.7 - Command line ExportReleaseBuild unable to compile to Captive Runtime?

    Hi,
    I am working on a project with the following setup:
    - AIR Desktop running with the ExtendedDesktop Profile with GPU rendermode
    - Apache Flex SDK 4.11
    - SWF version 18
    - Implements the FRESteamWorksNative Extension
    - Flash Builder 4.7 Premium is our work enviroment
    Our problem is that we can compile the project in Flash Builder manually as Captive Runtime, but when we run it with ExportReleaseBuild in our build.xml, it seems to forget our Captive runtime target and just outputs the installer.
    This is our buildscript:
    build.bat:
    SET FLASHBUILDER="%ADOBE_PATH%\%FLASHBUILDER_PATH%\FlashBuilderC.exe"
    %FLASHBUILDER% --launcher.suppressErrors -noSplash -application org.eclipse.ant.core.antRunner -data "%WORKSPACE%" -file "%BUILDXML%" desktop
    build.xml:
    <target name="desktop">
         <fb.exportReleaseBuild verbose="true" destdir="bin-test" project="ProjectName" basefilename="ProjectBaseFileName" packagetype="native" certificate="Certificate.p12" password="passwordToUse"/>
    </target>
    .actionScriptProperties:
    <buildTargets>
        <buildTarget buildTargetName="default" platformId="default">
          <airSettings airCertificatePath="Certificate.p12" airTimestamp="true" anePathSet="true" version="1">
            <airExcludes/>
            <anePaths>
              <anePathEntry path="steamworks/FRESteamWorks.ane"/>
            </anePaths>
            <newLaunchParams/>
            <modifiedLaunchParams/>
            <newPackagingParams/>
            <modifiedPackagingParams>
              <Parameter name="-target" value="air-captive"/>
        <Parameter name="-extdir" value="steamworks/"/>
            </modifiedPackagingParams>
          </airSettings>
          <actionScriptSettings version="1"/>
        </buildTarget>
      </buildTargets>
    Any help with this is much appreciated, and if I missed something, please let me know.

    Hi,
    I've opened bug at Adobe site:
    Bug#3801869 - FlashBuilder 4.7 command line fails due to "Exception in com.adobe.flexbuilder.codemodel.CMCoreActivator.s…
    please vote on the bug.
    thanks,
    Erez

  • Flash Builder 4.7 conditional compiling failed

    I installed Flash Builder 4.7 on my windows xp machine, and tried to migrate projects from FB 4.6. However in one of my projects I use conditional compiling, but I'm getting errors.For example in FB 4.6 I have this sample code:
    public class MyClass{
         CONFIG::DEBUGGING{
              import com.package.SomeClassOnlyForDebugging
         function someFunction():void{
              if (CONFIG::DEBUGGING){
                   SomeClassOnlyForDebugging.create();
    When I compiled it in FB 4.6 everything worked fine. However when I try to compile it in FB 4.7, then I get error on the conditional compiling only inside the function and not on the import statement. The only way I have found to overpass it is to go to Project>Properties>ActionScript Compiler and disable Enable strict type checking. But this is not a permanent solution.
    Am I doing something wrong, or is there some other way to do it?

    You should to do like that:
    function someFunction():void
    CONFIG::DEBUGGING {
         SomeClassOnlyForDebugging.create();
    without if.

  • Flash Builder 4.7 frequent compiler issues/restarts

    Basically Flash Builder 4.7 on Mac OSX 10.7.5 is unusable. Very frustrating.  Constant compiler issues that require frequent cleaning, closing of projects, restarts of FB, and even re-installs.  I've seen none of these issues on FB 4.6 with the same projects/code.
    The most common visible compiler errors are these two that randomly appear:
    1) An internal build error has occurred
    2) classes must not be nested
    I tried increasing memory as some have suggested, but this has no effect.
    It takes me 100 times longer to code now becuase every tiny code change cuases these errors.  Crazy!
    Before I revert back to FB 4.6, any suggestions? 
    Thanks,
    Don

    Hi!
    Close any unneeded projects in workspace.
    You can also split your large project to few libraries compiled into SWC. After compiling libraries, if not need to change often, close their projects. When such projects are closed main project compiling with just use of SWC libraries usually takes much less resources.

  • Flex Application Only Compiles in Flash Builder

    Hello,
        I am a newbie trying to become familiar with Flex.  I am starting by building and running some sample applications.  For some reason, the applications will execute inside of FlashBuilder, but I am getting a compile error when I compile them on my linux box. The I used the Flash Builder remote services finder to generate the code for the remote service.  The class that produces the error was generated by Flash Builder.  I have appended the class at the bottom of this post.  Any suggestions?  Thanks in advance.
    --Marco
    [mjmatch@mjmatch-linux flexsphi]$ ant
    Buildfile: build.xml
    compile-flex:
        [mxmlc] Loading configuration file /opt/tools/flex-sdk/4.1/frameworks/flex-config.xml
        [mxmlc] /opt/tools/blazeds/4.0.0/tomcat/webapps/flexsphi/src/client/services/_Super_Foo.as(20): col: 68 Error: The definition of base class RemoteObjectServiceWrapper was not found.
        [mxmlc] internal class _Super_Foo extends com.adobe.fiber.services.wrapper.RemoteObjectServiceWrapper
        [mxmlc]                                                                    ^
    BUILD FAILED
    /opt/tools/blazeds/4.0.0/tomcat/webapps/flexsphi/build.xml:16: mxmlc task failed
    Environment
    =========
    Flex SDK 4.1
    Flash Builder 4
    ant compile tasks
    ============
        <property name="FLEX_HOME" value="/opt/tools/flex-sdk/4.1"/>
        <property name="DEPLOY_DIR" value="/opt/tools/blazeds/4.0.0/tomcat/webapps/flexsphi"/>
        <property name="CONTEXT_ROOT" value="flexsphi"/>
        <taskdef resource="flexTasks.tasks" classpath="${FLEX_HOME}/ant/lib/flexTasks.jar"  />
        <target name="compile-flex">
            <mxmlc file="src/client/Main.mxml"
                    services="${DEPLOY_DIR}/WEB-INF/flex/services-config.xml"
                    context-root="${CONTEXT_ROOT}"
                    output="${DEPLOY_DIR}/flexsphi.swf"/>
        </target>
    _Super_Foo
    =========
    * This is a generated class and is not intended for modification.  To customize behavior
    * of this service wrapper you may modify the generated sub-class of this class - Foo.as.
    package services
    import com.adobe.fiber.core.model_internal;
    import com.adobe.fiber.services.wrapper.RemoteObjectServiceWrapper;
    import com.adobe.serializers.utility.TypeUtility;
    import mx.rpc.AbstractOperation;
    import mx.rpc.AsyncToken;
    import mx.rpc.remoting.Operation;
    import mx.rpc.remoting.RemoteObject;
    import valueObjects.Bar;
    import mx.collections.ItemResponder;
    import com.adobe.fiber.valueobjects.AvailablePropertyIterator;
    [ExcludeClass]
    internal class _Super_Foo extends com.adobe.fiber.services.wrapper.RemoteObjectServiceWrapper
        // Constructor
        public function _Super_Foo()
            // initialize service control
            _serviceControl = new mx.rpc.remoting.RemoteObject();
            // initialize RemoteClass alias for all entities returned by functions of this service
            valueObjects.Bar._initRemoteClassAlias();
            var operations:Object = new Object();
            var operation:mx.rpc.remoting.Operation;
            operation = new mx.rpc.remoting.Operation(null, "getBars");
             operation.resultElementType = valueObjects.Bar;
            operations["getBars"] = operation;
            operation = new mx.rpc.remoting.Operation(null, "addBar");
            operations["addBar"] = operation;
            _serviceControl.operations = operations;
            _serviceControl.convertResultHandler = com.adobe.serializers.utility.TypeUtility.convertResultHandler;
            destination = "foo";
             model_internal::initialize();
          * This method is a generated wrapper used to call the 'getBars' operation. It returns an mx.rpc.AsyncToken whose
          * result property will be populated with the result of the operation when the server response is received.
          * To use this result from MXML code, define a CallResponder component and assign its token property to this method's return value.
          * You can then bind to CallResponder.lastResult or listen for the CallResponder.result or fault events.
          * @see mx.rpc.AsyncToken
          * @see mx.rpc.CallResponder
          * @return an mx.rpc.AsyncToken whose result property will be populated with the result of the operation when the server response is received.
        public function getBars() : mx.rpc.AsyncToken
            var _internal_operation:mx.rpc.AbstractOperation = _serviceControl.getOperation("getBars");
            var _internal_token:mx.rpc.AsyncToken = _internal_operation.send() ;
            return _internal_token;
          * This method is a generated wrapper used to call the 'addBar' operation. It returns an mx.rpc.AsyncToken whose
          * result property will be populated with the result of the operation when the server response is received.
          * To use this result from MXML code, define a CallResponder component and assign its token property to this method's return value.
          * You can then bind to CallResponder.lastResult or listen for the CallResponder.result or fault events.
          * @see mx.rpc.AsyncToken
          * @see mx.rpc.CallResponder
          * @return an mx.rpc.AsyncToken whose result property will be populated with the result of the operation when the server response is received.
        public function addBar(arg0:String) : mx.rpc.AsyncToken
            var _internal_operation:mx.rpc.AbstractOperation = _serviceControl.getOperation("addBar");
            var _internal_token:mx.rpc.AsyncToken = _internal_operation.send(arg0) ;
            return _internal_token;

    The SWC files are within the resource directory of LCDS.
    For example:
    C:\lcds31\resources\lcds_swcs\FlexSDK4\frameworks\locale\en_US
    fiber_rb.swc
    C:\lcds31\resources\lcds_swcs\FlexSDK4\frameworks\libs
    fiber.swc and fds.swc
    You can use the following within ANT.
    <!-- Get default compiler options. -->
              <load-config filename="${FLEX_HOME}/frameworks/flex-config.xml"/>
                <!-- List of path elements that form the roots of ActionScript
                class hierarchies. -->
                <source-path path-element="${FLEX_HOME}/frameworks"/>
              <!-- List of SWC files or directories that contain SWC files. -->
                <compiler.library-path dir="${FLEX_HOME}/frameworks" append="true">
                    <include name="libs" />
                    <include name="../bundles/{locale}" />
                </compiler.library-path>

  • Flash Builder fails to copy over static files in incremental compiles

    During incremental compiles, the Flash Builder fails to copy over certain static files (such as *.js and html files).  I have my own html wrapper and during incremental compiles it fails to copy over this file and also deletes the file from bin-debug/bin-release.  I have to do a clean build instead to ensure these files are copied over.

    Just tried this out on an IIS server with Flash player 10.3.181.14 - it worked.
    Are you using the release version of Flash Builder 4.5 with the release version of Flex SDK (not a prior SDK build)?
    The URL you mentioned gives me a 403 forbidden error.
    -Anirudh

  • Flash Builder 4.5.1 - Problem compile Flex Mobile release build

    I am building a flex mobile applicaiton using Flash Builder 4.5.1. The application works fine on the device (Nexus S) and desktop in the debug mode however, whenever I export the release build the app is not installed on the device automatically. When I manually install .apk it also fails (get Application not installed message with green check mark). Any thoughts?

    Getting a big closer... Compiled .swf using mxmlc, then manually packaged .apk without any issues... When I try to run: adb install -r myapp.apk: I get the following error:
              pkg: /data/local/tmp/myapp.apk
    Failure [INSTALL_PARSE_FAILED_NO_CERTIFICATES]
    Perhaps certificates are not respected?

  • Library Projects compiled using Flash Builder and ANT have different outputs

    Hi Guys.,
    I am really having hard time to get something work right with RSL projects in Flex 3.2 SDK. Here is my weird problem.
    I have a library projects which has the following settings in Flash Builder
    Link Type : External
    airglobal.swc
    framework.swc
    datavisualization.swc
    rpc.swc
    utilites.swc
    applicationupdater.swc
    applicationupdater_ui.swc
    Link Type: Merged into code
    airframework.swc
    servicemonitor.swc
    Compiler settings
    -directory=true -output=../../lib/core -debug=true -optimize=false -define+=CONFIG::bindingdebug,false -define+=CONFIG::frameworkdebug,false -define+=CONFIG::flexspy,true -define+=CONFIG::debug,true -define+=CONFIG::release,false -define+=CONFIG::logtoconsole,false -allow-source-path-overlap=true  -keep-as3-metadata+=Metadata,DefaultProperty,Required,Event,AssignableTo,Inject,InjectCon structor,Publish,Subscribe,PublishSubscribe,Factory,Init,Destroy,Observe,AsyncInit,Managed Events,MessageDispatcher,MessageHandler,MessageBinding,MessageInterceptor,MessageError,Com mand,CommandComplete,CommandResult,CommandError,CommandStatus,ResourceBinding,Selector,Tar get,Autoremove,Internal,ObjectDefinition,DynamicObject
    When I compile my library projects I get a MyLibraryproject.swc. The SWC has the following files in it
    mx/controls/HTML.png
    mx/core/Windows.png
    library.swf
    Note: airframework.swc and servicemonitor.swc has a many png files and properties files in it. But these properties and png files are not included when compiled in Flash builder.
    But when the same project is compiled using ANT compc task, i get all the png and properties files from airframework.swc and servicemonitor.swc files into my library project SWC file.
    Here is the ANT version which is used to compile the library project
    <compc output="${project.output.dir}/${project.name}.swc"
       include-classes="${as} ${mxml}"
       use-network="false"
       directory="false"
       allow-source-path-overlap="true"
       incremental="${build.incremental}"
       debug="${build.debug}"
       locale="${build.locale}"
       optimize="false"
       >
    <define name="CONFIG::bindingdebug" value="${build.bindingdebug}" />
    <define name="CONFIG::logtoconsole" value="${build.logtoconsole}" />
    <define name="CONFIG::frameworkdebug" value="${build.frameworkdebug}" />
    <define name="CONFIG::flexspy" value="${build.flexspy}" />
    <define name="CONFIG::debug" value="${build.debug}" />
    <define name="CONFIG::release" value="${build.release}" />
    <keep-as3-metadata name="Metadata" />
    <keep-as3-metadata name="DefaultProperty" />
    <keep-as3-metadata name="Required" />
    <keep-as3-metadata name="Event" />
    <keep-as3-metadata name="AssignableTo" />
    <keep-as3-metadata name="Inject" />
    <keep-as3-metadata name="InjectConstructor" />
    <keep-as3-metadata name="Publish" />
    <keep-as3-metadata name="Subscribe" />
    <keep-as3-metadata name="PublishSubscribe" />
    <keep-as3-metadata name="Factory" />
    <keep-as3-metadata name="Init" />
    <keep-as3-metadata name="Destroy" />
        <keep-as3-metadata name="Observe" />
        <keep-as3-metadata name="AsyncInit" />
        <keep-as3-metadata name="ManagedEvents" />
        <keep-as3-metadata name="MessageDispatcher" />
        <keep-as3-metadata name="MessageHandler" />
        <keep-as3-metadata name="MessageBinding" />
        <keep-as3-metadata name="MessageInterceptor" />
        <keep-as3-metadata name="MessageError" />
        <keep-as3-metadata name="Command" />
        <keep-as3-metadata name="CommandComplete" />
        <keep-as3-metadata name="CommandResult" />
        <keep-as3-metadata name="CommandError" />
        <keep-as3-metadata name="CommandStatus" />
        <keep-as3-metadata name="ResourceBinding" />
    <keep-as3-metadata name="Selector" />
    <keep-as3-metadata name="Target" />
    <keep-as3-metadata name="Autoremove" />
    <keep-as3-metadata name="Internal" />
    <keep-as3-metadata name="ObjectDefinition" />
    <keep-as3-metadata name="DynamicObject" />
    <load-config filename="${air.config}"/>
    <compiler.include-libraries dir="${flex.frameworks.dir}/libs/air" append="true">
         <include name="servicemonitor.swc" />
         <include name="airframework.swc" />
    </compiler.include-libraries>
    <external-library-path dir="${build.compc.dir}" append="true">
         <include name="TriGeoFlexFramework/TriGeoFlexFramework.swc" />
         <include name="TriGeoLibrary/TriGeoLibrary.swc" />
         <include name="TriGeoRPCFramework/TriGeoRPCFramework.swc" />
         <include name="Degrafa_Beta3.1_Flex3" />
         <include name="parsley-flex3-2.4.0.swc" />
         <include name="spicelib-flex-2.4.0.swc" />
    </external-library-path>
    <external-library-path dir="${flex.frameworks.dir}/libs" append="true">
         <include name="framework.swc" />
         <include name="datavisualization.swc" />
         <include name="utilities.swc" />
         <include name="rpc.swc" />
         <include name="air/airglobal.swc" />
         <include name="air/applicationupdater.swc" />
         <include name="air/applicationupdater_ui.swc" />
    </external-library-path>
    <source-path path-element="${basedir}/src" />
    </compc>
    </target>
    </project>
    Any insights is greatly appreciated.!

    #1, If it compiles then you have no issue. There's no reason at this point not to use 4.6. You should bundle a captive runtime to assure the users computer won't need to have AIR installed at all.
    #2, Papervision is old. Use the Stage3D and/or a wrapper framework. As far as the generic "If I download lots of data will it take the user more time to load it", well, of course. Just don't make the loading experience painful. Entertain them while they way or find ways of displaying data sooner than later. If it's desirable on the web has more to do with the context of the app and the device displaying it. In other words, a phone user would find it easy but obviously not a desktop user.
    #3, Definitely referring you to Google on that one.
    #4, Size always matters, it's common sense. The more you process the harder it is. While I haven't done AR I've used the Microsoft Kinect SDK and ANE and tracking was extremely fast but limited. From what I've seen and your basic built in location and direction hardware on any mobile device you shouldn't have much trouble. Depends on what you're doing.
    #5, This discussion would be way too large for a forum. You'd need to consult a firm experienced in AR development.
    #6, "Applications using the commercial license do not have to provide source code, but must pay a licensing fee. Contact ARToolworks at [email protected] for more information." They will base your price on your product, there is no single price.
    #7, The models could be huge and elaborate or tiny and simple which changes the answer. Consult the answer in #4. Ultimately most people are getting on fast networks with mobile and excessively fast on desktop/wifi. Size matters a lot less than 3 years ago.
    #8, Depends on what you're doing. You have to explain it.

  • Flash Builder no longer compiles a project

    After my last edit - no syntax errors - of a given project, Flash Builder no longer builds my project.
    Restarted Flash Builder. Created a new project and copied all sources. Nothing helps. It just doesn't create the binary.
    I see two problem reports.
    Most of the time this one:
        An internal build error happened. See the error log for further details.
    Then, sometimes, this one appears:
       Classes aren't allowed to be defined inside other classes.
    The project is syntactically free of errors.
    As soon as I remove the main component from the App.mxml, the build finishes orderly and the app starts up. In this case - as expected - with a blank window.
    Does a workaround solution exist?  Does certain size restrictions make the build fail?
    OS:
       Mac OS X Lion.
    Bug-Report:
       http://bugs.adobe.com/jira/browse/FB-32216

    Unbelieveable. After 2 day, I found the problem right now:
    I wrote
      private var baseNiceText =  String = '';
    instead of
      private var baseNiceText :  String = '';
    After I changed the source and recompiled, the app builds.
    Anyway, it's a problem inside of compiler.

Maybe you are looking for