Here's my list of possible topics for Tomorrow Wednesday.
Feel free to add the list.
Info Sessions
[Gorkem]: Demo of JBoss IDE
[Andrew]: AppHarness URL Remapping
[Ian]: Custom URL Scheme How-To, ups downs.
[Shaz]: Tails of ios-deploy
Work Items
[Joe]: Cordova as a sub-project on
I wanted to work on testing. Specifically, moving tests out of mobile-spec
and into plugins, converted to jasmine 2, and moving the CordovaTests app I
started to cordova-labs and go from there. Lets see how many work items
there are tomorrow, this looks like a great list.
-Michal
On Mon, Oct
The cordova-medic project has been updated to use the npm version of
ios-deploy.
Also, separate tests for CLI and plugman have been added.
On Mon, Oct 28, 2013 at 10:20 AM, David Kemp drk...@google.com wrote:
When I run this tool like:
ios-deploy --id --bundle xxx --debug
it works,
Specifically I am thinking of a test that passes on one platform/device
but will not pass on another one.
so maybe 'take them out' was poor language.
If at all possible, the test should be coded in some way to skip it or
change the expectation for that platform/device, rather than 'just knowing'
I would also like to work on testing. In addition to mobile-spec, there are
unit tests dropped from cordova-js that should get moved to plugin repos.
I can also provide an update on the BB roadmap.
On Mon, Oct 28, 2013 at 10:52 AM, Michal Mocny mmo...@chromium.org wrote:
I wanted to work on
I'm also interested on BB roadmap, and maybe talked to you Bryan and the BB
guys about the problems we are having in IBM trying integrate WebWorks SDK
and Cordova 3.1 and going forward.
On Mon, Oct 28, 2013 at 11:20 AM, Bryan Higgins br...@bryanhiggins.netwrote:
I would also like to work on
Carlos, pls email your address and shirt size offlist. =)
On Thu, Oct 24, 2013 at 6:18 AM, Carlos Santana csantan...@gmail.comwrote:
I'm attending ATO [1] conference and realize that will be cool to wear
Cordova t-shirt
Who do I need to bribe or how can I order one?
Oh by the way if any
Seeing an expected failure on their device may be the impetus for Microsoft or
any other device maker to change the api.
To me, hiding or not executing the test means we surrender to the fact that it
will never pass. Also, there could be cases where a solution exists but is not
yet known, and
It's most likely the way how the tool runs a script, there is a delay added
before it starts attaching I believe -- this is needed to make the whole
thing work (there is an intermediate python script that is called for
launching lldb).
This was a patch by a contributor, and I haven't had a chance
I grok the theory here but not sure I agree w/ the practice. The working
'master' should always be green. Working branches should be the place where
failing tests happen. If I'm looking to collaborate I won't be hacking on
any branches w/ failing tests b/c I'll just assume the developers are in
Nevermind then. Doesn't really matter considering tests will be broken out
into each repo anyway.
@purplecabbage
risingj.com
On Mon, Oct 28, 2013 at 9:22 AM, Brian LeRoux b...@brian.io wrote:
I grok the theory here but not sure I agree w/ the practice. The working
'master' should always be
Please assign doc fix to me, thanks. Am going to try to keep CLI doc from
spinning out of control the more features you guys add to it. ;-)
--Mike Sierra
From: Ray Camden [rayca...@adobe.com]
Sent: Friday, October 25, 2013 4:57 PM
To:
To be clear, as Michal said, the `cordova` CLI tool *does not* support this
directly; only indirectly, as part of the config.json file.
The fourth command line parameter relates only to the various bin/create
scripts that are part of each platform. The default template that is
overridden with
+1 to suggestion for adding it as arg to cordova platform add.
Could it be as simple as:
cordova platform add path/to/platform/type ?
-Michal
On Mon, Oct 28, 2013 at 1:56 PM, Ian Clelland iclell...@chromium.orgwrote:
To be clear, as Michal said, the `cordova` CLI tool *does not* support
So I am *completely* lost then. Can you explain what the config.json file
is? I¹ve never heard of it.
On 10/28/13, 12:56 PM, Ian Clelland iclell...@chromium.org wrote:
To be clear, as Michal said, the `cordova` CLI tool *does not* support
this
directly; only indirectly, as part of the
I disagree completely. Why does cordova need to know about the platform?
Right now when I make a virgin project, before I add *any* platform, there
is a default project created. All we want (well, ok, all I want ;) is the
ability to override that so I can have a ³blank² project as opposed to the
On Mon, Oct 28, 2013 at 2:07 PM, Michal Mocny mmo...@chromium.org wrote:
+1 to suggestion for adding it as arg to cordova platform add.
Could it be as simple as:
cordova platform add path/to/platform/type ?
Not sure if we could make it *that* simple :)
At least we could very easily make
Indeed, the CLI should not care about the platform. The ./cordova/create
script is very concerned with platform. That is where our impedance
mismatch exists. =)
We need ALL platforms to allow for this capability in ./cordova/bin/create
before we can surface in the CLI. That would be the next
On Mon, Oct 28, 2013 at 2:17 PM, Ray Camden rayca...@adobe.com wrote:
I disagree completely. Why does cordova need to know about the platform?
Right now when I make a virgin project, before I add *any* platform, there
is a default project created. All we want (well, ok, all I want ;) is the
Hmm. Ok, I *did* log a bug report for this already, and I think I just
assumed that this (https://issues.apache.org/jira/browse/CB-4652) was a
copy and mine was a dupe. Unfortunately now I can’t find it. So… I’ll file
a new one.
Sorry for the confusion folks!
On 10/28/13, 1:46 PM, Ian Clelland
Great that we cleared this up.
FWIW, there *is* already an issue for it (
https://issues.apache.org/jira/browse/CB-4153) and I linked it in my
original reply. Its about replacing the initial www/ template, and you can
do this today with a roundabout way by supplying a config into the
Ok, thanks for the update Michal.
On 10/28/13, 3:05 PM, Michal Mocny mmo...@chromium.org wrote:
Great that we cleared this up.
FWIW, there *is* already an issue for it (
https://issues.apache.org/jira/browse/CB-4153) and I linked it in my
original reply. Its about replacing the initial www/
FWIW, here is another idea for consideration.
For any additional mobile-spec tests which we developed in-house we
have adopted a convention of prefixing a JIRA reference for any test
which is known to fail (for whatever reason). This is based on the
assertion that any failing test ought to have
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/15004/
---
Review request for cordova.
Repository: cordova-site
Description
---
I
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/15004/#review27653
---
Ship it!
Ship It!
- Carlos Santana
On Oct. 29, 2013, 12:58
Our CI is failing with the message:
Error: No compatible version found: plugman@'=0.14.0- 0.15.0-'
npm ERR!
That is because I pushed plugman + cli to master but not to npm yet. That
will go away right when they get published to npm. After some more views on
the review of the blog post I will publish them.
On Monday, October 28, 2013, David Kemp wrote:
Our CI is failing with the message:
Error: No
Hey everyone,
Long time no commit but I was working on getting cordova 3.X support
working in ripple (really really close and about to release it) but I saw
some weird stuff in some of the plugins.
In the vibration plugin the base javascript calls into the cordova exec
module [1] and does all
Thats a cool heuristic for human readability (actually I think I'll adopt
it to some extent), but for something like CI (buildbot/medic) which
automatically emails if anything breaks, that solution doesn't quite
suffice.
However, its an interesting point that we could make use of some
If you are using both versions off master, why are you getting that error
message?
Seems it may happen if using master CLI and running npm install without
linking plugman first?
On Mon, Oct 28, 2013 at 9:52 PM, Steven Gill stevengil...@gmail.com wrote:
That is because I pushed plugman + cli
Just pulled latest cli/plugman to check that the version numbers deps,
and seems that they are. So im guessing its a tooling version mismatch on
the CI machine (using dev cli with released plugman).
-Michal
On Tue, Oct 29, 2013 at 12:57 AM, Michal Mocny mmo...@chromium.org wrote:
If you are
I am assuming the cli is doing npm install without linking. I changed the
plugman dependency to use 0.14.0 which wasn't live on npm at the time. I
pushed it to npm a little while ago. The tests should be be working now.
On Mon, Oct 28, 2013 at 9:57 PM, Michal Mocny mmo...@chromium.org wrote:
32 matches
Mail list logo
