I've changed my strategy a bit on this and I'm using the [Embed] directive with application/octet-stream.
It seems that there's some default compression going on when the MXMLC compiler embeds these text assets. Does anyone know what it is? I can't find much in the docs, though I probably missed it. Thanks --- In [email protected], "taude1" <tpreka...@...> wrote: > > Hello, > I'm using the command-line flex compiler to compile LZW resource strings > into a SWF that can be dynamically loaded into an application at run time. I > have no problem generating the Module and and loading it into the application > when I'm doing simple name value pairs. > I wish to use more complex name value pairings where the value is a LZW > compressed WSDL file... > I'm having issues with the encoded string wrapping multiple lines in the > resource file. I've tries appending the "\" at the end of the line, and this > seems to fix the problem of getting the resrouce SWF to actually compile. > However, it's (or something is) corrupting the compressed LZW string so it > doesn't decode properly. > > Anyone ever done anything like this? Any ideas? > > Thanks >
