Return-Path: X-Original-To: apmail-cordova-dev-archive@www.apache.org Delivered-To: apmail-cordova-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 26D1010AC4 for ; Thu, 3 Apr 2014 11:19:36 +0000 (UTC) Received: (qmail 10594 invoked by uid 500); 3 Apr 2014 11:19:35 -0000 Delivered-To: apmail-cordova-dev-archive@cordova.apache.org Received: (qmail 10230 invoked by uid 500); 3 Apr 2014 11:19:34 -0000 Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cordova.apache.org Delivered-To: mailing list dev@cordova.apache.org Received: (qmail 10216 invoked by uid 99); 3 Apr 2014 11:19:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Apr 2014 11:19:32 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of ignisvulpis@gmail.com designates 209.85.213.51 as permitted sender) Received: from [209.85.213.51] (HELO mail-yh0-f51.google.com) (209.85.213.51) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 03 Apr 2014 11:19:24 +0000 Received: by mail-yh0-f51.google.com with SMTP id f10so1489187yha.24 for ; Thu, 03 Apr 2014 04:19:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=z4DD3tt74iLcp68QKNtPf0INN6EgxXzs/x1INltSs5k=; b=ByQuh1c19vZYbw/ZncGxBIH/tpUMSilZyswFyzT/fdNbswI84x/UEfAghsJTCyDkd0 hZDxra0n39LYNbF0n602dQIoKhe/tmZ+uUvksA9WXPa6i8pLznIcFQbYUJALqcvEU6RY w1LrPw6q5iOj0U2PAOMl+JsLSoGHLzbePxl3s5r3OY16oltLzyaApz70oP8Nur9dL/Xl +oOLaAqMi2GphKpBkiG1dq2bw/ePtVKOXfGrOhi8mIoQcAy943Yz74K9YRC1cJ9UHk8g jmF7XQ+0DzIfG4/JRs6nV4nWWSeDPWpDZet1i2zGd7xQgnclx5dmZMe6VV0p8HFdDyij ICZg== MIME-Version: 1.0 X-Received: by 10.236.230.41 with SMTP id i39mr7882795yhq.14.1396523942750; Thu, 03 Apr 2014 04:19:02 -0700 (PDT) Received: by 10.170.114.71 with HTTP; Thu, 3 Apr 2014 04:19:02 -0700 (PDT) In-Reply-To: References: <4eef8ad331c84341a714c394611b1d43@BL2PR03MB417.namprd03.prod.outlook.com> <7d7248787c10470c9bc868d6bfb05e53@BL2PR03MB417.namprd03.prod.outlook.com> Date: Thu, 3 Apr 2014 13:19:02 +0200 Message-ID: Subject: Re: cordova launcher icon support https://github.com/apache/cordova-cli/pull/126 From: Axel Nennker To: dev Content-Type: multipart/alternative; boundary=089e0160d2c48733eb04f62191c7 X-Virus-Checked: Checked by ClamAV on apache.org --089e0160d2c48733eb04f62191c7 Content-Type: text/plain; charset=ISO-8859-1 merged. Thanks, Sergey! 2014-04-03 12:47 GMT+02:00 Sergey Grebnov (Akvelon) : > Hi Axel, > > +1 to finalize icons support > > Just sent a PR[1] to your branch with the following improvements. > 1. Support of 'cdv:platform' and 'gap:platform' for to be PG build > compliant > 1. iOS support > 2. FirefoxOS code updated > 3. Other minor improvements > > You can find test icons configuration here[2]. > > Regarding platform element support > 1. I believe right now is only used when main config.xml is > copied to platform config.xml. CLI ConfigParser does not take it into > account > 2. I've recently sent a fix that includes support for > 'config.getPreference' method. [2] > > [1] https://github.com/AxelNennker/cordova-cli/pull/3 > [2] https://gist.github.com/sgrebnov/9949313 > [3] https://github.com/apache/cordova-cli/pull/145/files > > Thx! > Sergey > -----Original Message----- > From: Axel Nennker [mailto:ignisvulpis@gmail.com] > Sent: Thursday, April 3, 2014 1:06 PM > To: dev > Subject: Re: cordova launcher icon support > https://github.com/apache/cordova-cli/pull/126 > > Bryan, > where is this "platform element support" implemented? > It is not in > https://github.com/apache/cordova-cli/blob/master/src/ConfigParser.js > right? > > Regarding "cdv:platform": No this is the opposite. There are other threads > in this mailing (search for CB-2606). > To summarize those: > All proposals that included new elements like "cdv:icon" or new attributes > for the icon element "cdv:platform" did not get broad support. > All proposals related to the gap prefix or namespaces did not get broad > support. > Dropping the w3c widget standard for config.xml was postponed to "later". > Hooks work but feel like a nailed on afterwards solution. > > So I came up with the proposal to select the icons be the width/height > attributes. This proposal does not cover all use case e.g.: If you want > different icons on different platforms then this will not work. but it is > simple > > The pro side: > - standard icon sizes seem to be quite distinct per platform. > - this proposal is already implemented for Android, FirefoxOS, WP8. Sergey > works on ios. > - it does not fiddle with xml stuff > - easy to implement and easy to understand by devs > > It is a shame that CB-2606 is unresolved this long. We should have > something rolled out soon. > > -axel > > > > > 2014-04-02 22:21 GMT+02:00 Bryan Higgins : > > > config.xml already supports a platform element for platform specific > > config > > > > Is the proposal to also add an attribute cdv:platform which serves the > > same purpose? > > > > > > On Wed, Apr 2, 2014 at 4:09 PM, Sergey Grebnov (Akvelon) < > > v-segreb@microsoft.com> wrote: > > > > > Hi, > > > > > > Have we agreed to proceed with explicit icons definition via > > > config.xml similar to PG Build[1]? - If so I'm going to add iOS > > > support and update our docs. So we will have support of iOS, > > > Android, FxOS, WP8 and > > Windows8. > > > Adding icons to a new platform will be easy, similar to [2] > > > > > > Some my thoughts: Adding explicit icon references to config.xml > > > looks redundant since in most cases developers will still use > > > default icon > > names > > > following platform guides so we can just proceed with predefined > > > folder ('res' as an example) and documenting folder structure and > > > icon names for different platforms. - Sort of 'merges' where we > > > replace app resources using some special logic. But it could be > > > useful if we share same image between platforms or reference the > > > same image for different needs inside single platform. > > > > > > [1] > > > > > http://docs.build.phonegap.com/en_US/3.3.0/configuring_icons_and_splas > > h.md.html#Icons%20and%20Splash%20Screens > > > [2] > > > > > https://github.com/apache/cordova-cli/pull/126/files#diff-45a2a0f22289 > > a5eb91348499a5053cd8R170 > > > > > > Thx! > > > Sergey > > > -----Original Message----- > > > From: Axel Nennker [mailto:ignisvulpis@gmail.com] > > > Sent: Thursday, March 13, 2014 5:05 PM > > > To: dev > > > Subject: RE: cordova launcher icon support > > > https://github.com/apache/cordova-cli/pull/126 > > > > > > Please fork https://github.com/AxelNennker/cordova-cli and send a PR > > > for wp. > > > Thanks > > > Axel > > > Am 13.03.2014 13:18 schrieb "Sergey Grebnov (Akvelon)" < > > > v-segreb@microsoft.com>: > > > > > > > Hi > > > > 1. It seems pull request does not contain related changes for > > > > windows8 and wp8. I may help here if nobody has already started > > > > working in this direction. > > > > 2. I also can't replace default splash screen image following > > > > instructions below. It seems to be PhoneGap Build specific, isn't it? > > > > Do we support changing splash screen as part of cordova-cli? > > > > > > > > http://cordova.apache.org/docs/en/3.4.0/config_ref_images.md.html# > > > > Icon > > > > s%20and%20Splash%20Screens > > > > > > > > Thx! > > > > Sergey > > > > -----Original Message----- > > > > From: Axel Nennker [mailto:ignisvulpis@gmail.com] > > > > Sent: Saturday, February 22, 2014 1:44 AM > > > > To: dev > > > > Subject: Re: cordova launcher icon support > > > > https://github.com/apache/cordova-cli/pull/126 > > > > > > > > there is a pull request that implements this gap: prefix and > > > > phonegap namespace stuff but this is Cordova and we have cdv: as > > > > prefix and another > > > > namespace: xmlns:cdv="http://cordova.apache.org/ns/1.0" > > > > Looks like config.json adapted by both projects is a way out. > > > > > > > > > > > > 2014-02-21 21:36 GMT+01:00 Don Coleman : > > > > > > > > > Icons are a drag. Explicit configuration sucks, but is the way to > go. > > > > > > > > > > It would be nice if the Cordova solution was compatible with > > > > > PhoneGap Build icons< > > > > > http://docs.build.phonegap.com/en_US/3.1.0/configuring_icons_and > > > > > _spl as h.md.html#Icons%20and%20Splash%20Screens > > > > > > > > > > > . > > > > > > > > > > > > > > > > > > > > > > > > > On Fri, Feb 21, 2014 at 11:24 AM, Axel Nennker > > > > > > > > > >wrote: > > > > > > > > > > > What is your favorite explicit configuration? > > > > > > Am 21.02.2014 16:49 schrieb "Brian LeRoux" : > > > > > > > > > > > > > As much as I'd like a single icon source I do not think it > > > > > > > is the right path. To do this right I think we need to audit > > > > > > > all possible icons for > > > > > > each > > > > > > > platform and create a map to analyze what could be distilled > > > > > > > across platforms. > > > > > > > > > > > > > > Ideally we'd accept a vector format (SVG) and generate all > > > > > > > these > > > > > > ridiculous > > > > > > > sizes but designers will not like this. Pixel perfection, > > > > > > > especially > > > > > for > > > > > > a > > > > > > > springboard icon, is paramount. The only way we're getting > > > > > > > there safely > > > > > > is > > > > > > > zero magic and explicit configuration. > > > > > > > > > > > > > > Lame, I know. > > > > > > > > > > > > > > > > > > > > > On Thu, Feb 20, 2014 at 1:07 AM, Axel Nennker > > > > > > > > > > > > > > wrote: > > > > > > > > > > > > > > > How about this strategy: > > > > > > > > > > > > > > > > project_dir/config.xml > > > > > > > > - no new elements in config.xml like cdv:icon > > > > > > > > - no new attributes in icon element in config.xml like > > > > > > > > cdv:platform > > > > > or > > > > > > > > gap:platform > > > > > > > > - do not invent stuff we have to support for the rest of > > > > > > > > our > > > life. > > > > > > > > > > > > > > > > On all platforms: > > > > > > > > - if config.xml contains a > > > > > > > > without any attributes like width and heigth, then copy > > > > > > > > that src to to all > > > > > platform > > > > > > > > specific locations where that platform expects launcher > > > > > > > > icons and > > > > > > update > > > > > > > > config files like manifest.webapp on FirefoxOS if there > > > > > > > > isn't a > > > > > > specific > > > > > > > > icon element for that location (see later). > > > > > > > > - no downscaling of icons to lower sizes > > > > > > > > - no upscaling of icons to higher sizes > > > > > > > > - do not add dependencies to new node modules (e.g. to > > > > > > > > parse icon > > > > > > files) > > > > > > > > > > > > > > > > On Android: > > > > > > > > I) if there is a specific > > > > > > > /> then > > > > > copy > > > > > > > > that icon.png to res/drawable-mdpi (height is ignored if > > > > > > > > width is > > > > > > > present, > > > > > > > > no check for non-sqare icons) > > > > > > > > II) Other sizes are handled according to this list from: > > > > > > > > http://developer.android.com/guide/practices/screens_suppo > > > > > > > > rt.h > > > > > > > > tm > > > > > > > > l > > > > > > > > > > > > > > > > - 36x36 for low-density > > > > > > > > - 48x48 for medium-density > > > > > > > > - 72x72 for high-density > > > > > > > > - 96x96 for extra high-density > > > > > > > > > > > > > > > > Directories not matching this algorithm that have names > > > > > > > > starting with res/drawable get the biggest icon if no > > > > > > > > default icon is available > > > > > (I). > > > > > > > > III) icons with width or height other than the ones > > > > > > > > mentioned here > > > > > are > > > > > > > > ignored. > > > > > > > > > > > > > > > > On FirefoxOS: > > > > > > > > See > > > > > https://developer.mozilla.org/en-US/Apps/Developing/Manifest#ico > > > > > ns > > > > > > > > > > > > > > > > For Firefox OS, icons should follow the app icon > > > > > > > > guidelines< > > > > > > > > https://www.mozilla.org/en-US/styleguide/products/firefox- > > > > > > > > os/i > > > > > > > > co > > > > > > > > ns/ > > > > > >, > > > > > > > > they should not have a drop shadow, and they should be in > > > > > > > > the > > > > > following > > > > > > > > sizes: > > > > > > > > 128 x 128 For display on the Firefox Marketplace 60 x 60 > > > > > > > > For the > > > > > > actual > > > > > > > > on-device icon; only the 128px icon is mandatory, but it > > > > > > > > is > > > > > recommended > > > > > > > to > > > > > > > > include this size as well for optimal device icon display > > > > > > > > https://www.mozilla.org/en-US/styleguide/products/firefox- > > > > > > > > os/i > > > > > > > > co > > > > > > > > ns/ > > > > > > > > > > > > > > > > I) ignore icon elements in config.xml without width or > > > > > > > > height > > > > > > attributes > > > > > > > > II) copy all icons mentioned in config.xml with width or > > > > > > > > height > > > > > equal > > > > > > to > > > > > > > > 60 or 128 to the app's root and create an icon section in > > > > > > manifest.webapp > > > > > > > > that matches these icons. > > > > > > > > III) if no icon is specified for width/height 60 or 128 > > > > > > > > then copy > > > > > each > > > > > > > icon > > > > > > > > mentioned in config.xml that has width or height specified. > > > > > > > > > > > > > > > > On other platforms: > > > > > > > > some strategy matching the ones for Android and FirefoxOS. > > > > > > > > If a size > > > > > is > > > > > > > > there that is typical for that platform (72,144 for ios) > > > > > > > > then us only > > > > > > > those > > > > > > > > matching icons. Try to help developers. > > > > > > > > > > > > > > > > -Axel > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 2014-02-13 9:56 GMT+01:00 Axel Nennker > > > > > > > > > >: > > > > > > > > > > > > > > > > > The topic is reaching politics status... > > > > > > > > > > > > > > > > > > I think it is worth some effort to keep phonegap and > > > > > > > > > cordova > > > > > aligned. > > > > > > > > > What is "Adobe"'s position on W3C widget and xml vs json? > > > > > > > > > > > > > > > > > > -Axel > > > > > > > > > > > > > > > > > > Regarding which PR to accept: I want support for > > > > > > > > > launcher icons > > > > > and I > > > > > > > do > > > > > > > > > not care whether my PR is accepted or the other one. > > > > > > > > > Actually I do not understand why CB-2606 is open for so > long. > > > > > > > > > https://issues.apache.org/jira/browse/CB-2606 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > 2014-02-12 23:33 GMT+01:00 Jesse >: > > > > > > > > > > > > > > > > > > Part of what you are seeing is the phonegap namespace > > > > > > > > > extensions > > > > > that > > > > > > > are > > > > > > > > >> added for build.phonegap.com and the online tools. [1] > > > > > > > > >> [2] > > > > > > > > >> > > > > > > > > >> > > > > > > > > >> [1] > > > > > > > > >> > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > http://docs.build.phonegap.com/en_US/3.1.0/configuring_basics.md > > > > > .htm > > > > > l# > > > > > The%20Basics > > > > > > > > >> [2] > > > > > > > > > > > > > https://github.com/phonegap/phonegap-start/blob/master/www/confi > > > > > g.xm > > > > > l > > > > > > > > >> > > > > > > > > >> > > > > > > > > >> @purplecabbage > > > > > > > > >> risingj.com > > > > > > > > >> > > > > > > > > >> > > > > > > > > >> On Wed, Feb 12, 2014 at 2:03 PM, Andrew Grieve < > > > > > > agrieve@chromium.org> > > > > > > > > >> wrote: > > > > > > > > >> > > > > > > > > >> > Just started a new thread to propose removing the > > namespace. > > > > > > > > >> > > > > > > > > > >> > Don't the we should use "gap:density", since that's > > > > > > > > >> > pretty > > > > > > > PhoneGap-y > > > > > > > > as > > > > > > > > >> > opposed to Cordova-y. > > > > > > > > >> > > > > > > > > > >> > How about we have "size" and "density" attributes > > > > > > > > >> > that are just > > > > > > > > >> synonyms? > > > > > > > > >> > > > > > > > > > >> > Off for the day. > > > > > > > > >> > > > > > > > > > >> > > > > > > > > > >> > > > > > > > > > >> > On Wed, Feb 12, 2014 at 4:57 PM, Axel Nennker < > > > > > > > ignisvulpis@gmail.com> > > > > > > > > >> > wrote: > > > > > > > > >> > > > > > > > > > >> > > Hm. I guess the id test is historical stuff. It is > > > > > > > > >> > > legal XML > > > > > and > > > > > > > the > > > > > > > > >> > parser > > > > > > > > >> > > ignores it. > > > > > > > > >> > > > > > > > > > > >> > > Regarding the NS prefix: cdv vs gap I am quite sure > > > > > > > > >> > > I did not invent cdv myself. > > > > > > > > >> > > > > > > > > > > >> > > Regarding the w3c widget standard: I am OK with > > > > > > > > >> > > ditching > > > it. > > > > > > > Should > > > > > > > > >> there > > > > > > > > >> > > be a poll or how do you handle such things? > > > > > > > > >> > > All app templates should remove namespaces then, > right? > > > > > > > > >> > > > > > > > > > > >> > > Isn't there another thread around namespaces > > > > > > > > >> > > breaking the wp > > > > > > > > platform? > > > > > > > > >> > > > > > > > > > > >> > > Anyway, I think we should follow the phonegap way > > > > > > > > >> > > with e.g > > > > > > > > >> gap:density > > > > > > > > >> > for > > > > > > > > >> > > now. And ditch namespaces later. > > > > > > > > >> > > > > > > > > > > >> > > Axel > > > > > > > > >> > > Am 12.02.2014 22:38 schrieb "Andrew Grieve" < > > > > > > agrieve@chromium.org > > > > > > > >: > > > > > > > > >> > > > > > > > > > > >> > > > On Tue, Feb 11, 2014 at 3:43 PM, Brian LeRoux > > > > > > > > >> > > > > > > > > > > wrote: > > > > > > > > >> > > > > > > > > > > > >> > > > > Given we are the only 'widget spec' impl in use > > > > > > > > >> > > > > today I'm > > > > > ok > > > > > > > > with > > > > > > > > >> > > > diverging > > > > > > > > >> > > > > and not adding namespace confusion. Def want > > > > > > > > >> > > > > config to be > > > > > > > > explicit > > > > > > > > >> > and > > > > > > > > >> > > > not > > > > > > > > >> > > > > have magical implicit mappings. > > > > > > > > >> > > > > > > > > > > > > >> > > > > > > > > > > > > >> > > > > On Tue, Feb 11, 2014 at 12:24 PM, Axel Nennker > > > > > > > > >> > > > > < > > > > > > > > >> > ignisvulpis@gmail.com > > > > > > > > >> > > > > >wrote: > > > > > > > > >> > > > > > > > > > > > > >> > > > > > - My implementation does not use "id". Don't > > > > > > > > >> > > > > > know what > > > > > > this > > > > > > > or > > > > > > > > >> > might > > > > > > > > >> > > > > mean. > > > > > > > > >> > > > > > > > > > > > > >> > > > Found it from your test in spec/test-config.xml > > > > > > > > >> > > > > > > > > > > > >> > > > > > > > > > > > >> > > > > > - I do not want to discuss the sense of xml > > > > > > > > >> > > > > namespaces > > > > > in > > > > > > > > this > > > > > > > > >> > issue > > > > > > > > >> > > > if > > > > > > > > >> > > > > we > > > > > > > > >> > > > > > can avoid it. The current template config.xml > > > > > > > > >> > > > > > defines > > > > > two > > > > > > > > >> > namespaces > > > > > > > > >> > > > and > > > > > > > > >> > > > > > for this issue's implementation I do not want > > > > > > > > >> > > > > > to change > > > > > > > that. > > > > > > > > >> So I > > > > > > > > >> > > > would > > > > > > > > >> > > > > > not drop the widget namespace and would not > > > > > > > > >> > > > > > support "platform"-without-prefix. > > > > > > > > >> > > > > > > > > > > > > >> > > > > > > > > > > > >> > > > Having gap:platform there makes the property seem > > > > > > > > >> > > > like an > > > > > > > > >> second-class > > > > > > > > >> > > > maybe-not-supposed-to-be-there kind of attribute > > > > > > > > >> > > > to > > me. > > > > > > > > >> > > > I'd be happy to change the default template to > > > > > > > > >> > > > not reference > > > > > > the > > > > > > > > >> widget > > > > > > > > >> > > > spec and to make cordova's the default namespace > > > > > > > > >> > > > if that > > > > > will > > > > > > > make > > > > > > > > >> your > > > > > > > > >> > > > inner XML validator rest at-ease, but I really > > > > > > > > >> > > > feel strongly > > > > > > > > against > > > > > > > > >> > > having > > > > > > > > >> > > > XML namespaces creep in. I don't think that most > > > > > > > > >> > > > devs know > > > > > > what > > > > > > > > they > > > > > > > > >> > do, > > > > > > > > >> > > > and our tools wouldn't support you changing the gap: > > > > > namespace > > > > > > > > >> prefix. > > > > > > > > >> > > > > > > > > > > > >> > > > > > > > > > > > >> > > > > > > > > > > > >> > > > > > - I would follow the phonegap example > > > > > > > > >> > > > > > > > > > > > > > >> > > > > > > > > > > > > > >> > > > > > > > > > > > > >> > > > > > > > > > > > >> > > > > > > > > > > >> > > > > > > > > > >> > > > > > > > > > > > > > > > > > > > > > > > > > > http://docs.build.phonegap.com/en_US/3.1.0/configuring_icons_and > > > > > _spl as h.md.html#Icons%20and%20Splash%20Screens > > > > > > > > >> > > > > > that defines e.g. " > > > > > > > > >> > > > > > > > > > > > > > >> > > > > > > > > > gap:platform="android" > > > > > > > > >> > > > > > gap:density="ldpi" /> > > > > > > > > >> > > > > > > > > > > > > > >> > > > > > " and I would like to don't parse the icon > > > > > > > > >> > > > > > file to infer > > > > > > > > >> > parameters. > > > > > > > > >> > > > > > Developers want need icons for their app on > > > > > > > > >> > > > > > all > > > > > platforms > > > > > > > they > > > > > > > > >> > > support. > > > > > > > > >> > > > > So > > > > > > > > >> > > > > > they will create all of them in all polished > > > > > > > > >> > > > > > sizes and > > > > > > > > >> densities. > > > > > > > > >> > > > > > My Android implementation puts icons without > > > > > > > > >> > > > > > cdv:density > > > > > > > into > > > > > > > > >> > > > > > "drawable/icon.png" regardless of width/height. > > > > > > > > >> > > > > > What behaviour would you suggest when both > > > > > > > > >> > > > > > lines are > > > > > > present > > > > > > > > in > > > > > > > > >> one > > > > > > > > >> > > > > > config.xml > > > > > > > > >> > > > > > > > > cdv:platform="android" > > > > > > /> > > > > > > > // > > > > > > > > >> > would > > > > > > > > >> > > > end > > > > > > > > >> > > > > up > > > > > > > > >> > > > > > in drawable-mdpi by your suggestion > > > > > > > >> > > > > > src="icon-mdpi.png" cdv:density="mdpi" > > > > > > > > >> cdv:platform="android" > > > > > > > > >> > > /> > > > > > > > > >> > > > // > > > > > > > > >> > > > > > would end up in drawable-mdpi too > > > > > > > > >> > > > > > > > > > > > > >> > > > > > > > > > > > >> > > > My thinking here was that density says the same > > > > > > > > >> > > > thing as > > > > > size, > > > > > > > so > > > > > > > > I > > > > > > > > >> > would > > > > > > > > >> > > > just not support density (or make size="mdpi" an > > > > > > > > >> > > > alias for > > > > > > > > >> size="48"). > > > > > > > > >> > > > > > > > > > > > >> > > > > > > > > > > > >> > > > > > > > > > > > >> > > > > > > > > > > > > > >> > > > > > I think that developers know what is the > > > > "platform-way" > > > > > > for > > > > > > > > each > > > > > > > > >> > > > > platform. > > > > > > > > >> > > > > > On Android the usual way is to specify > densities. > > > > > > > > >> > > > > > > > > > > > > > >> > > > > > - I would not use "size" because that is not > > > > > > > > >> > > > > > w3c widget > > > > > > > style. > > > > > > > > >> > > > > > > > > > > > > > >> > > > > > -- Axel > > > > > > > > >> > > > > > > > > > > > > > >> > > > > > > > > > > > > > >> > > > > > > > > > > > > > >> > > > > > 2014-02-11 20:22 GMT+01:00 Andrew Grieve < > > > > > > > > agrieve@chromium.org > > > > > > > > >> >: > > > > > > > > >> > > > > > > > > > > > > > >> > > > > > > Would love to move this along. Would like > > > > > > > > >> > > > > > > to get > > > > > buy-in > > > > > > > from > > > > > > > > >> > others > > > > > > > > >> > > > > > > first though. > > > > > > > > >> > > > > > > > > > > > > > > >> > > > > > > The proposal in this PR is to add tags like: > > > > > > > > >> > > > > > > > > > > > > > > >> > > > > > > > > > > > > > > >> > > > > > >