bumpI think there are a few of us looking to dynamically link framework swf's (as rsl's) into our work. Any further info?Is the RSL/linker guy back? :)ThanksAngus
On 29/09/06, Mike Morearty [EMAIL PROTECTED] wrote:
I don't think this is necessary. I gave a
Thanks for the reminder :-) Yes, the RSL/linker guy is back.
There are several options:
* Use the existing framework.swc as an RSL.
* You can compile your main app with the -include-libraries command-
line option, to entirely pull certain libraries into your main app.
For example, if you
Thanks Mike. Second option seems the way to go for this project. (Using the standard framework as an rsl triggers the prompt for debugger location the guys mentioned earlier in the thread).CheersAngus
On 10/10/06, Mike Morearty [EMAIL PROTECTED] wrote:
Thanks
The problem is with the way the player and the debugger initiate
their communication. Here's how it works when things are going well:
1. When you click Debug in Flex Builder, it starts listening on a
TCP/IP socket, and it launches your browser.
2. When the Flash Player notices that the SWF
Hi Mike,Maybe If I could set -debug=false for each RSL would avoid that problem?but, if so...how could I set that param for a RSL? I think I can only put that additional param for the main project.
On 9/28/06, Mike Morearty [EMAIL PROTECTED] wrote:
The
Thanks Mike. Is there a way to launch the debugger manually, from Flex
Builder. For instance to wait for incoming requests from the player. I
realize the command line debugger would likely work but the GUI would be
much easier.
Mike Morearty wrote:
The problem is with the way the player and
There is a hack way to launch the debugger manually: create a launch
configuration where the debug URL points to some random page that
doesn't have a SWF on it, like http://www.google.com. A browser will
come up, but you can just close it.
--- In flexcoders@yahoogroups.com, Paul Spitzer
Try putting -debug=false into the Additional Compiler Options field
of the Flex Library Project that was used to build the SWC. Not sure
if that works, but it might.
If it doesn't, I know this is a lot of work but you could do a
command-line build with compc.exe (the swc building tool).
---
Mike,
Is there way to get standard libraries (framework, rpc, flex, etc) built with -debug=false Thank you,
Anatole
On 9/28/06, Mike Morearty [EMAIL PROTECTED] wrote:
The problem is with the way the player and the debugger initiate their communication. Here's how it works when things are
Ok, As Anatole brings to the light, I want to use framework.swc and flex.swc as RSLs, but I can't compile it with -debug=false since I haven't the project that generates the SWC...maybe someone at adobe could give us the project templates so we can set up in our enviroment. could it be
Are you changing them to be external, rather than statically linked
into your app? Because if you're leaving them statically linked into
your app (the default), then there is no need to recompile them with -
debug=false; at link time, if linking the release swf, the linker will
strip out all
Mike,
It might make sense to have separatefolder in SDKwith all the libraries compiled without debugging for size/performance reasons. Realistically, every production application would like to benefit from that and subjecting everybody to Ant process - especially given the additional libs like
I don't think this is necessary. I gave a pointer to how to
recompile it because someone asked, but it is deliberate that we only
ship a single swc: as I said, when you link that swc into your
project, it strips out all the debug information. There is no
performance or size hit on your swf.
13 matches
Mail list logo
