OK,
now It's stuck on events which are waiting for initialization (in array
channel.deviceReadyChannelsArray)
https://github.com/apache/cordova-firefoxos/blob/master/lib/cordova.firefoxos.js#L5976
- onCordovaReady and onCordovaConnectionReady.
onCordovaReady is fired, but
I'm relatively new, but from what I've seen contributions are made only to
master. The older x.y.0 branches don't see any commits after they have been
released, unless there is a serious issue that would require an x.y.1 release
because x.y.0 was broken at it's inception.
But 3.0.0 hasn't been
So, I've been away from Cordova development for several months. I thought
I might look into fixing a few iOS bugs.
- I updated my cordova-ios repo and used the create script to create a
new test project as this seemed to be still available. I know cli is
available but I didn't see
Hey Piotr,
Most Cordova platforms include two stacks: a native and a web stack, or
side, or context. For example, Android and iOS implement various bits of
functionality (like access to contacts data) by bridging into the native
SDK APIs and making native calls, then sending messages back into
The project name provided to the cli is just a project name.
If you want to tweak the LABEL of your app, you should be changing the
contents of the config.xml file under your www/ folder. For more
information check out the config.xml section of the README [1].
[1]
That is awesome Andrew!
On 6/28/13 7:05 PM, Andrew Grieve agri...@chromium.org wrote:
Just added a plugin to mobile-spec that depends on other plugins. Here's a
3.0 flow that uses coho and the dependency plugin to build mobile-spec for
ios android where all plugins repos point to dev versions:
Great idea
On Mon, Jul 1, 2013 at 1:02 PM, Filip Maj f...@adobe.com wrote:
That is awesome Andrew!
On 6/28/13 7:05 PM, Andrew Grieve agri...@chromium.org wrote:
Just added a plugin to mobile-spec that depends on other plugins. Here's a
3.0 flow that uses coho and the dependency plugin to
Yep, at least Mike and I will be working this week. We are just coming
back from nodeconf, re-energized and ready to apply learnings to our node
tooling :)
On 6/28/13 5:02 PM, Joe Bowser bows...@gmail.com wrote:
I think most of the Vancouver committers are still working (I'm not).
On Jun 28,
I like this, allows for fine-grained support.
Does this proposal essentially EOL the engine elements in the plugin
spec? Is there a case where a plugin manifest would want to specify both
minimum/maximum cordova version constraints AS WELL AS platform os/sdk
constraints?
On 6/28/13 3:42 PM,
Copy/paste fine for this particular instance but if we start seeing every
other iOS plugin do a similar thing, I think that translates into
something that should be considered as the core iOS implementation
providing, no?
On 6/28/13 1:42 PM, Andrew Grieve agri...@chromium.org wrote:
Yeah, I
I think we still want engine. We (the Google team) discussed this tag a
while back, since it seemed to be contentless. It shouldn't need to be
changed often, since for most plugins the Cordova API is stable.
But sometimes the Cordova bridge or API changes in a way the plugin depends
on, and
Here's another take that, after discussing with Mike Brooks about, makes
more sense: introducing a `supports` API, something like:
cordova platform supports android
AND
cordova supports android
Both would invoke the same thing: essentially shelling out to
./bin/check_reqs for each platform.
Good day,
I just signed up to the mailing list, though I have been a very happy user of
Cordova for a while now. I am working on a plugin for Cordova, and have thus
far developed on iOS, and everything is fine. I started a new project with
Cordova OS X, and ported some code over. But it was
First, I know I should likely not be using 'master', but a named branch like
'2.9.x', but I cannot seem to wrangle git into doing this for me.
With that out of the way, I just did a git pull on the my locally cloned,
read-only repo. According to the last commit message - Remove CDVLogger
All right,
Thanks for your reply
- Original Message -
From: Marcel Kinard cmarc...@gmail.com
To: dev@cordova.apache.org
Sent: Tuesday, July 2, 2013 2:58:36 AM
Subject: Re: Question about the git workflow when working on a branch
I'm relatively new, but from what I've seen contributions
Hmmm,
I actually thought we were leaving logger in core and not pulling out the
console plugin. I at least marked it on jira
https://issues.apache.org/jira/browse/CB-3639. We should probably discuss
if this is something that we want to pull out into its own plugin.
CDVLogger is the reason
16 matches
Mail list logo
