Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (athena.apache.org: domain of csantana23@gmail.com
 designates 209.85.212.179 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CA+GVa3YmRtYTLeak7nPb==FPRyBzOHWPO6_GaQYnxndSgP799g@mail.gmail.com>
References: <20140729223207.6357079.13749.6173@blackberry.com>
	<CAHYtTqmttVeECgPLk-vELd=NiL2BvY9hC-E16+u8Mi1+2X81NA@mail.gmail.com>
	<CAEeF2TcVnqLQj+k47GV1cDEpXpJ9MoivauVxOf7f8n_5ARpFSQ@mail.gmail.com>
	<CAHYtTq=Qxb8aUeFfQXF4RogWaF5v-_UQ1uw0mvMPHXMFbSxdxw@mail.gmail.com>
	<CA+GVa3YBOXdXg8nSC0neNCsobgBbw=MEE_fmxruo90j6XKFbxw@mail.gmail.com>
	<CAHYtTqk4dxXzrVyztVxYO34FnBuGLbs-H+pc+tzALTmzMomH-Q@mail.gmail.com>
	<CA+GVa3bLYLfar14PcO+DV-m-ZJ=u6-wMo1Q-qLSNsGDNwwoA=Q@mail.gmail.com>
	<CAHYtTqkqd+Tq3o0femqVCJ4HuoM7Cn_MJ4ZzbLFQjfC21as7hA@mail.gmail.com>
	<CAEeF2TfycpV7tjVD9V0OQ5_f+RZO7dDwTosM3h5tc0Owi30Q4w@mail.gmail.com>
	<CAHYtTqnMznT_-mQJKXA2y4tzMOsk+RiC_xeEY=DpsDy72Xkcfw@mail.gmail.com>
	<CAHYtTq=c-r6T6zzhxJN5fg78F=By_Swyjo9GiEMqtWEr_7KULw@mail.gmail.com>
	<CA+GVa3bZpaRNkkqD9LCMD7TRO-n0JT-4GQo8ci_i5FTE2YUOGA@mail.gmail.com>
	<CAHYtTq=byvBGrfhF2zcre-ymZo9KMkodv71_5dPW0ns0FCPZnQ@mail.gmail.com>
	<CA+GVa3YmRtYTLeak7nPb==FPRyBzOHWPO6_GaQYnxndSgP799g@mail.gmail.com>
Date: Wed, 30 Jul 2014 18:03:54 -0400
Message-ID: 
 <CAHYtTqkd++tRnnt4GDGSu-zJTjh=q-o=U7RggQySHzLQFo6nmg@mail.gmail.com>
Subject: Re: missing documentation and missing major version bump
From: Carlos Santana <csantana23@gmail.com>
To: "dev@cordova.apache.org" <dev@cordova.apache.org>
Content-Type: multipart/alternative; boundary=f46d044403a2fe89ba04ff705455

--f46d044403a2fe89ba04ff705455
Content-Type: text/plain; charset=UTF-8

Yes I agree the projectname should be saved in config.xml
and have it as an official flag in documented cordova cli

I think the concern was more of using current default name
HelloCordova.pbxproj this will always be the name of the project, unless
you really, really know what you are doing and want to change it you can
specify in cli, shell script, or in config.xml <name
project="changetothis">appname</name>
My guess is to not brake someone that is relying on that behavior today and
understand the limitations on file and directory names


On Wed, Jul 30, 2014 at 5:48 PM, Mark Koudritsky <kamrik@google.com> wrote:

> On Wed, Jul 30, 2014 at 12:50 PM, Carlos Santana <csantana23@gmail.com>
> wrote:
>
> > For the prepare I was thinking hooks.
> >
> > Does all hooks receive all the command line arguments including the extra
> > ones?
> >
> Yes, it receives the entire command line string, like this
> execOpts.env.CORDOVA_CMDLINE = process.argv.join(' ');
> from cordova/hooker.js:143
> <
> https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/cordova/hooker.js#L143
> >
>
>
>
> > The use case is related to CB-7131 [1], to be use like "platform add ios
> > --project="CordovaProject"
> > Where the Cordova App name is different from the xcode project name.
> >
> > [1]:https://issues.apache.org/jira/browse/CB-7231
>
>
> If we decide to add the flexibility to separately set the project name, I
> think we will have to have "--project" (or whatever we decide to call that
> flag) be part of cordova cli core flags. That name is better be saved
> somewhere like www/config.xml, so it's definitely not an ephemeral flag to
> be passed along to the platform scripts and forgotten.
>
> And going back to that discussion about project name(s). From going over it
> I didn't understand what is wrong with always using CordovaApp.pbxproj.  Is
> that "CordovaApp" visible somewhere on the final device where the app is
> installed?
>


-- 
Carlos Santana
<csantana23@gmail.com>

--f46d044403a2fe89ba04ff705455--