Another best-practices note! How about the drawables that are part of the API like android.R.drawable? For instance isn't it desirable for the user experience to use common icons such as R.drawable.ic_delete and R.drawable.ic_menu_add, etc.? Is it best practice to copy these into your application? Is there an issue with this if your application is not open source?
(Sorry to add this new subject to his thread) On Jan 11, 10:24 am, Mark Murphy <[email protected]> wrote: > jotobjects wrote: > > Looking at your sample you include the drawer handle png drawable that > > looks a lot like the one in the home page. Is there a built-in drawer > > handle on the platform or does every app have to create their own? > > The core Android team generally does not recommend you attempt to rely > on built-in drawables. This would be a fine example, as I would expect > the drawable used by the Home screen's sliding drawer to be missing in > Android 2.1, since the sliding drawer is not used by the Home screen > anymore, at least not for applications. > > Whether you copy an image out of the AOSP or find your own, you should > supply your own drawable. > > -- > Mark Murphy (a Commons > Guy)http://commonsware.com|http://twitter.com/commonsguy > > _Android Programming Tutorials_ Version 1.1 Available!
-- 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
