Whoops, I saw AIR, but it didn't register completely, hence my focus on client vs server functionality. That is different with AIR.
Not having much experience with AIR, I suggest you repost your question under a descriptive subject, in hopes that an AIR developer here will see and respond. Now, one issue with AIR is that it is designed to be platform independent. This creates limitations with accessing native programs. But re-post, since I am mostly useless on this one. Also, search the archives, and try google. Tracy ________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of bredwards358 Sent: Monday, April 21, 2008 2:33 PM To: [email protected] Subject: [flexcoders] Re: Hello, and a question... Thanks and I'll be sure to be mindful of that in the future. First off I am not wondering if I can get an AIR app to run on a PALM device, as I'm pretty sure that can't happen. I am wondering about how to accept input from a PALM device. Some parts of the app I'm building are supposed to accept input from a PALM device that has, for example scanned a barcode and can send that input from the scanner to the AIR app on the client computer. I do not have any idea on how the client/server relationship works since I have not gotten to that part yet. The functionality I am trying to implement is on the client side at the moment so server-side functionality can be ignored for now. I guess the core of my question is how is a PALM conduit coded for desktop applications. I'll try to be as descriptive as I can but be warned, I have only been coding in Flex for the past two weeks since I have picked it up after my boss and I fell in love with the idea of an AIR application that is as much web as desktop. If you are still confused, don't hesitate to tell me, the more clarity the better. --- In [email protected] <mailto:flexcoders%40yahoogroups.com> , "Tracy Spratt" <[EMAIL PROTECTED]> wrote: > > Welcome! > > > > Since it is your first post here, we'll forgive you ;), but hereafter, > please make your subject descriptive of your question, and indicate if > it is about AIR (if you think that may be significant). The traffic on > this list prevents us from reading all posts, so many of us use the > subject to decide whethere we can be of any use. > > > > Now, your question is pretty general. I am not sure I understand the > architecture you are thinking about. Are you expecting the AIR app to > run on the PDAs? That might (I do not do AIR yet) be an issue in > itself. Can you describe the architecture of the legacy app? What > happens on the server (not Flex), what on the client(Flex) and how the > communication between client ans server is handled? > > > > Tracy > > > > ________________________________ > > From: [email protected] <mailto:flexcoders%40yahoogroups.com> [mailto:[email protected] <mailto:flexcoders%40yahoogroups.com> ] On > Behalf Of bredwards358 > Sent: Monday, April 21, 2008 10:41 AM > To: [email protected] <mailto:flexcoders%40yahoogroups.com> > Subject: [flexcoders] Hello, and a question... > > > > Hi, I'm new to this group so I would like to get my introductions out > of the way before I ask my question. I've recently begun a project at > work which involves an Adobe AIR application coded in Flex 3. It is > essentially a totally new version of legacy software which was coded > in VB 6. I am quickly getting to the point where I need to begin > coding the logic for the program which will be mostly done in > Actionscript. > > The legacy software included functionality for sending and receiving > information from PALM PDA's. I've never dealt with these devices > before and while I can look at the VB 6 modules to see how it was done > there, I really have no idea where to begin on how to figure out how > that works or where to begin on implementing similar functionality in > my own project. > > What I'm asking essentially is a point in the right direction of > something that can help me write in functionality for PALM handhelds > for the application. I appreciate and thank you for your assistance in > advance. > > -Brian >
