Second thoughts, a better workaround would probably be to just use your highest resolution icons and put them in drawable. Scale them (down) at runtime. If you have a load of users running normal-mdpi screens, then you might want to put lower res icons in drawable-normal- mdpi. For those users running small-hdpi, normal-ldpi etc, tough luck!
But anyway yes, in general, this "import" approach to indirection would be useful... On Jun 23, 10:06 am, Mark Carter <[email protected]> wrote: > In this particular case, I would just use drawable-nodpi (using naming > like icon1_72px.png, icon1_48px.png) and then handle it all manually. > > On Jun 23, 9:47 am, Al Sutton <[email protected]> wrote: > > > > > First off; I know the implementation of this should be discussed on > > the framework list, but I'm putting this idea out on here to see if > > there is a need for it. > > > I've recently worked on a project where the designer wanted a 2 x 3 > > grid of icons as the apps "home" page. This threw up an interesting > > situation because to do this using the best resolution possible it > > seems we would either need to copy the actual icons into multiple > > directories, or create a resource alias file for each icon, neither of > > which is ideal (think 30+ icons across the app which needed > > duplicating). > > > What I'm wondering is if there is a need for a single file which > > contains all of the resources to use within another resource > > directory. To give you an idea of the problem I'll scale it down to 3 > > icons which have mdpi and hdpi variants; > > > drawables/icon1.png > > drawables/icon2.png > > drawables/icon3.png > > drawables-hdpi/icon1.png > > drawables-hdpi/icon2.png > > drawables-hdpi/icon3.png > > > As the Dell Streak is a WVGA device that identifies itself as a large- > > mdpi device we wanted to use the -hdpi icons for it, but this would > > result in three new files containing resource aliases; > > > drawables-large-mdpi/icon1.xml > > drawables-large-mdpi/icon2.xml > > drawables-large-mdpi/icon3.xml > > > What I'm wondering is should this be a single file which contains a > > list of all the imports. For example; > > > drawables-large-mdpi/imports.xml > > > which contains; > > > <imports> > > <import source="drawables-hdpi">icon1.png</import> > > <import source="drawables-hdpi">icon2.png</import> > > <import source="drawables-hdpi">icon3.png</import> > > < /imports> > > > This does away with the file-per-resource requirements of the current > > configuration and it allows resources for multiple other directories > > to be included because the source could refer to any other resource > > directory. > > > So, do people think this would be of use, or have I missed something > > which makes this whole idea obsolete? > > > Al. > > > -- > > * Looking for Android Apps? - Tryhttp://andappstore.com/* > > ====== > > Funky Android Limited is registered in England & Wales with the > > company number 6741909. > > The views expressed in this email are those of the author and not > > necessarily those of Funky Android Limited, it's associates, or it's > > subsidiaries. -- 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
