cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Josh Soref <>
Subject Re: New project <PATH> vs. <NAME>
Date Wed, 23 Jul 2014 21:28:34 GMT
Jan Velecký wrote:
>probably many of you developers are english speaking.

You're apparently English speaking too.
You might mean that many developers speak English as a primary language,

> But most of languages have diacritics.

This is probably an overly broad generalization.
but what do you consider special about diacritics?

If I use CJK/Cyrillic/Arabic/Hebrew, do I need diacritics to satisfy
whatever you're actually concerned about?

> NAME is a human readable field
> NAME is an application name

>Look at item NAME – human readable. CLI tell us, that this is human
>field, I think diacritics is very very human readable, if people speaking
>language with diacritics are people... In fact, this option is name of
>project, but name of project cannot be diacritical, because of historical
>reasons and their impacts on present software...

Are you saying you can't provide diacritics in create today?

What problem are you having?

$ cordova create zip 'שלום'
Creating a new cordova project with name "שלום" and id "" at
location "zip"
$ grep name zip/config.xml

Is what happens when I use create on OS X.

>Another thing, don't you think, that is the best practise to use same
>project directory name as project name?


>1.) Typically, there cannot be two project of same name alike there
>be two directories of same name. Also, there are good reasons to use in
>of names only latin letters, numbers, hyphen and underscore. So, why path
>name isn't also project name?

Imagine my org is com.example.something.or.other.whatever
I could create projects "Directory" and "Calendar",

I could either have two nice directories named "directory" and "calendar",
or two incredibly painful directories named:

Having to type that when I'm doing "cd …" is painful.
Now, it might be the case that I know how to use tab completion, or
wildcards, but it might also just totally ruin my week or my experience of
using the tool.

>2.) With name attribute supporting more chars, it can be used as
>name (showed on device/emulator). So if developer develops czech
>with off course czech name and with diacritics too, he don't have to
>any files in platforms projects. Also, if he develops english-named
>application, but with some rare char to make name attractive, he don't
>to do this. And this should be name of project in config.xml in project
>root, so user (in future) can change this application name and CLI
>names of applciation name in each project instead of him.

I don't understand your proposal at all.

>This have only benefits, and for most of developers I think with no

Personally I'm -10 on changes to existing interfaces.
I have an existing SDK that I'm trying to support. I can't have people
randomly changing how basic commands work just because they think they can
make some minor improvement.

View raw message