Config.xml should contain app metadata only, not default dev device to
deploy to..

On 6/4/13 2:37 PM, "Lorin Beer" <[email protected]> wrote:

>the json file currently contains
>
>1. string to name bar file
>2. path to find bb10 plugins
>3. default target
>4. all targets currently created
>
>list of registered targets would mean we could make finding and
>registering devices on the onus of the user, making several CLI
>scripts trivial rather than impossible (vm related scripts for
>instance).
>
>As Bryan suggests, project name gets moved to config.xml, along with
>maybe default target?
>
>On Tue, Jun 4, 2013 at 2:31 PM, Ken Wallis <[email protected]> wrote:
>> +1 here as well.
>>
>> what else is in the JSON file, and what scripts are related to that
>>additional information if any?
>> --
>>
>> Ken Wallis
>>
>> Product Manager ­ WebWorks
>>
>> BlackBerry
>>
>> 289-261-4369
>>
>> ________________________________________
>> From: Bryan Higgins [[email protected]]
>> Sent: Tuesday, June 04, 2013 2:30 PM
>> To: [email protected]
>> Subject: Re: Alias of BB create tools
>>
>> +1
>>
>> I'd like to see the entire JSON file moved out of the project. It's
>>meant
>> to be for environment specific settings.
>>
>> barName should get moved into config.xml
>>
>>
>> On Tue, Jun 4, 2013 at 5:24 PM, Filip Maj <[email protected]> wrote:
>>
>>> Fil likes.
>>>
>>> On 6/4/13 2:21 PM, "Lorin Beer" <[email protected]> wrote:
>>>
>>> >Something I've wanted to do for a while with the BB repos:
>>> >
>>> >alias the target add script which is currently a project level script
>>> >into the root /bin
>>> >the purpose of this would be to allow users to create device targets
>>> >from the repo, which would then be propagated to individual projects.
>>> >
>>> >This has two advantages I can see:
>>> >
>>> >1. you no longer have to re-create targets or copy the .json file over
>>> >when creating new BB10 projects
>>> >
>>> >2. by making target create a repo level script, we can fully support
>>> >more of the CLI scripts
>>> >
>>> >What does BB think?
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> This transmission (including any attachments) may contain confidential
>>information, privileged material (including material protected by the
>>solicitor-client or other applicable privileges), or constitute
>>non-public information. Any use of this information by anyone other than
>>the intended recipient is prohibited. If you have received this
>>transmission in error, please immediately reply to the sender and delete
>>this information from your system. Use, dissemination, distribution, or
>>reproduction of this transmission by unintended recipients is not
>>authorized and may be unlawful.

Reply via email to