Library Projects compiled using Flash Builder and ANT have different outputs

Question

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.!

Answer 1

#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.