I am a school teacher, and I am starting work on an application for tracking some information about my students (whether or not they complete their homework each day). The implementation I am planning would be based on essentially three tables: Sections, Students, and HomeworkRecord. But it occurs to me that I may wish to write other applications for school in the future, and Students and Sections data is likely to be common to all of them. So my question is: Does it make sense to implement one application that implements a ContentProvider for Sections and Students, with maybe a couple of Activities to edit them, and then do a separate app for the homework stuff? If so, what is the "right" way to store a reference to a row in Students in a table implemented in another app? Is it appropriate just to use the Students._id, or should I store the entire URI (this would seem pretty wasteful in terms of bytes, but maybe there is some reason to do it).
Thanks, Jay -- 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
