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 1456510E89 for ; Wed, 8 Jan 2014 19:25:43 +0000 (UTC) Received: (qmail 86239 invoked by uid 500); 8 Jan 2014 19:24:55 -0000 Delivered-To: apmail-cordova-dev-archive@cordova.apache.org Received: (qmail 86032 invoked by uid 500); 8 Jan 2014 19:24:50 -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 85868 invoked by uid 99); 8 Jan 2014 19:24:41 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Jan 2014 19:24:41 +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 agrieve@google.com designates 209.85.160.44 as permitted sender) Received: from [209.85.160.44] (HELO mail-pb0-f44.google.com) (209.85.160.44) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 08 Jan 2014 19:24:35 +0000 Received: by mail-pb0-f44.google.com with SMTP id rq2so1969991pbb.17 for ; Wed, 08 Jan 2014 11:24:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=lCMM03hFM+ti1eWu6VEGACs1zRkT1C42O8k4yHPP8Lo=; b=Jqh6XKsgNHhoJaIpse3PmbWMytFJCn5KoRnkRvB9HrkI2U60TRI+/fvFNMnbolOqqz pq8bDRJbWZloG2Vkj7n2/2H8aBYshS3iPNQZNBmXLzrvXVuLn/7rbkPUPSdhZlAMsITm uZGQBmSIpNZoFjxYZCi/LR8ZYuw6NDQJoZZTKPVCcPM3ssDunqfaXEDCaX+B1fnXFn6d ob5XanBO5d1UXx3+VMvbelYHVgsidWwgOmnn2C/9LHYJ/b42qyskaH5xsKeKt+1H3so8 EKsLsPI4JimoqzF9z9JVFo5xl2go7UXv5QqpBOnP2NN1LWf4kWTTbzVePxmAgfu4UHwF CeaQ== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=lCMM03hFM+ti1eWu6VEGACs1zRkT1C42O8k4yHPP8Lo=; b=X3WhcjqiDhBgDD2BHZ2jt3fiicZytbcIvICo+WlMvKnIz/GzM4ZO2x44Bh+6lLMjp6 U1ddAhqmk3LgT673Fa2h9/naBLpYxFE2ophHejVx8ZkH96syMvdZHwfKxklI8rqCxo00 kGzStPHl1VmrwDpXVzyBx9KZcv7Qmhe8s+n9k= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:content-type; bh=lCMM03hFM+ti1eWu6VEGACs1zRkT1C42O8k4yHPP8Lo=; b=MiPcvRznqo2FHzP0THyIAwKIrvyUL/7PaZV2DcNG8xm5iTovcDYptRwjDiU1ghZSzl 8L11hb28mcltnO7K8eN3jCJhs8ElhHSGedkWCZ+dNaGgNR2bIjRoN6wxPMyVCxEPfwZV mBhmY8vAi17g1dTygOPt2JC3s0MUC2AcXgRELZhmQyDyafxcN5tHyXT2lDw02IRGqkAD tfgXoLAw8LLKof1rIUR7IGF9A0du3q7eHlkQH5cDtNmqxA69GUAwAMG4HhIGN8sVNPkI upyH4i2zT4OXEBtbyP7V1qZcKFX4Ppe5HO2jr5HsOhs6NO0E/Bq636yy14d9fQOoZJbD dAfA== X-Gm-Message-State: ALoCoQkhKxSwVqpArTRLPjjZCjT/XLl1myXdcC1bRoa03We+kfoFW8ddPgLuGnlIIUD4fFG7MsQrKq8zwCQ4CZHowIPhZKOtqhCMixPh2llmKc4AG/ITBjcFgV1qPTu7VGkxqzGIS9pe4BWoWur1IIbbAgCrdQ79IxN3GDjexq8Ri9qmBk3KvSob7ma8WmNZDgx0wd1zs7UNtMJReUSG36rg1ENyY2+T6w== X-Received: by 10.66.241.73 with SMTP id wg9mr15194112pac.69.1389209054463; Wed, 08 Jan 2014 11:24:14 -0800 (PST) MIME-Version: 1.0 Sender: agrieve@google.com Received: by 10.68.136.35 with HTTP; Wed, 8 Jan 2014 11:23:53 -0800 (PST) In-Reply-To: References: <20131220170733.6754455.79772.8183@blackberry.com> From: Andrew Grieve Date: Wed, 8 Jan 2014 11:23:53 -0800 X-Google-Sender-Auth: JhVomQ-RPkwWLxjKLQ7CNuwOtYE Message-ID: Subject: Re: Started Implementing CB-2606 Add support for Content-Type: multipart/alternative; boundary=047d7b10cb1935f12104ef7a7012 X-Virus-Checked: Checked by ClamAV on apache.org --047d7b10cb1935f12104ef7a7012 Content-Type: text/plain; charset=UTF-8 The change has landed (minus docs on cordova-docs), but we'll have to support config.xml being in the root or in www/. What that means for file paths I'm not sure. Maybe just say regardless of where the .xml file is make paths relative to the project root? No idea about namespaces. On Wed, Jan 8, 2014 at 10:31 AM, Axel Nennker wrote: > I think I'll wait for when "www/config.xml -> config.xml" has landed before > continuing with this, right?! > Axel > > ps: > Does the xml parser handle name spaces correctly? > That is: How do I find an element in a certain namespace regardless of > prefix? > > https://github.com/AxelNennker/cordova-cli/blob/master/src/config_parser.js#L249 > Can I write something like > > els = this.config.doc.findall('icon', 'http://cordova.apache.org/ns/1.0'); > > in elementree? > > > > > > 2013/12/22 Axel Nennker > > > 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 > > > >> The xmlns is in the config.xml of the 3.3 HelloWorld app. > >> > >> > >> > >> -Axel > >> > >> > >> Am 20.12.2013 18:08 schrieb "Josh Soref" : > >> > >> 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 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 , 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. > >>> > >> > > > --047d7b10cb1935f12104ef7a7012--