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 A75E51089B for ; Wed, 25 Sep 2013 20:59:56 +0000 (UTC) Received: (qmail 89568 invoked by uid 500); 25 Sep 2013 20:59:56 -0000 Delivered-To: apmail-cordova-dev-archive@cordova.apache.org Received: (qmail 89544 invoked by uid 500); 25 Sep 2013 20:59:55 -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 89536 invoked by uid 99); 25 Sep 2013 20:59:54 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Sep 2013 20:59:54 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of csantana23@gmail.com designates 74.125.82.46 as permitted sender) Received: from [74.125.82.46] (HELO mail-wg0-f46.google.com) (74.125.82.46) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Sep 2013 20:59:50 +0000 Received: by mail-wg0-f46.google.com with SMTP id k14so241636wgh.1 for ; Wed, 25 Sep 2013 13:59:29 -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=QHO6X8r4uhdmZWz9FrRmT2KiGnCxA3H6vcmqP+dS62Q=; b=U1HaSE45OBcc7nhZEUQwbw9aTQd4uP/g4SPr8XqFEXslVlbgivRRrpAiikrKKYgCEQ YlQfreE7w3qMOLzfbjyllKbTyB4T/CglWP869rCatchex3H+/r1DuR95Ep+iJS7kup7q k5lj9FoKYzW9NVCc43cgw3vTQffEmqew9mjd2/ThTbws9AUh+XfHC/Me7ZQpqZhNCzzG 1oRG/BNJ6IggcFZVeviC5G1qxyVgXU6n+Pbc6we9tyBa/jqf51sHoaumenqXpwYoujHU vDrYdkRmUZd8ob5M6gN2GVoU6qutsMLshzCJbFIv7uGmOxPWFhBcPoIKfs3+c12a4ss7 P0/A== MIME-Version: 1.0 X-Received: by 10.194.109.68 with SMTP id hq4mr29027942wjb.12.1380142769629; Wed, 25 Sep 2013 13:59:29 -0700 (PDT) Received: by 10.194.39.36 with HTTP; Wed, 25 Sep 2013 13:59:29 -0700 (PDT) In-Reply-To: References: Date: Wed, 25 Sep 2013 16:59:29 -0400 Message-ID: Subject: Re: config.xml discussion, we need to talk From: Carlos Santana To: "dev@cordova.apache.org" Content-Type: multipart/alternative; boundary=089e0102e6da85f0c104e73b877d X-Virus-Checked: Checked by ClamAV on apache.org --089e0102e6da85f0c104e73b877d Content-Type: text/plain; charset=ISO-8859-1 I was not trying to be purist with the w3c www/config.xml I just want to see some consistency across all platforms for configuration settings for a Cordova App. The same way I have a single index.html, app.css and app.js. I want see one config.xml for all platforms inside www/ or many config.xml per platform config.ios.xml, config.android.xml, etc... But as a web developer I'm excepting all the files that I need to modify inside www/ using CLI or not Even if I have to run something like ./bin/processconfig.sh to propagate changes from the /www/config.xml As web developer I might update the config.xml once for every 100 edits to my app web files (HTML, JS, CSS) TLDR: consistency wins over correctness PS: what is the phonegap team doing? I think you tell users to edit one config.xml for the web app and pgbuild takes care of the rest -- Carlos On Wednesday, September 25, 2013, Braden Shepherdson wrote: > I'm in favour of CLI (platform parsers, probably) deleting this > www/config.xml that they don't use. It's a waste of space and has confused > people in the past. > > It even confused the iOS prepare code and caused that odd "my project > doesn't work if it starts with x, y or z" bug (because xFactor/config.xml > sorts after www/config.xml, and it was blindly taking the first one). > > Braden > > > On Wed, Sep 25, 2013 at 4:22 PM, Bryan Higgins > >wrote: > > > Thanks for the clarification. BlackBerry happened to luck out because we > > expect config.xml in www. > > > > Perhaps copying of config.xml should become a responsibility of the > > platform parsers. > > > > I can understand moving config.xml to root or cordova for the reason > stated > > in the JIRA, but my vote would be to keep it "config.xml" rather than > > "app.xml". > > > > > > On Wed, Sep 25, 2013 at 3:55 PM, Jesse wrote: > > > > > I am not saying deviate, I am saying, what is it supposed to be? If you > > > look at the various platforms you will see it is all over the map. > > > > > > Looking at Android code, and talking to Joe, the only location that the > > > config.xml file is loaded from is in res/xml, and the fact that > > cordova-cli > > > creates another one sitting in the www folder is just irrelevant > > > sloppiness. > > > > > > It may make sense for the config.xml file to sit in the root/www folder > > of > > > the CLI project, but in reality at runtime, it's location will vary by > > > platform. > > > > > > > > > > > > @purplecabbage > > > risingj.com > > > > > > > > > On Wed, Sep 25, 2013 at 12:29 PM, Bryan Higgins < > bhiggins@blackberry.com > > > >wrote: > > > > > > > www/config.xml aligns nicely with the w3c widget spec [1]. Why would > we > > > > want to deviate? > > > > > > > > [1] http://www.w3.org/TR/widgets/#reserved-file-and-folder-names > > > > > > > > > > > > On Wed, Sep 25, 2013 at 3:23 PM, Jesse > > wrote: > > > > > > > > > Seems any project created with the CLI has a config.xml in the www > > > > folder. > > > > > [1] > > > > > Why do we have 2 of these? > > > > > > > > > > I also recently closed a defect created by Carlos, stating that WP8 > > did > > > > NOT > > > > > have it's config.xml in the www folder. [2] Now I am not sure I > > should > > > > have > > > > > called this invalid, however, after creating a new WP8 project with > > the > > > > > CLI, I see a config.xml in the www folder AND one in the app root. > > wtf? > > > > > > > > > > There is an open issue [3] to re-org config files, where Braden > > states > > > > "We > > > > > already have plans to move $PROJECT/www/config.xml to > > $PROJECT/app.xml, > > > > > which more or less addresses ..." Have we formalized what > exactly > > > this > > > > > is? > > > > > > > > > > Seems we still have a lot of discussion that has to happen before > we > > > can > > > > > move ahead on these items. I am currently adding config.xml > support > > to > > > > > Windows 8, and was hoping to have a nice clear path of what to do, > > but > > > it > > > > > still looks pretty muddy. [4] > > > > > > > > > > > > > > > [1] https://issues.apache.org/jira/browse/CB-4476 > > > > > [2] https://issues.apache.org/jira/browse/CB-46< > > > > > https://issues.apache.org/jira/browse/CB-4658> > > > > > 58 > > > > > [3] https://issues.apache.org/jira/browse/CB-4910 > > > > > [4] https://issues.apache.org/jira/browse/CB-4608 > > > > > > > > > > @purplecabbage > > > > > -- Carlos Santana --089e0102e6da85f0c104e73b877d--