Mrkvozrout commented on issue #1464:
URL: https://github.com/apache/cordova-ios/issues/1464#issuecomment-2326596901

   Hi, I am currently also searching for a possibility to define (or just have) 
a simple technical project name instead of using app name. 
   
   Using app name as technical identifier is really not ideal because its 
purpose is to be human readable display name for the target audience (with all 
those spaces and special characters).
   
   In my use case it gets even worse because we have we have one app codebase 
for several different app variants where each variant needs to have different 
name (and package name and bundle ID and other identifiers). We use 
`before_prepare` hook to update these values in `config.xml` which works ok, 
but then e.g. the xcode project name is also always changing for each of the 
variant which makes working with it not ideal.
   
   My current workaround (I am working on now) is to have simple stable 
`<name>` value as a project name and having several other hooks and 
`edit-config`s in order to update the real app name in all native platforms. A 
bit tedious and not ideal.
   
   My solution proposal would be either of these:
   
   1. add `<project-name>` element into `config.xml`
       - its value would allow to define stable simple project name used as 
technical identifier where needed (e.g. xcode project)
       - if not defined, the value would be taken from current `<name>` 
element's value
   2. add another attribute to `<name>` element
       - e.g. `<name short="Short App Name" long="Long Name of My 
App">my-app-project-name</name>`
       - the `short` attribute currently exists and is used as human readable 
app name in short contexts
       - similarly add new `long` (or `app`) attribute to be used as human 
readable app name in common contexts
       - if not defined, the value would be taken from current `<name>` 
element's value
   
   I favour option 2) more because all naming would be defined in single 
element and it just extends current ability to define `short` name.
   
   Also the advantages of both options are:
   - backward compatibility - if new element/attribute is not defined, the 
behaviour is the same like current/older cordova build logic
   - having the ability to define custom simple project name (e.g. to better 
differentiate projects in IDE)
   
   What do you guys think? @dpogue @erisu 


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@cordova.apache.org
For additional commands, e-mail: issues-h...@cordova.apache.org

Reply via email to