You could change the package in the Manifest to a package name you own
("com.yoursite.yourapp"), and rename the corresponding packages used
in the source.Classes that are public and supported are documented here: http://developer.android.com/reference/packages.html Peli www.openintents.org On Jul 15, 9:16 pm, dmodroid <[email protected]> wrote: > I know this topic has been covered a lot, so apologies if this is > redundant. I would like to work in the SDK and simply extend a core > app that already exists, and then override some functionality. For > example, I would like to extend Contacts, but then overwrite the > entire ContactsListActivity class, for my own experimental > MyContacts.apk. > > In this youtube video:http://www.youtube.com/watch?v=3aUjukCdPyQ > > Dianne talks about the ringtone picker, did she just extend the core > ringtone picker and work in the SDK? > > I DO have the entire platform source code, and have made some changes > to core apps there, but rebuilding takes awhile (even useing mmm, and > snod), so I was hoping to speed up development by working in the SDK > (where building and running the emulator seems to go faster). Not > sure if this is realistic or not. > > This is all just for some internal experimentation, I am not looking > to contribute the the core apps. > > In another post, someone had referred to ".... classes available in > the SDK....". How can we see what classes we have access to, in the > SDK. > > thanks! --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
