You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cordova.apache.org by Carlos Santana <cs...@gmail.com> on 2013/09/20 19:54:16 UTC
bbwp vs. blackberry-nativepackager?
I see that cordova 3.x uses blackberry-nativepackager instead of bbwp
Any known problems with using bbwp?
Is bbwp not supported as a method to package a Cordova App?
When using bbwp on an App created with Cordova 3 it errors on validation
config.xml
<feature> tag missing attribute "id"
<feature name="Camera" value="Camera" />
adding "id" makes validation pass
<feature id="Camera" name="Camera" value="Camera" />
Shouldn't according to BB docs feature only contain "id" and nothign else?
like this
<feature id="Camera" />
http://developer.blackberry.com/html5/documentation/feature_element_834678_11.html
Syntax
<feature id="string"
required=["true" | "false"]
version="string" />
--
Carlos Santana
<cs...@gmail.com>
Re: bbwp vs. blackberry-nativepackager?
Posted by Carlos Santana <cs...@gmail.com>.
Oh This is great all features for BB10 are Cordova plugins. This is great !
:-)
This helps my team articulate better that they proper way to
enhance/customize a Cordova App is just implementing a plugin and follow
the API
--Carlos
On Fri, Sep 20, 2013 at 3:19 PM, Bryan Higgins <br...@bryanhiggins.net>wrote:
> Correct
>
>
> https://github.com/blackberry/cordova-blackberry-plugins/blob/master/plugin/com.blackberry.app/plugin.xml#L29
>
>
> On Fri, Sep 20, 2013 at 3:17 PM, Carlos Santana <csantana23@gmail.com
> >wrote:
>
> > Next version of SDK config.xml will have different schema using "name"
> and
> > "value" for <feature> ?
> >
> >
> >
> >
> > On Fri, Sep 20, 2013 at 2:45 PM, Bryan Higgins <bryan@bryanhiggins.net
> > >wrote:
> >
> > > The roadmap for WebWorks SDK is to use Apache Cordova as its base.
> > >
> > > We have modified those files to comply with cordova spec, utilizing
> name
> > > rather than id.
> > >
> > > As a cordova developer, you only need the native tools on your path.
> > These
> > > can come from either the WebWorks SDK or the Native SDK.
> > >
> > >
> > > On Fri, Sep 20, 2013 at 2:26 PM, Carlos Santana <csantana23@gmail.com
> > > >wrote:
> > >
> > > > Thanks Bryan
> > > >
> > > > I think I understand now most of the node js script in cordova are
> also
> > > > present in webworks sdk
> > > >
> > > > 1. I think cordova should create a valid config.xml to be use by
> > > > blackberry10 platform.
> > > > 2. We should use updated code to validate that config.xml is a valid
> > file
> > > > even with user additions
> > > > 3. Since we required the sdk anyway why have an old copy of the same
> > > files
> > > > in cordova and not leverage the ones present in sdk?
> > > >
> > > > config-parser.js in cordova is different in than webworks
> > > config.parser.js
> > > >
> > > > function createAccessListObj(uri, allowSubDomain) {
> > > > return {
> > > > uri: uri,
> > > > allowSubDomain: allowSubDomain
> > > > };
> > > > }
> > > >
> > > > vs in webworks
> > > > function createAccessListObj(featuresArray, uri, allowSubDomain) {
> > > > return {
> > > > features: featuresArray,
> > > > uri: uri,
> > > > allowSubDomain: allowSubDomain
> > > > };
> > > > }
> > > >
> > > > resulting in different validations in function
> > > > config-parser.js: function validateConfig(widgetConfig)
> > > > if (access.features) {
> > > > // Assert each feature has a proper ID and is not
> empty
> > > > access.features.forEach(function (feature) {
> > > > if (!feature) {
> > > > throw
> > > > localize.translate("EXCEPTION_INVALID_FEATURE_ID");
> > > > }
> > > > check(feature.id,
> > > >
> > localize.translate("EXCEPTION_INVALID_FEATURE_ID")).notNull().notEmpty();
> > > > });
> > > > }
> > > >
> > > > Should I filed a bug to add <feature "id" ..> to all cordova plugins
> > and
> > > > update config-parser.js in cordova?
> > > >
> > > > --Carlos
> > > >
> > > >
> > > >
> > > > On Fri, Sep 20, 2013 at 2:08 PM, Bryan Higgins <
> bryan@bryanhiggins.net
> > > > >wrote:
> > > >
> > > > > The tools are not compatible. In fact, most of the source from bbwp
> > has
> > > > > been contributed into Cordova.
> > > > >
> > > > >
> > > > > On Fri, Sep 20, 2013 at 1:54 PM, Carlos Santana <
> > csantana23@gmail.com
> > > > > >wrote:
> > > > >
> > > > > > I see that cordova 3.x uses blackberry-nativepackager instead of
> > bbwp
> > > > > >
> > > > > > Any known problems with using bbwp?
> > > > > > Is bbwp not supported as a method to package a Cordova App?
> > > > > >
> > > > > > When using bbwp on an App created with Cordova 3 it errors on
> > > > validation
> > > > > > config.xml
> > > > > >
> > > > > > <feature> tag missing attribute "id"
> > > > > >
> > > > > > <feature name="Camera" value="Camera" />
> > > > > >
> > > > > > adding "id" makes validation pass
> > > > > >
> > > > > > <feature id="Camera" name="Camera" value="Camera" />
> > > > > >
> > > > > > Shouldn't according to BB docs feature only contain "id" and
> > nothign
> > > > > else?
> > > > > >
> > > > > > like this
> > > > > >
> > > > > > <feature id="Camera" />
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> http://developer.blackberry.com/html5/documentation/feature_element_834678_11.html
> > > > > >
> > > > > > Syntax
> > > > > > <feature id="string"
> > > > > > required=["true" | "false"]
> > > > > > version="string" />
> > > > > >
> > > > > > --
> > > > > > Carlos Santana
> > > > > > <cs...@gmail.com>
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Carlos Santana
> > > > <cs...@gmail.com>
> > > >
> > >
> >
> >
> >
> > --
> > Carlos Santana
> > <cs...@gmail.com>
> >
>
--
Carlos Santana
<cs...@gmail.com>
Re: bbwp vs. blackberry-nativepackager?
Posted by Bryan Higgins <br...@bryanhiggins.net>.
Correct
https://github.com/blackberry/cordova-blackberry-plugins/blob/master/plugin/com.blackberry.app/plugin.xml#L29
On Fri, Sep 20, 2013 at 3:17 PM, Carlos Santana <cs...@gmail.com>wrote:
> Next version of SDK config.xml will have different schema using "name" and
> "value" for <feature> ?
>
>
>
>
> On Fri, Sep 20, 2013 at 2:45 PM, Bryan Higgins <bryan@bryanhiggins.net
> >wrote:
>
> > The roadmap for WebWorks SDK is to use Apache Cordova as its base.
> >
> > We have modified those files to comply with cordova spec, utilizing name
> > rather than id.
> >
> > As a cordova developer, you only need the native tools on your path.
> These
> > can come from either the WebWorks SDK or the Native SDK.
> >
> >
> > On Fri, Sep 20, 2013 at 2:26 PM, Carlos Santana <csantana23@gmail.com
> > >wrote:
> >
> > > Thanks Bryan
> > >
> > > I think I understand now most of the node js script in cordova are also
> > > present in webworks sdk
> > >
> > > 1. I think cordova should create a valid config.xml to be use by
> > > blackberry10 platform.
> > > 2. We should use updated code to validate that config.xml is a valid
> file
> > > even with user additions
> > > 3. Since we required the sdk anyway why have an old copy of the same
> > files
> > > in cordova and not leverage the ones present in sdk?
> > >
> > > config-parser.js in cordova is different in than webworks
> > config.parser.js
> > >
> > > function createAccessListObj(uri, allowSubDomain) {
> > > return {
> > > uri: uri,
> > > allowSubDomain: allowSubDomain
> > > };
> > > }
> > >
> > > vs in webworks
> > > function createAccessListObj(featuresArray, uri, allowSubDomain) {
> > > return {
> > > features: featuresArray,
> > > uri: uri,
> > > allowSubDomain: allowSubDomain
> > > };
> > > }
> > >
> > > resulting in different validations in function
> > > config-parser.js: function validateConfig(widgetConfig)
> > > if (access.features) {
> > > // Assert each feature has a proper ID and is not empty
> > > access.features.forEach(function (feature) {
> > > if (!feature) {
> > > throw
> > > localize.translate("EXCEPTION_INVALID_FEATURE_ID");
> > > }
> > > check(feature.id,
> > >
> localize.translate("EXCEPTION_INVALID_FEATURE_ID")).notNull().notEmpty();
> > > });
> > > }
> > >
> > > Should I filed a bug to add <feature "id" ..> to all cordova plugins
> and
> > > update config-parser.js in cordova?
> > >
> > > --Carlos
> > >
> > >
> > >
> > > On Fri, Sep 20, 2013 at 2:08 PM, Bryan Higgins <bryan@bryanhiggins.net
> > > >wrote:
> > >
> > > > The tools are not compatible. In fact, most of the source from bbwp
> has
> > > > been contributed into Cordova.
> > > >
> > > >
> > > > On Fri, Sep 20, 2013 at 1:54 PM, Carlos Santana <
> csantana23@gmail.com
> > > > >wrote:
> > > >
> > > > > I see that cordova 3.x uses blackberry-nativepackager instead of
> bbwp
> > > > >
> > > > > Any known problems with using bbwp?
> > > > > Is bbwp not supported as a method to package a Cordova App?
> > > > >
> > > > > When using bbwp on an App created with Cordova 3 it errors on
> > > validation
> > > > > config.xml
> > > > >
> > > > > <feature> tag missing attribute "id"
> > > > >
> > > > > <feature name="Camera" value="Camera" />
> > > > >
> > > > > adding "id" makes validation pass
> > > > >
> > > > > <feature id="Camera" name="Camera" value="Camera" />
> > > > >
> > > > > Shouldn't according to BB docs feature only contain "id" and
> nothign
> > > > else?
> > > > >
> > > > > like this
> > > > >
> > > > > <feature id="Camera" />
> > > > >
> > > > >
> > > >
> > >
> >
> http://developer.blackberry.com/html5/documentation/feature_element_834678_11.html
> > > > >
> > > > > Syntax
> > > > > <feature id="string"
> > > > > required=["true" | "false"]
> > > > > version="string" />
> > > > >
> > > > > --
> > > > > Carlos Santana
> > > > > <cs...@gmail.com>
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Carlos Santana
> > > <cs...@gmail.com>
> > >
> >
>
>
>
> --
> Carlos Santana
> <cs...@gmail.com>
>
Re: bbwp vs. blackberry-nativepackager?
Posted by Carlos Santana <cs...@gmail.com>.
Next version of SDK config.xml will have different schema using "name" and
"value" for <feature> ?
On Fri, Sep 20, 2013 at 2:45 PM, Bryan Higgins <br...@bryanhiggins.net>wrote:
> The roadmap for WebWorks SDK is to use Apache Cordova as its base.
>
> We have modified those files to comply with cordova spec, utilizing name
> rather than id.
>
> As a cordova developer, you only need the native tools on your path. These
> can come from either the WebWorks SDK or the Native SDK.
>
>
> On Fri, Sep 20, 2013 at 2:26 PM, Carlos Santana <csantana23@gmail.com
> >wrote:
>
> > Thanks Bryan
> >
> > I think I understand now most of the node js script in cordova are also
> > present in webworks sdk
> >
> > 1. I think cordova should create a valid config.xml to be use by
> > blackberry10 platform.
> > 2. We should use updated code to validate that config.xml is a valid file
> > even with user additions
> > 3. Since we required the sdk anyway why have an old copy of the same
> files
> > in cordova and not leverage the ones present in sdk?
> >
> > config-parser.js in cordova is different in than webworks
> config.parser.js
> >
> > function createAccessListObj(uri, allowSubDomain) {
> > return {
> > uri: uri,
> > allowSubDomain: allowSubDomain
> > };
> > }
> >
> > vs in webworks
> > function createAccessListObj(featuresArray, uri, allowSubDomain) {
> > return {
> > features: featuresArray,
> > uri: uri,
> > allowSubDomain: allowSubDomain
> > };
> > }
> >
> > resulting in different validations in function
> > config-parser.js: function validateConfig(widgetConfig)
> > if (access.features) {
> > // Assert each feature has a proper ID and is not empty
> > access.features.forEach(function (feature) {
> > if (!feature) {
> > throw
> > localize.translate("EXCEPTION_INVALID_FEATURE_ID");
> > }
> > check(feature.id,
> > localize.translate("EXCEPTION_INVALID_FEATURE_ID")).notNull().notEmpty();
> > });
> > }
> >
> > Should I filed a bug to add <feature "id" ..> to all cordova plugins and
> > update config-parser.js in cordova?
> >
> > --Carlos
> >
> >
> >
> > On Fri, Sep 20, 2013 at 2:08 PM, Bryan Higgins <bryan@bryanhiggins.net
> > >wrote:
> >
> > > The tools are not compatible. In fact, most of the source from bbwp has
> > > been contributed into Cordova.
> > >
> > >
> > > On Fri, Sep 20, 2013 at 1:54 PM, Carlos Santana <csantana23@gmail.com
> > > >wrote:
> > >
> > > > I see that cordova 3.x uses blackberry-nativepackager instead of bbwp
> > > >
> > > > Any known problems with using bbwp?
> > > > Is bbwp not supported as a method to package a Cordova App?
> > > >
> > > > When using bbwp on an App created with Cordova 3 it errors on
> > validation
> > > > config.xml
> > > >
> > > > <feature> tag missing attribute "id"
> > > >
> > > > <feature name="Camera" value="Camera" />
> > > >
> > > > adding "id" makes validation pass
> > > >
> > > > <feature id="Camera" name="Camera" value="Camera" />
> > > >
> > > > Shouldn't according to BB docs feature only contain "id" and nothign
> > > else?
> > > >
> > > > like this
> > > >
> > > > <feature id="Camera" />
> > > >
> > > >
> > >
> >
> http://developer.blackberry.com/html5/documentation/feature_element_834678_11.html
> > > >
> > > > Syntax
> > > > <feature id="string"
> > > > required=["true" | "false"]
> > > > version="string" />
> > > >
> > > > --
> > > > Carlos Santana
> > > > <cs...@gmail.com>
> > > >
> > >
> >
> >
> >
> > --
> > Carlos Santana
> > <cs...@gmail.com>
> >
>
--
Carlos Santana
<cs...@gmail.com>
Re: bbwp vs. blackberry-nativepackager?
Posted by Bryan Higgins <br...@bryanhiggins.net>.
The roadmap for WebWorks SDK is to use Apache Cordova as its base.
We have modified those files to comply with cordova spec, utilizing name
rather than id.
As a cordova developer, you only need the native tools on your path. These
can come from either the WebWorks SDK or the Native SDK.
On Fri, Sep 20, 2013 at 2:26 PM, Carlos Santana <cs...@gmail.com>wrote:
> Thanks Bryan
>
> I think I understand now most of the node js script in cordova are also
> present in webworks sdk
>
> 1. I think cordova should create a valid config.xml to be use by
> blackberry10 platform.
> 2. We should use updated code to validate that config.xml is a valid file
> even with user additions
> 3. Since we required the sdk anyway why have an old copy of the same files
> in cordova and not leverage the ones present in sdk?
>
> config-parser.js in cordova is different in than webworks config.parser.js
>
> function createAccessListObj(uri, allowSubDomain) {
> return {
> uri: uri,
> allowSubDomain: allowSubDomain
> };
> }
>
> vs in webworks
> function createAccessListObj(featuresArray, uri, allowSubDomain) {
> return {
> features: featuresArray,
> uri: uri,
> allowSubDomain: allowSubDomain
> };
> }
>
> resulting in different validations in function
> config-parser.js: function validateConfig(widgetConfig)
> if (access.features) {
> // Assert each feature has a proper ID and is not empty
> access.features.forEach(function (feature) {
> if (!feature) {
> throw
> localize.translate("EXCEPTION_INVALID_FEATURE_ID");
> }
> check(feature.id,
> localize.translate("EXCEPTION_INVALID_FEATURE_ID")).notNull().notEmpty();
> });
> }
>
> Should I filed a bug to add <feature "id" ..> to all cordova plugins and
> update config-parser.js in cordova?
>
> --Carlos
>
>
>
> On Fri, Sep 20, 2013 at 2:08 PM, Bryan Higgins <bryan@bryanhiggins.net
> >wrote:
>
> > The tools are not compatible. In fact, most of the source from bbwp has
> > been contributed into Cordova.
> >
> >
> > On Fri, Sep 20, 2013 at 1:54 PM, Carlos Santana <csantana23@gmail.com
> > >wrote:
> >
> > > I see that cordova 3.x uses blackberry-nativepackager instead of bbwp
> > >
> > > Any known problems with using bbwp?
> > > Is bbwp not supported as a method to package a Cordova App?
> > >
> > > When using bbwp on an App created with Cordova 3 it errors on
> validation
> > > config.xml
> > >
> > > <feature> tag missing attribute "id"
> > >
> > > <feature name="Camera" value="Camera" />
> > >
> > > adding "id" makes validation pass
> > >
> > > <feature id="Camera" name="Camera" value="Camera" />
> > >
> > > Shouldn't according to BB docs feature only contain "id" and nothign
> > else?
> > >
> > > like this
> > >
> > > <feature id="Camera" />
> > >
> > >
> >
> http://developer.blackberry.com/html5/documentation/feature_element_834678_11.html
> > >
> > > Syntax
> > > <feature id="string"
> > > required=["true" | "false"]
> > > version="string" />
> > >
> > > --
> > > Carlos Santana
> > > <cs...@gmail.com>
> > >
> >
>
>
>
> --
> Carlos Santana
> <cs...@gmail.com>
>
Re: bbwp vs. blackberry-nativepackager?
Posted by Carlos Santana <cs...@gmail.com>.
Thanks Bryan
I think I understand now most of the node js script in cordova are also
present in webworks sdk
1. I think cordova should create a valid config.xml to be use by
blackberry10 platform.
2. We should use updated code to validate that config.xml is a valid file
even with user additions
3. Since we required the sdk anyway why have an old copy of the same files
in cordova and not leverage the ones present in sdk?
config-parser.js in cordova is different in than webworks config.parser.js
function createAccessListObj(uri, allowSubDomain) {
return {
uri: uri,
allowSubDomain: allowSubDomain
};
}
vs in webworks
function createAccessListObj(featuresArray, uri, allowSubDomain) {
return {
features: featuresArray,
uri: uri,
allowSubDomain: allowSubDomain
};
}
resulting in different validations in function
config-parser.js: function validateConfig(widgetConfig)
if (access.features) {
// Assert each feature has a proper ID and is not empty
access.features.forEach(function (feature) {
if (!feature) {
throw
localize.translate("EXCEPTION_INVALID_FEATURE_ID");
}
check(feature.id,
localize.translate("EXCEPTION_INVALID_FEATURE_ID")).notNull().notEmpty();
});
}
Should I filed a bug to add <feature "id" ..> to all cordova plugins and
update config-parser.js in cordova?
--Carlos
On Fri, Sep 20, 2013 at 2:08 PM, Bryan Higgins <br...@bryanhiggins.net>wrote:
> The tools are not compatible. In fact, most of the source from bbwp has
> been contributed into Cordova.
>
>
> On Fri, Sep 20, 2013 at 1:54 PM, Carlos Santana <csantana23@gmail.com
> >wrote:
>
> > I see that cordova 3.x uses blackberry-nativepackager instead of bbwp
> >
> > Any known problems with using bbwp?
> > Is bbwp not supported as a method to package a Cordova App?
> >
> > When using bbwp on an App created with Cordova 3 it errors on validation
> > config.xml
> >
> > <feature> tag missing attribute "id"
> >
> > <feature name="Camera" value="Camera" />
> >
> > adding "id" makes validation pass
> >
> > <feature id="Camera" name="Camera" value="Camera" />
> >
> > Shouldn't according to BB docs feature only contain "id" and nothign
> else?
> >
> > like this
> >
> > <feature id="Camera" />
> >
> >
> http://developer.blackberry.com/html5/documentation/feature_element_834678_11.html
> >
> > Syntax
> > <feature id="string"
> > required=["true" | "false"]
> > version="string" />
> >
> > --
> > Carlos Santana
> > <cs...@gmail.com>
> >
>
--
Carlos Santana
<cs...@gmail.com>
Re: bbwp vs. blackberry-nativepackager?
Posted by Bryan Higgins <br...@bryanhiggins.net>.
The tools are not compatible. In fact, most of the source from bbwp has
been contributed into Cordova.
On Fri, Sep 20, 2013 at 1:54 PM, Carlos Santana <cs...@gmail.com>wrote:
> I see that cordova 3.x uses blackberry-nativepackager instead of bbwp
>
> Any known problems with using bbwp?
> Is bbwp not supported as a method to package a Cordova App?
>
> When using bbwp on an App created with Cordova 3 it errors on validation
> config.xml
>
> <feature> tag missing attribute "id"
>
> <feature name="Camera" value="Camera" />
>
> adding "id" makes validation pass
>
> <feature id="Camera" name="Camera" value="Camera" />
>
> Shouldn't according to BB docs feature only contain "id" and nothign else?
>
> like this
>
> <feature id="Camera" />
>
> http://developer.blackberry.com/html5/documentation/feature_element_834678_11.html
>
> Syntax
> <feature id="string"
> required=["true" | "false"]
> version="string" />
>
> --
> Carlos Santana
> <cs...@gmail.com>
>