So I cannot send a FlexPrintObject over an L.C., is what you're saying? Hmmmm... Is there a way to send a FlexPrintJob object directly from the Flex app to the AIR app?
On Sep 7, 2010 7:15 PM, "Scott Talsma" <[email protected]> wrote: > The local connention idea will only work if you can serialize your data to a > string (XML). You cannot send serialized data over an lc. If you can do > that, then compose the XML and send it in chunks w an anknowledgemenr each > time from the reciever sent over a 2nd lc. When you are out of data to send, > the flex app calls a secondary fn that starts tearing down the 2 LCs. > > Sent from my iPhone > > On Sep 7, 2010, at 6:47 PM, Laurence MacNeill <[email protected]> > wrote: > > The launching of the AIR app from the Flex app sounds like a better idea, > actually... Then the Flex app has the control over the AIR app, which is > what I want, it would seem... > > I'm thinking the AIR app would be just a simple thing, taking the > FlexPrintJob object and a printer-name of some sort, and just sending the > job straight to that printer... > > So, once the AIR app is open, Flex wouldn't need to open it again, > obviously. It would seem that I would need to make a LocalConnection to the > AIR app -- but documentation on that is pretty spotty, it seems. And there > also seems to be a limit on the amount of data you can pass over a > LocalConnection -- 40KB, I think? How do I pass a large FlexPrintJob > through that, with that kind of limit on it? > > Any ideas or suggestions? > > Thanks, > L. > > On Mon, Sep 6, 2010 at 10:18 PM, Douglas Knudsen > <[email protected]>wrote: > >> Yet another possibility is to create a Air based app for the printing and >> have the Flex application open it, passing needed data to it for the >> printing. >> >> A example of opening launching a AIR app from Flex can be found here >> >> http://www.medoix.com.au/2009/11/06/install-launch-air-application-from-flex-web-page/ >> Note there is a way to do this without the Adobe air.swf, but its no >> documented :) >> >> >> Douglas Knudsen >> [email protected] >> >> >> >> On Sep 6, 2010, at 4:53 PM, Scott Talsma wrote: >> >> Another approach would be to create an AIR wrapper that encapsulates your >> print functionality. The AIR wrapper then loads the Flex app >> (mx:Application). You simply put together what you want to have printed >> (FlexPrintJob) and then pass the instance up the parent chain. That way you >> can continue to maintain your Flex app as you are currently while slowly >> getting your feet wet in the AIR world w/o committing the entire application >> to AIR. (Additionally, you can continue to host the Flex portion online for >> update purposes; you just point the AIR "print client" at its URL.) >> >> On Mon, Sep 6, 2010 at 4:10 AM, Darin Kohles <[email protected]> wrote: >> >>> As (now) a desktop app. vs a web served swf: >>> >>> If you want to do it by hand, you'll have to change the main file from >>> <mx:Application> to <mx:WindowedApplication>; do a diff on the "." files in >>> the project folder (compare to a generic Air app), 'cause there are a few >>> changes. >>> >>> If you want to add network sensitivity there is a bit more coding, >>> otherwise have your "not connected"/"fault" errors handled appropriately. >>> >>> >>> That's about it! ... of course there is digital signing, update awareness, >>> @etc;. >>> >>> >>> On Sat, Sep 4, 2010 at 2:39 PM, Laurence MacNeill < [email protected] >>> > wrote: >>> >>>> To clarify, I'm aware that FB4 has a "convert from Flash to AIR" >>>> wizard... I don't trust wizards to actually do the right thing, in most >>>> cases... In fact, I generally find that they break more than they fix... >>>> So, I guess I'm asking for your experiences with this wizard, if you have >>>> any... >>>> >>>> Thanks, >>>> L. >>>> >>>> >>>> >>>> On Sat, Sep 4, 2010 at 5:31 PM, Laurence MacNeill < >>>> [email protected]> wrote: >>>> >>>>> So... With all this discussion of printing from Flash Player and >>>>> whatnot, it seems almost certain that we're going to have to switch to >>>>> AIR... >>>>> >>>>> Has anyone here ever taken a fairly mature app from Flash Player to >>>>> AIR? I'm certain it can't be as simple as checking the "AIR App" button in >>>>> the FB4 Project Properties window -- there must be something else (or many >>>>> things) that I'm going to have to change/adjust/re-write... The app >>>>> currently interacts a great deal with our CF server, and I'd imagine that's >>>>> going to have to change somehow, yes? User authentication would probably >>>>> have to change as well, I would assume? >>>>> >>>>> Can anyone offer any advice along these lines? If anyone here has ever >>>>> done what I'm thinking about doing, please let me know about your >>>>> experiences. >>>>> >>>>> Thanks, >>>>> Laurence MacNeill >>>>> Mableton, Georgia, USA >>>>> >>>>> >>>> >>>> >>> >>> >>> -- >>> Darin Kohles >>> Adobe Certified Developer >>> >> >> >> >> -- >> Scott Talsma >> CTO, echoEleven >> >> >>
