That is the point, basically. As it now stands, I have a chat application with unusual IO, and since deploying this as I now have it would require me to host a server, I want to first parcel off the I/O into a service and allow other application developers to employ it in their own apps. So I see that I'd want to go from my Activity now (a chat with whimsical I/O) into, initially
1. a Service offering those I/O methods 2. a small Activity permitting the preferences for those I/O routines to be viewed and adjusted, and a few other fun things and later, perhaps, 3. my chat Activity refactored to use the underlying functionality in a remote Service, and not integrally as it does now. However, I don't want to have redundant code trees. I see Mark Murphy has given me an answer, but it falls outside my experience space with XML-- a syntax form I handle as little as possible. I will try to tinker a bit. I think it may be sufficient for me to work on creating #2 with #1 being a local service, and set aside my code for the chat for the time being. tone On Oct 2, 12:05 am, mammen <[EMAIL PROTECTED]> wrote: > What is the purpose of this? Is it multiple applications? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to android-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en -~----------~----~----~----~------~----~------~--~---
