On Fri, Feb 18, 2011 at 8:06 AM, Mark Carter <[email protected]> wrote:
> When you say "skip the whole content provider API" do you mean, access the > underlying database directly (through helper methods of course) or not use > the database at all? > Just don't use a database. > I'm not sure I'm going about this the right way. Essentially I pulled in > the DownloadService class and then gradually pulled in more and more > referenced classes until the thing compiled. I commented out Media-specific > & SSL code because those are not relevant to what I'm doing. I ended up with > about 30 classes which I placed in a single new package (I felt it was safer > to isolate the code rather than use original package names). I also had to > pull in a bunch of resources (strings, styles and a layout). I haven't done > anything about the native method calls, which I'm sure I will find out about > later. > > Now, I haven't tried running anything yet because I'm thinking I may be > going down an increasingly rocky and treacherous path, so was hoping for > some feedback before I get lost or twist my ankle! > That does sound like a lot of code. :} I'm not familiar enough with the download manager to know how much that sounds reasonable. I am just thinking to only use the networking pieces from it, and write your own front-end (posting notifications if that is what you want, or doing whatever UI you want). -- Dianne Hackborn Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support, and so won't reply to such e-mails. All such questions should be posted on public forums, where I and others can see and answer them. -- 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
