You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by "Joe Bowser (JIRA)" <ji...@apache.org> on 2012/07/24 00:45:33 UTC
[jira] [Created] (CB-1108) Migrate config.xml to the W3C spec
Joe Bowser created CB-1108:
------------------------------
Summary: Migrate config.xml to the W3C spec
Key: CB-1108
URL: https://issues.apache.org/jira/browse/CB-1108
Project: Apache Cordova
Issue Type: Bug
Components: Android
Affects Versions: 2.0.0
Reporter: Joe Bowser
Assignee: Joe Bowser
Fix For: 2.1.0
In 2.0.0, we decided that config.xml should exist in some form. Unfortunately, that form has nothing to do with the W3C version. We should try to move towards the W3C version wherever possible. Android was the only one to actually have a config.xml added, mostly because creating this file was trivial.
If this is not technically possible, the xml file should be changed back to cordova.xml.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-1108) Migrate config.xml to the W3C spec
Posted by "Joe Bowser (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13477153#comment-13477153 ]
Joe Bowser commented on CB-1108:
--------------------------------
Bumping, since I don't think this will get done in time for 2.2.0
> Migrate config.xml to the W3C spec
> ----------------------------------
>
> Key: CB-1108
> URL: https://issues.apache.org/jira/browse/CB-1108
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, Bada, BlackBerry, iOS, webOS, WP7
> Affects Versions: 2.0.0
> Reporter: Joe Bowser
> Assignee: Joe Bowser
> Fix For: 2.3.0
>
>
> In 2.0.0, we decided that config.xml should exist in some form. Unfortunately, that form has nothing to do with the W3C version. We should try to move towards the W3C version wherever possible. Android was the only one to actually have a config.xml added, mostly because creating this file was trivial.
> If this is not technically possible, the xml file should be changed back to cordova.xml.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-1108) Migrate config.xml to the W3C spec
Posted by "Shazron Abdullah (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Shazron Abdullah updated CB-1108:
---------------------------------
Fix Version/s: (was: 2.3.0)
2.4.0
Don't think this will make 2.3.0, punting
> Migrate config.xml to the W3C spec
> ----------------------------------
>
> Key: CB-1108
> URL: https://issues.apache.org/jira/browse/CB-1108
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, Bada, BlackBerry, iOS, webOS, WP7
> Affects Versions: 2.0.0
> Reporter: Joe Bowser
> Assignee: Joe Bowser
> Fix For: 2.4.0
>
>
> In 2.0.0, we decided that config.xml should exist in some form. Unfortunately, that form has nothing to do with the W3C version. We should try to move towards the W3C version wherever possible. Android was the only one to actually have a config.xml added, mostly because creating this file was trivial.
> If this is not technically possible, the xml file should be changed back to cordova.xml.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (CB-1108) Migrate config.xml to the W3C
spec
Posted by "Filip Maj (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13421015#comment-13421015 ]
Filip Maj edited comment on CB-1108 at 7/23/12 11:07 PM:
---------------------------------------------------------
The only difference should be {{<plugin>}} should be mapped to {{<feature>}} as [per the spec|http://www.w3.org/TR/widgets/#the-feature-element-and-its-attributes]. The {{name}} attribute for {{<feature>}} should be the platform-agnostic service label for plugins. Unfortunately there is no additional parameter defined in the spec that we can use in the {{<feature>}} element immediately to provide the native side class mapping, however, [the <param> element|http://www.w3.org/TR/widgets/#the-param-element-and-its-attributes] as defined in the spec can be used as a child element of {{<feature>}}.
The feature stuff should probably be looped back on the mailing list so all platforms can follow suit.
{{<preference>}} already exists in the spec so we're fine on that front.
was (Author: filmaj):
The only difference should be {{<plugin>} should be mapped to {{<feature>}} as [per the spec|http://www.w3.org/TR/widgets/#the-feature-element-and-its-attributes]. The {{name}} attribute for {{<feature>}} should be the platform-agnostic service label for plugins. Unfortunately there is no additional parameter defined in the spec that we can use in the {{<feature>}} element immediately to provide the native side class mapping, however, [the <param> element|http://www.w3.org/TR/widgets/#the-param-element-and-its-attributes] as defined in the spec can be used as a child element of {{<feature>}}.
The feature stuff should probably be looped back on the mailing list so all platforms can follow suit.
{{<preference>}} already exists in the spec so we're fine on that front.
> Migrate config.xml to the W3C spec
> ----------------------------------
>
> Key: CB-1108
> URL: https://issues.apache.org/jira/browse/CB-1108
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
> Affects Versions: 2.0.0
> Reporter: Joe Bowser
> Assignee: Joe Bowser
> Fix For: 2.1.0
>
>
> In 2.0.0, we decided that config.xml should exist in some form. Unfortunately, that form has nothing to do with the W3C version. We should try to move towards the W3C version wherever possible. Android was the only one to actually have a config.xml added, mostly because creating this file was trivial.
> If this is not technically possible, the xml file should be changed back to cordova.xml.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (CB-1108) Migrate config.xml to the W3C
spec
Posted by "Joe Bowser (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13456061#comment-13456061 ]
Joe Bowser edited comment on CB-1108 at 9/15/12 6:37 AM:
---------------------------------------------------------
This has sub-tasks that have already been completed. We are currently using the old format for config.xml but could use a new one where plugins are features as described in the ticket. See CB-1108.
was (Author: bowserj):
This has sub-tasks that have already been completed. We are currently using the old format for config.xml but could use a new one where plugins are features as described in the ticket.
> Migrate config.xml to the W3C spec
> ----------------------------------
>
> Key: CB-1108
> URL: https://issues.apache.org/jira/browse/CB-1108
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, Bada, BlackBerry, iOS, webOS, WP7
> Affects Versions: 2.0.0
> Reporter: Joe Bowser
> Assignee: Joe Bowser
> Fix For: 2.2.0
>
>
> In 2.0.0, we decided that config.xml should exist in some form. Unfortunately, that form has nothing to do with the W3C version. We should try to move towards the W3C version wherever possible. Android was the only one to actually have a config.xml added, mostly because creating this file was trivial.
> If this is not technically possible, the xml file should be changed back to cordova.xml.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-1108) Migrate config.xml to the W3C spec
Posted by "Shazron Abdullah (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13426484#comment-13426484 ]
Shazron Abdullah commented on CB-1108:
--------------------------------------
Is this Android only? Just wondering since the components tagged are all platforms. iOS has CB-888 already.
> Migrate config.xml to the W3C spec
> ----------------------------------
>
> Key: CB-1108
> URL: https://issues.apache.org/jira/browse/CB-1108
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, Bada, BlackBerry, iOS, webOS, WP7
> Affects Versions: 2.0.0
> Reporter: Joe Bowser
> Assignee: Joe Bowser
> Fix For: 2.1.0
>
>
> In 2.0.0, we decided that config.xml should exist in some form. Unfortunately, that form has nothing to do with the W3C version. We should try to move towards the W3C version wherever possible. Android was the only one to actually have a config.xml added, mostly because creating this file was trivial.
> If this is not technically possible, the xml file should be changed back to cordova.xml.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-1108) Migrate config.xml to the W3C spec
Posted by "Joe Bowser (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13426897#comment-13426897 ]
Joe Bowser commented on CB-1108:
--------------------------------
CB-888 was our old habit of going for existence of a config.xml without caring what it has in it
> Migrate config.xml to the W3C spec
> ----------------------------------
>
> Key: CB-1108
> URL: https://issues.apache.org/jira/browse/CB-1108
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, Bada, BlackBerry, iOS, webOS, WP7
> Affects Versions: 2.0.0
> Reporter: Joe Bowser
> Assignee: Joe Bowser
> Fix For: 2.1.0
>
>
> In 2.0.0, we decided that config.xml should exist in some form. Unfortunately, that form has nothing to do with the W3C version. We should try to move towards the W3C version wherever possible. Android was the only one to actually have a config.xml added, mostly because creating this file was trivial.
> If this is not technically possible, the xml file should be changed back to cordova.xml.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-1108) Migrate config.xml to the W3C spec
Posted by "Shazron Abdullah (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13491080#comment-13491080 ]
Shazron Abdullah commented on CB-1108:
--------------------------------------
Not sure for iOS if we support config.xml we have to "deprecate" use of Cordova.plist (which means supporting both for a while) or it's a clean break.
> Migrate config.xml to the W3C spec
> ----------------------------------
>
> Key: CB-1108
> URL: https://issues.apache.org/jira/browse/CB-1108
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, Bada, BlackBerry, iOS, webOS, WP7
> Affects Versions: 2.0.0
> Reporter: Joe Bowser
> Assignee: Joe Bowser
> Fix For: 2.3.0
>
>
> In 2.0.0, we decided that config.xml should exist in some form. Unfortunately, that form has nothing to do with the W3C version. We should try to move towards the W3C version wherever possible. Android was the only one to actually have a config.xml added, mostly because creating this file was trivial.
> If this is not technically possible, the xml file should be changed back to cordova.xml.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-1108) Migrate config.xml to the W3C spec
Posted by "Joe Bowser (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13421022#comment-13421022 ]
Joe Bowser commented on CB-1108:
--------------------------------
Actually, we don't conform to the current spec, we use this old spec that we invented along the way. To conform, we have to change certain widgets. I'm going to add them as sub-tasks. I don't expect this to get done in 2.1, but we should look at starting the migration in this release.
> Migrate config.xml to the W3C spec
> ----------------------------------
>
> Key: CB-1108
> URL: https://issues.apache.org/jira/browse/CB-1108
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
> Affects Versions: 2.0.0
> Reporter: Joe Bowser
> Assignee: Joe Bowser
> Fix For: 2.1.0
>
>
> In 2.0.0, we decided that config.xml should exist in some form. Unfortunately, that form has nothing to do with the W3C version. We should try to move towards the W3C version wherever possible. Android was the only one to actually have a config.xml added, mostly because creating this file was trivial.
> If this is not technically possible, the xml file should be changed back to cordova.xml.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-1108) Migrate config.xml to the W3C spec
Posted by "Filip Maj (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13421015#comment-13421015 ]
Filip Maj commented on CB-1108:
-------------------------------
The only difference should be {{<plugin>} should be mapped to {{<feature>}} as [per the spec|http://www.w3.org/TR/widgets/#the-feature-element-and-its-attributes]. The {{name}} attribute for {{<feature>}} should be the platform-agnostic service label for plugins. Unfortunately there is no additional parameter defined in the spec that we can use in the {{<feature>}} element immediately to provide the native side class mapping, however, [the <param> element|http://www.w3.org/TR/widgets/#the-param-element-and-its-attributes] as defined in the spec can be used as a child element of {{<feature>}}.
The feature stuff should probably be looped back on the mailing list so all platforms can follow suit.
{{<preference>}} already exists in the spec so we're fine on that front.
> Migrate config.xml to the W3C spec
> ----------------------------------
>
> Key: CB-1108
> URL: https://issues.apache.org/jira/browse/CB-1108
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android
> Affects Versions: 2.0.0
> Reporter: Joe Bowser
> Assignee: Joe Bowser
> Fix For: 2.1.0
>
>
> In 2.0.0, we decided that config.xml should exist in some form. Unfortunately, that form has nothing to do with the W3C version. We should try to move towards the W3C version wherever possible. Android was the only one to actually have a config.xml added, mostly because creating this file was trivial.
> If this is not technically possible, the xml file should be changed back to cordova.xml.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-1108) Migrate config.xml to the W3C spec
Posted by "Joe Bowser (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Bowser updated CB-1108:
---------------------------
Fix Version/s: (was: 2.2.0)
2.3.0
> Migrate config.xml to the W3C spec
> ----------------------------------
>
> Key: CB-1108
> URL: https://issues.apache.org/jira/browse/CB-1108
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, Bada, BlackBerry, iOS, webOS, WP7
> Affects Versions: 2.0.0
> Reporter: Joe Bowser
> Assignee: Joe Bowser
> Fix For: 2.3.0
>
>
> In 2.0.0, we decided that config.xml should exist in some form. Unfortunately, that form has nothing to do with the W3C version. We should try to move towards the W3C version wherever possible. Android was the only one to actually have a config.xml added, mostly because creating this file was trivial.
> If this is not technically possible, the xml file should be changed back to cordova.xml.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (CB-1108) Migrate config.xml to the W3C spec
Posted by "Joe Bowser (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Joe Bowser updated CB-1108:
---------------------------
Component/s: WP7
webOS
iOS
BlackBerry
Bada
> Migrate config.xml to the W3C spec
> ----------------------------------
>
> Key: CB-1108
> URL: https://issues.apache.org/jira/browse/CB-1108
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, Bada, BlackBerry, iOS, webOS, WP7
> Affects Versions: 2.0.0
> Reporter: Joe Bowser
> Assignee: Joe Bowser
> Fix For: 2.1.0
>
>
> In 2.0.0, we decided that config.xml should exist in some form. Unfortunately, that form has nothing to do with the W3C version. We should try to move towards the W3C version wherever possible. Android was the only one to actually have a config.xml added, mostly because creating this file was trivial.
> If this is not technically possible, the xml file should be changed back to cordova.xml.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-1108) Migrate config.xml to the W3C spec
Posted by "Braden Shepherdson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13456058#comment-13456058 ]
Braden Shepherdson commented on CB-1108:
----------------------------------------
I'm looking at this for Android.
> Migrate config.xml to the W3C spec
> ----------------------------------
>
> Key: CB-1108
> URL: https://issues.apache.org/jira/browse/CB-1108
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, Bada, BlackBerry, iOS, webOS, WP7
> Affects Versions: 2.0.0
> Reporter: Joe Bowser
> Assignee: Joe Bowser
> Fix For: 2.2.0
>
>
> In 2.0.0, we decided that config.xml should exist in some form. Unfortunately, that form has nothing to do with the W3C version. We should try to move towards the W3C version wherever possible. Android was the only one to actually have a config.xml added, mostly because creating this file was trivial.
> If this is not technically possible, the xml file should be changed back to cordova.xml.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-1108) Migrate config.xml to the W3C spec
Posted by "Joe Bowser (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13456061#comment-13456061 ]
Joe Bowser commented on CB-1108:
--------------------------------
This has sub-tasks that have already been completed. We are currently using the old format for config.xml but could use a new one where plugins are features as described in the ticket.
> Migrate config.xml to the W3C spec
> ----------------------------------
>
> Key: CB-1108
> URL: https://issues.apache.org/jira/browse/CB-1108
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, Bada, BlackBerry, iOS, webOS, WP7
> Affects Versions: 2.0.0
> Reporter: Joe Bowser
> Assignee: Joe Bowser
> Fix For: 2.2.0
>
>
> In 2.0.0, we decided that config.xml should exist in some form. Unfortunately, that form has nothing to do with the W3C version. We should try to move towards the W3C version wherever possible. Android was the only one to actually have a config.xml added, mostly because creating this file was trivial.
> If this is not technically possible, the xml file should be changed back to cordova.xml.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-1108) Migrate config.xml to the W3C spec
Posted by "Michael Brooks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13426704#comment-13426704 ]
Michael Brooks commented on CB-1108:
------------------------------------
By the looks of it, this issue is an umbrella for all platforms to migrate to {{config.xml}}, with sub-tasks for the specific steps involved in the migration.
CB-888 is similar, but hasn't concluded on what {{config.xml}} elements should be implemented.
Both issues are setup strange. After deciding what tasks need to be done, we should have created sub-tasks to track each platform's progress. Instead, we have a single task for every platform to work within (and no way to show that it is complete).
I can organize these tasks, if you'd like. However, I wouldn't get around to it for the next few hours.
> Migrate config.xml to the W3C spec
> ----------------------------------
>
> Key: CB-1108
> URL: https://issues.apache.org/jira/browse/CB-1108
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, Bada, BlackBerry, iOS, webOS, WP7
> Affects Versions: 2.0.0
> Reporter: Joe Bowser
> Assignee: Joe Bowser
> Fix For: 2.1.0
>
>
> In 2.0.0, we decided that config.xml should exist in some form. Unfortunately, that form has nothing to do with the W3C version. We should try to move towards the W3C version wherever possible. Android was the only one to actually have a config.xml added, mostly because creating this file was trivial.
> If this is not technically possible, the xml file should be changed back to cordova.xml.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (CB-1108) Migrate config.xml to the W3C
spec
Posted by "Joe Bowser (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13456061#comment-13456061 ]
Joe Bowser edited comment on CB-1108 at 9/15/12 6:38 AM:
---------------------------------------------------------
This has sub-tasks that have already been completed. We are currently using the old format for config.xml but could use a new one where plugins are features as described in the ticket. See CB-1109.
was (Author: bowserj):
This has sub-tasks that have already been completed. We are currently using the old format for config.xml but could use a new one where plugins are features as described in the ticket. See CB-1108.
> Migrate config.xml to the W3C spec
> ----------------------------------
>
> Key: CB-1108
> URL: https://issues.apache.org/jira/browse/CB-1108
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, Bada, BlackBerry, iOS, webOS, WP7
> Affects Versions: 2.0.0
> Reporter: Joe Bowser
> Assignee: Joe Bowser
> Fix For: 2.2.0
>
>
> In 2.0.0, we decided that config.xml should exist in some form. Unfortunately, that form has nothing to do with the W3C version. We should try to move towards the W3C version wherever possible. Android was the only one to actually have a config.xml added, mostly because creating this file was trivial.
> If this is not technically possible, the xml file should be changed back to cordova.xml.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (CB-1108) Migrate config.xml to the W3C spec
Posted by "Shazron Abdullah (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CB-1108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13489161#comment-13489161 ]
Shazron Abdullah commented on CB-1108:
--------------------------------------
This still needs to be broken up into sub-tasks for each platform.
> Migrate config.xml to the W3C spec
> ----------------------------------
>
> Key: CB-1108
> URL: https://issues.apache.org/jira/browse/CB-1108
> Project: Apache Cordova
> Issue Type: Bug
> Components: Android, Bada, BlackBerry, iOS, webOS, WP7
> Affects Versions: 2.0.0
> Reporter: Joe Bowser
> Assignee: Joe Bowser
> Fix For: 2.3.0
>
>
> In 2.0.0, we decided that config.xml should exist in some form. Unfortunately, that form has nothing to do with the W3C version. We should try to move towards the W3C version wherever possible. Android was the only one to actually have a config.xml added, mostly because creating this file was trivial.
> If this is not technically possible, the xml file should be changed back to cordova.xml.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira