Just opened [1] for restoring the plugins. There is also a PR attached to
the Jira. I would appreciate if someone could take a look. I also have
minor changes to plugman that will follow.
If you would like a sneak preview of the feature
https://www.youtube.com/watch?v=bc60WAQdOjE
[1]
Hi,
I would like to propose a couple of enhancements to the top level
config.xml that would enable us to recreate a project easily.
(Note: the examples below assumes a cdv namespace on config.xml)
1. engines tag :
cdv:engine id=org.apache.cordova.android version=3.5.1 /
cdv:engine
I had the same idea and I really love it
but why not platform instead of engine ?
On Wed, Apr 9, 2014 at 5:58 PM, Gorkem Ercan gorkem.er...@gmail.com wrote:
Hi,
I would like to propose a couple of enhancements to the top level
config.xml that would enable us to recreate a project easily.
I guess it could be platform as well. I put engine because that is what
plugin.xml uses for its dependencies.
--
Gorkem
On Wed, Apr 9, 2014 at 10:01 AM, Sebastien Blanc scm.bl...@gmail.comwrote:
I had the same idea and I really love it
but why not platform instead of engine ?
On Wed, Apr
This would be a great contribution.
We should consider using the dependency tag for plugins, which I think
maps well to existing specifications for urls and versions.
For platforms, I'm fine with engine, though I don't like tieing to
specific versions by default. I think we should support it,
(we should also support --searchpath for cordova create)
On Wed, Apr 9, 2014 at 2:45 PM, Michal Mocny mmo...@chromium.org wrote:
This would be a great contribution.
We should consider using the dependency tag for plugins, which I think
maps well to existing specifications for urls and
Agreed, I was thinking about making the version attribute optional which
would basically signal CLI to create platforms with the latestgreatest
platforms releases.
--
Gorkem
On Wed, Apr 9, 2014 at 12:45 PM, Michal Mocny mmo...@chromium.org wrote:
This would be a great contribution.
We should
Sounds like the ouput of this how it works should go in cordova-docs. If it's
not clear to us, then it won't be clear to users. ;-)
On Jan 13, 2014, at 9:36 PM, Andrew Grieve agri...@chromium.org wrote:
On Mon, Jan 13, 2014 at 6:14 PM, Gorkem Ercan gorkem.er...@gmail.com wrote:
On Mon, Jan
Howdy,
I think there are too many default engines defined.
for instance
engine name=cordova-android version==1.8.0 /
is essentially the same as
engine name=cordova version==1.8.0 platform=android /
Could someone remind the reason for having platform specific default
engine names? If
JBoss Tools have recently added the capability to switch between
Cordova engines. See [1] for details. While implementing checks for
plug-in compatibility I found the engine definitions on the plug-in
specification to
be more complex than needed to be.
I think there are too many default engines
FYI to others - the docs for this is found here (seems to have some
incorrectly formatted markdown too :( ) :
http://cordova.apache.org/docs/en/3.3.0/plugin_ref_spec.md.html#Plugin%20Specification
My understanding was that:
engine name=cordova-android version==1.8.0 /
is the same as:
engine
On Mon, Jan 13, 2014 at 04:32:20PM -0500, Andrew Grieve wrote:
FYI to others - the docs for this is found here (seems to have some
incorrectly formatted markdown too :( ) :
http://cordova.apache.org/docs/en/3.3.0/plugin_ref_spec.md.html#Plugin%20Specification
My understanding was that:
12 matches
Mail list logo
