cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carlos Santana <csantan...@gmail.com>
Subject Re: New project <PATH> vs. <NAME>
Date Fri, 25 Jul 2014 19:57:45 GMT
Jan sorry, I think I made a mistake on #3, I think overall what you
suggested, is what we both agree an app name and project name, can be
configure and specify.

But I want to look how we do the refactoring of the project for xcode,
right now is not very reliable, we can leave it there how it is today, and
just recommend that user don't change the project name in config.xml just
the app name



On Fri, Jul 25, 2014 at 3:52 PM, Carlos Santana <csantana23@gmail.com>
wrote:

> Let's see if I understood your feedback Jan:
>
> 1. Do you agree that it is a good idea to treat them as two independent
> things, the App name and the Project Name?
> 2. Do you agree that user should be able to to run "cordova create" and
> provide AppName and ProjectName? (i.e. cordova create --id com.example.foo
> --cordovaPath Folder --appName FooApp --projectName FooProject, ignore the
> specifics in the arguments but just having the flexibility to specify more
> granular things)
> 3. Do you agree that should not be required to provide all the parameters,
> that we can pick default values (cordova create FolderCordova, will set
> name=FolderCordova, project=CordovaApp id=io.cordovahellocordova)
> 4. Do you agree that if user wants to change the name only the name of the
> App without changing the Project Files it should be able to do it by
> changing a string in config.xml and running "cordova build"?
>
> All this things is what I agree.
>
> 1. What I'm proposing is that we start splitting in two to indepent things
> 2. That we stay away of refactoring/modifying specifically for Xcode
> project and related files after creation (I'm ok if other platforms want to
> supported)
>
> I'm OK if we just start by agreeing and doing #1 above.
>
>
> On Fri, Jul 25, 2014 at 3:37 PM, Jan Velecký <VVelda@seznam.cz> wrote:
>
>> So, then we will have dozen CordovaApp projects with different application
>> name? Not, that is not good. There is project name (for Android) in
>> .project
>> and build.xml files, and this names must be safe (As far as I know), but
>> CordovaApp? Noo... For this reason we simply need two names.
>>
>> And the most quality solution is two names in config.xml – application
>> name
>> and project name. It can be done for backward compability:
>> <name for="proj">CordovaApp</name>
>> <name for="app">Cordova App</name>
>> And then add parameter to create script and change it to <proj-name>[<app-
>> name> ].
>> Simply app-name and proj-name make same if app-name omitted.
>>
>> Sorry, e-mail provider ate tags, hope now it will be sended correct.
>>
>>
>> ---------- Původní zpráva ----------
>> Od: Carlos Santana <csantana23@gmail.com>
>> Komu: dev@cordova.apache.org <dev@cordova.apache.org>
>> Datum: 25. 7. 2014 15:12:09
>> Předmět: Re: New project <PATH> vs. <NAME>
>>
>> "I can speak for iOS.
>>
>> The way it works today from [1] [2].
>>
>> The App Name on the Home Screen (i.e. Product name Foo) and the XCode
>> Project Name (i.e. Foo.pbxproj, Foo-Info.plist, Foo-Prefix.pch) Foo are
>> too
>> tight couple and causing problems.
>>
>> I think we should split this in to separate concerns, and name in cordova
>> create or config.xml ONLY change the Product Name and NOT try to refactor
>> the Xcode project files which is the part that is causing problems.
>>
>> I think 80% of time people just want to change/set the App Name, and would
>> be fine if the Xcode project name and files don't change and have a
>> deafult
>> value of "CordovaApp" Xcode project that creates an App with name "Foo"
>>
>> Let me know what you think is this is a design you don't disagree, and I
>> can create a JIRA enhancement item.
>>
>> [1] https://github.com/apache/cordova-ios/blob/master/bin/create#L105
>> [2]
>> https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/cordova/
>> metadata/ios_parser.js#L157
>> <https://github.com/apache/cordova-lib/blob/master/cordova-lib/src/cordova/metadata/ios_parser.js#L157>
>> [3]
>> https://github.com/alunny/node-xcode/blob/master/lib/pbxProject.js#L453
>>
>>
>>
>> On Thu, Jul 24, 2014 at 10:55 AM, Michal Mocny <mmocny@chromium.org>
>> wrote:
>>
>> > Chuck, thanks for finding the right JIRA issue already. I agree that one
>> > should be addressed, and thats probably enough to address this report.
>> >
>> > Thanks Jan for bringing more attention to it! (and if you would like to
>> > provided PR for fixing i.e. the documentation, please link to them from
>> > here so they don't go unnoticed).
>> >
>> > -Michal
>> >
>> >
>> > On Wed, Jul 23, 2014 at 9:05 PM, Chuck Lantz <clantz@microsoft.com>
>> wrote:
>> >
>> > > The problem does seem to tie to platform implementations.
>> > >
>> > > On the Visual Studio side, we have been seeing issues with both
>> Android
>> > > and iOS failing to compile if the name of the app (<name></name>
in
>> > > config.xml not the project) contains unicode characters. The reason
>> this
>> > is
>> > > special is it shows up on device home pages. For iOS this appeared to
>> > > present because the app name is used for the underlying native project
>> > > name. For Android, it looks like it's tied to a class name that is
>> > > generated. Another issue appears to stem from the fact that some of
>> the
>> > > build processes are using shell scripts which can mangle international
>> > > characters if your system isn't setup with the right system locale -
>> > which
>> > > is what is driving CB-7129. However, even updating to the correct
>> system
>> > > locale doesn't fix Android or iOS.
>> > >
>> > > We've seen a surprising amount of international interest, so not being
>> > > able to use a language appropriate app name seems like a pretty big
>> deal
>> > > particularly given there's base globalization plugin designed the help
>> > with
>> > > these scenarios. Chinese is a big one that comes to mind.
>> > >
>> > > Here's the iOS bug in question:
>> > > https://issues.apache.org/jira/browse/CB-6992
>> > >
>> > > -Chuck
>> > >
>> > > -----Original Message-----
>> > > From: Josh Soref [mailto:jsoref@blackberry.com]
>> > > Sent: Wednesday, July 23, 2014 4:31 PM
>> > > To: dev@cordova.apache.org
>> > > Subject: Re: New project <PATH> vs. <NAME>
>> > >
>> > > Jan Velecký wrote:
>> > > >On Windows with Android, it "works". But make zkouka class and class
>> > > >file, so it's confusing. I prefer project name separatedly...
>> > > >PS: From this (weird) žůžováÁpčina name makes ovpina, how cool...
:-)
>> > >
>> > > >on Mac (zkouška is test in czech), then add ios platform ends with
>> > error.
>> > > >It's because diacritics cannot be in project name. When I after that
>> > > >change <name> to zkouska, adding ios platform finish successfully.
>> > > >Don't confuse project name and application name.
>> > >
>> > > On BlackBerry10 (cordova-blackberry), it just works <period>
>> > >
>> > > I get a nice running application with שלום in the list of running
>> apps,
>> > > and in the launcher.
>> > >
>> > > This to me seems more like a bug w/ cordova-ios and cordova-android
>> than
>> > a
>> > > thing that should be changed in how cordova-cli works.
>> > >
>> > > Of note, I did have one person who asked why we didn't name our .bar
>> > > (application packages) based on the app name. This is probably one of
>> the
>> > > benefits we get from not doing that...
>> > >
>> > >
>> >
>>
>>
>>
>> --
>> Carlos Santana
>> <csantana23@gmail.com>"
>>
>
>
>
> --
> Carlos Santana
> <csantana23@gmail.com>
>



-- 
Carlos Santana
<csantana23@gmail.com>

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