cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Axel Nennker <ignisvul...@gmail.com>
Subject Re: Started Implementing CB-2606 Add support for <icon in config.xml
Date Sat, 21 Dec 2013 23:13:28 GMT
Now with firefoxos support which lacked support for the mandatory icons
field in the manifest before this patch.
https://github.com/AxelNennker/cordova-cli/blob/master/src/metadata/firefoxos_parser.js#L63

-Axel


2013/12/20 Axel Nennker <ignisvulpis@gmail.com>

> The xmlns is in the config.xml of the 3.3 HelloWorld app.
>
> <widget id="com.example.hello" version="0.0.1" xmlns="
> http://www.w3.org/ns/widgets" xmlns:cdv="http://cordova.apache.org/ns/1.0
> ">
>
> -Axel
>
>
> Am 20.12.2013 18:08 schrieb "Josh Soref" <jsoref@blackberry.com>:
>
>  Andrew wrote:
>> > Should CLI be in the business of resizing icons or converting image
>> formats?
>>
>> Probably not
>>
>> > Should you have to supply an icon for each platform separately, or
>> should
>> > we support one <icon> tag that will be used as the default for
>> all platforms?
>>
>> Different platforms may have different icon styles.
>>
>> > Specifying the platform should not be the norm. It should be enough
>> > to have a bunch if <icon src=foo density=bar>, and platforms will pick
>> up
>> > the sizes of icons that they require.
>>
>> > I realize this is "proper" XML, since they aren't a part of the widget
>>
>> Proper involves an xmlns which I didn't see.
>> ---------------------------------------------------------------------
>> This transmission (including any attachments) may contain confidential
>> information, privileged material (including material protected by the
>> solicitor-client or other applicable privileges), or constitute non-public
>> information. Any use of this information by anyone other than the intended
>> recipient is prohibited. If you have received this transmission in error,
>> please immediately reply to the sender and delete this information from
>> your system. Use, dissemination, distribution, or reproduction of this
>> transmission by unintended recipients is not authorized and may be unlawful.
>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message