I have a related question, is it possible to add folders to a plugin as if
I seletected Create folder references for any added folders option? (blue
folder)
with resource-file src=path/to/file / I get the resource as if I
selected the Create groups for any added folder option (yellow folder)
awesome, great to have you here Sebastian: don't hesitate to start a
thread, open an issue, and dive in on improvements
always lots to do around here!
On Wed, Jul 30, 2014 at 7:37 PM, Carlos Santana csantan...@gmail.com
wrote:
Welcome Sebastian
checkout this link
Ah the docs. Many threads have appeared and receded into the ether about
our Docs. (Searching the ML archives might be interesting but in no way
required.)
So even the very generation and publishing of Cordova docs could use a
love. And somehow this might be related to generating/publishing docs
Use asset element your folder will be included inside as blue folder
inside the www bluefolder inside your Mobile App
You can do a file or folder
For example a folder named workligh:
!-- a directory, also to be copied in the root directory --
asset src=www/worklight target=worklight /
On
Github user bryanhiggins closed the pull request at:
https://github.com/apache/cordova-plugin-globalization/pull/18
---
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
I'm into it! BlackBerry now supports File plugin roots and Globalization :)
On Tue, Jul 29, 2014 at 3:29 PM, Steven Gill stevengil...@gmail.com wrote:
How do you all feel about a plugins release?
I can aim to start a vote thread tomorrow or Thursday if people feel good
about it.
-Steve
This is now done.
I only documented run initially because I didn't really want to think
through the code (prepare is an interesting odd case) and I knew it
applied to run.
On 7/30/14, 11:45 AM, Carlos Santana csantan...@gmail.com wrote:
If it's applicable to more than build command, then it
GitHub user stacic opened a pull request:
https://github.com/apache/cordova-plugin-device-motion/pull/16
CB-7160 port tests for accelerometer
-Added manual tests on top of existing automated tests
-Removed changes to plugin.xml
-Added nested plugin.xml
-Changed 'test'
Github user stacic closed the pull request at:
https://github.com/apache/cordova-plugin-device-motion/pull/14
---
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
Thanks for updating the help, Josh.
On Thu, Jul 31, 2014 at 11:16 AM, Josh Soref jso...@blackberry.com wrote:
This is now done.
I only documented run initially because I didn't really want to think
through the code (prepare is an interesting odd case) and I knew it
applied to run.
On
GitHub user stacic opened a pull request:
https://github.com/apache/cordova-mobile-spec/pull/81
CB-7160 Removed accelerometer tests
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/stacic/cordova-mobile-spec CB-7160
Github user stacic commented on the pull request:
https://github.com/apache/cordova-mobile-spec/pull/81#issuecomment-50784364
The tests ported in this PR should be used instead:
https://github.com/apache/cordova-plugin-device-motion/pull/16
---
If your project is set up for it, you
Github user stacic commented on the pull request:
https://github.com/apache/cordova-plugin-device-motion/pull/16#issuecomment-50784416
Tests are removed from mobile-spec in this PR:
https://github.com/apache/cordova-mobile-spec/pull/81
---
If your project is set up for it, you can
GitHub user stacic opened a pull request:
https://github.com/apache/cordova-mobile-spec/pull/82
CB-6958 Removed camera tests
Tests from this PR should be used instead:
https://github.com/apache/cordova-plugin-camera/pull/38
You can merge this pull request into a Git repository by
Github user stacic commented on the pull request:
https://github.com/apache/cordova-plugin-camera/pull/38#issuecomment-50786472
Tests are removed from mobile-spec in this PR:
https://github.com/apache/cordova-mobile-spec/pull/82
---
If your project is set up for it, you can reply
Github user kamrik commented on a diff in the pull request:
https://github.com/apache/cordova-lib/pull/55#discussion_r15655705
--- Diff: cordova-lib/src/hooks/scriptsFinder.js ---
@@ -0,0 +1,164 @@
+/**
+ Licensed to the Apache Software Foundation (ASF) under one
+ or
Hi all,
CLI on master, contains some changes that are breaking --link-to
argument, throwing a error during usage.
--link-to is highly used by createmobilespec module to link the custom
resources in there, so by extension is breaking the workflow on that module
as well.
I've switched to
Github user sgrebnov commented on a diff in the pull request:
https://github.com/apache/cordova-lib/pull/55#discussion_r15658798
--- Diff: cordova-lib/src/hooks/scriptsFinder.js ---
@@ -0,0 +1,164 @@
+/**
+ Licensed to the Apache Software Foundation (ASF) under one
+ or
Hello,
We work on cordova app for a client and he requires that each externals sources
must be tagued. We used the 0.2.9 but we had the issue CB-6907
Yes, you are right, linking it with the latest cordova-lib in master works
pretty fine. I think that the master branch should be working stable and
working just typing npm install, it just seems like an extra burden, get
to clone cordova-lib, then install it, then link it to the CLI node modules.
Hmm, indeed 0.2.10 was released but not tagged 0.2.10 in the plugin's
Apaches git repo.
On Thu, Jul 31, 2014 at 5:51 AM, BOURGE, Guillaume
guillaume.bou...@capgemini.com wrote:
Hello,
We work on cordova app for a client and he requires that each externals
sources must be tagued. We used the
I'll tag this 0.2.10:
https://git-wip-us.apache.org/repos/asf?p=cordova-plugin-network-information.git;a=commit;h=07ff22accc1e0a22dbf97153a516ebef886aae41
Which corresponds to the sha from the Vote thread for 0.2.10:
cordova-plugin-network-information: 0.2.10 (07ff22accc)
On Thu, Jul 31, 2014 at
GitHub user stacic opened a pull request:
https://github.com/apache/cordova-mobile-spec/pull/83
CB-6959 Removed capture tests
Tests should be replaced with this ported ones in this PR:
https://github.com/apache/cordova-plugin-media-capture/pull/22
You can merge this pull request
Github user stacic commented on the pull request:
https://github.com/apache/cordova-plugin-media-capture/pull/22#issuecomment-50808014
Tests removed from mobile-spec here:
https://github.com/apache/cordova-mobile-spec/pull/83
---
If your project is set up for it, you can reply to
This looks good to me. Anyone else want to test it before I merge it in?
On Wed, Jul 30, 2014 at 3:38 PM, Suraj Pindoria
suraj.pindo...@yahoo.com.invalid wrote:
So I updated this to include some of the additional use cases discussed
earlier. Now, running cordova prepare --browserify in an
GitHub user martincgg opened a pull request:
https://github.com/apache/cordova-mobile-spec/pull/84
CB-7242 Added wp8 subdirectory to localPlatforms variable
createmobilespec --wp8 fails, because the path for wp8 on localPlatforms
is incomplete, it requires the wp8 subdirectory
So Globalization has issues with missing headers and needs a update to the
notice file for new licenses. Both Blackberry and FFOS need to go do this
before I release that plugin!
What am I doing with test-harness? That isn't being released right? It also
needs headers included + notice file
GitHub user kamrik opened a pull request:
https://github.com/apache/cordova-lib/pull/69
Add JSCS config file
Don't merge yet - feedback wanted.
JSHint people want to focus on syntax linting and are dropping style
oriented
options. They recommend using JSCS (in addition
Just opened a pull request with an experimental JSCS config. Would be glad
to get some feedback about this. My goal is to eventually run JSCS together
with JSHint as part of `npm test`. This is a relatively liberal config that
doesn't generate too many warnings with the existing code.
29 matches
Mail list logo
