Another possibility would be to somehow pass in the path to a server-loaded swf that is associated with the event (in your xml). The AIR app pulls down that Flex app, gives it the xml, and gets a PrintJob returned. That way, you have a single shared AIR app, with the ability to manipulate the layout logic via a deployed swf. If the layout changes, you simply redeploy the layout swf, which gets pulled down by the AIR app for the subsequent print job; avoids having to reinstall the AIR app for what are essentially presentation (read "we sent you the wrong logo", or "our printer can print with less than 1.25" margins") tweaks.
On Wed, Sep 8, 2010 at 3:44 PM, Laurence MacNeill <[email protected]>wrote: > Each show's badge is laid out differently... I've got all the code in my > Flex program to properly format the FlexPrintJob for the badge(s)... Was > just hoping to create that FlexPrintJob as-is, and pass it to the AIR > program... Just me bein' lazy... :-) > > Worst-case scenario, I simply copy that code from the Flex app to the AIR > app and run it from there, sending just a couple of lines of XML thru the > LocalConnection, containing the registration ID# and attendee # -- stuff the > AIR app can use to lookup all the data it needs to generate the FlexPrintJob > properly. > L. > > > On Wed, Sep 8, 2010 at 3:24 PM, Scott Talsma <[email protected]>wrote: > >> If you are just printing badges, how much info is there really to deal >> with? It seems to me that you can easily serialize the necessary data >> (backgroundImage, first, last, company, title) into xml. That can be sent >> to AIR, deserialized, laid out, etc. Then create the PrintJob on that side. >> >> >> I thought that you were trying to print arbitrary stuff; if it is only >> simple stuff, there probably isn't too much business logic to recreate on >> the AIR side. (And I have never done printing from Flash Player where I >> didn't have to go back and re-layout everything specifically for the print >> job anyway, so you will have specialized logic.) >> > > -- Scott Talsma CTO, echoEleven
