Return-Path: 
 <dev-return-54791-apmail-cordova-dev-archive=cordova.apache.org@cordova.apache.org>
X-Original-To: apmail-cordova-dev-archive@www.apache.org
Delivered-To: apmail-cordova-dev-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 99C5317E5F
	for <apmail-cordova-dev-archive@www.apache.org>;
 Fri, 29 Jan 2016 18:41:14 +0000 (UTC)
Received: (qmail 35093 invoked by uid 500); 29 Jan 2016 18:41:11 -0000
Delivered-To: apmail-cordova-dev-archive@cordova.apache.org
Received: (qmail 35053 invoked by uid 500); 29 Jan 2016 18:41:11 -0000
Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@cordova.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@cordova.apache.org>
List-Post: <mailto:dev@cordova.apache.org>
List-Id: <dev.cordova.apache.org>
Reply-To: dev@cordova.apache.org
Delivered-To: mailing list dev@cordova.apache.org
Received: (qmail 35037 invoked by uid 99); 29 Jan 2016 18:41:11 -0000
Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org)
 (140.211.11.23)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 29 Jan 2016 18:41:11 +0000
Received: by git1-us-west.apache.org (ASF Mail Server at
 git1-us-west.apache.org, from userid 33)
	id A21DADFFF4; Fri, 29 Jan 2016 18:41:10 +0000 (UTC)
From: rakatyal <git@git.apache.org>
To: dev@cordova.apache.org
Reply-To: dev@cordova.apache.org
References: <git-pr-463-cordova-docs@git.apache.org>
In-Reply-To: <git-pr-463-cordova-docs@git.apache.org>
Subject: [GitHub] cordova-docs pull request: CB-10389: Turning config.xml
 documentat...
Content-Type: text/plain
Message-Id: <20160129184110.A21DADFFF4@git1-us-west.apache.org>
Date: Fri, 29 Jan 2016 18:41:10 +0000 (UTC)

Github user rakatyal commented on a diff in the pull request:

    https://github.com/apache/cordova-docs/pull/463#discussion_r51297739
  
    --- Diff: www/docs/en/dev/config_ref/index.md ---
    @@ -45,207 +45,356 @@ passively copied into various `platforms/` subdirectories, for example:
             app/platforms/blackberry10/www/config.xml
             app/platforms/android/res/xml/config.xml
     
    -This section details global and cross-platform configuration options.
    -See the following sections for platform-specific options:
    -
    -- [iOS Configuration](../guide/platforms/ios/config.html)
    -- [Android Configuration](../guide/platforms/android/config.html)
    -- [BlackBerry 10 Configuration](../guide/platforms/blackberry10/config.html)
    -
     In addition to the various configuration options detailed below, you
     can also configure an application's core set of images for each target
     platform. See [Icons and Splash Screens](images.html) for more information.
     
    -## Core Configuration Elements
    -
    -This example shows the default `config.xml` generated by the CLI's
    -`create` command, described in [The Command-Line Interface](../guide/cli/index.html):
    -
    -        <widget id="com.example.hello" version="0.0.1">
    -            <name>HelloWorld</name>
    -            <description>
    -                A sample Apache Cordova application that responds to the deviceready event.
    -            </description>
    -            <author email="dev@callback.apache.org" href="http://cordova.io">
    -                Apache Cordova Team
    -            </author>
    -            <content src="index.html" />
    -            <access origin="*" />
    -        </widget>
    -
    -The following configuration elements appear in the top-level
    -`config.xml` file, and are supported across all supported Cordova
    -platforms:
    -
    -- The `<widget>` element's `id` attribute provides the app's
    -  reverse-domain identifier, and the `version` its full version number
    -  expressed in major/minor/patch notation.
    -
    -  The widget tag can also have attributes that specify alternative versions,
    -  namely `versionCode` for Android, `CFBundleVersion` for iOS, and 
    -  `packageVersion` for Windows. See the Additional Versioning section below 
    -  for details.
    -
    -- The `<name>` element specifies the app's formal name, as it appears
    -  on the device's home screen and within app-store interfaces.
    -
    -- The `<description>` and `<author>` elements specify metadata and
    -  contact information that may appear within app-store listings.
    -
    -- The optional `<content>` element defines the app's starting
    -  page in the top-level web assets directory. The default value is
    -  `index.html`, which customarily appears in a project's top-level
    -  `www` directory.
    -
    -- `<access>` elements define the set of external domains the app is
    -  allowed to communicate with. The default value shown above allows
    -  it to access any server. See the Domain [Whitelist Guide](../guide/appdev/whitelist/index.html) for details.
    -
    -- The `<preference>` tag sets various options as pairs of
    -  `name`/`value` attributes. Each preference's `name` is
    -  case-insensitive.  Many preferences are unique to specific
    -  platforms, as listed at the top of this page. The following sections
    -  detail preferences that apply to more than one platform.
    -
    -### Additional Versioning
    +# widget
    --- End diff --
    
    I followed the format of <tag-name> as heading i.e. <widget> here, for plugin.xml. What do you think is better? We should be consistent.


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cordova.apache.org
For additional commands, e-mail: dev-help@cordova.apache.org