On Mon, Sep 5, 2011 at 11:47 AM, Greg Deward <[email protected]> wrote: > Anyone?
Please bear in mind that Sunday is part of the weekend, and today is a holiday in the US. So, the fact that you did not receive a response in 18 hours is not unexpected. >> How would you recommend creating a common authentication / login >> module for my use in multiple applications? This is a rather broad question. Perhaps you might consider breaking the problem down into pieces and asking about some of those. >> The product that I want to create is actually a suite of >> applications... smaller apps that work together as a whole. There are >> several components (Views, sequences, services, etc.) that I see being >> needed for all of the applications. For example, the opening sequence >> and the login / enrollment views. I'm looking for some guidance on >> how to create those reusable views / modules. Similarly, IMHO, that can't be answered in the abstract. If you are really asking: "how do I reuse code, including resources", then the answer is "use an Android library project". -- Mark Murphy (a Commons Guy) http://commonsware.com | http://github.com/commonsguy http://commonsware.com/blog | http://twitter.com/commonsguy Android Training in Oslo: http://bit.ly/fjBo24 -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] 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
