Thanks for driving this Andrew! I hope infra doesn't hate us for this!!
On Thu, Feb 7, 2013 at 7:44 AM, Andrew Grieve wrote:
> https://issues.apache.org/jira/browse/INFRA-5839
>
>
> On Thu, Feb 7, 2013 at 10:36 AM, Andrew Grieve wrote:
>
>> Yep, agree. Until we can actually come up with somethin
Should probably start its life as markdown files in the cordova-cli
repo to allow interactive help during usage. (First place I'd go for
help using it would be the tool itself.)
On Thu, Feb 7, 2013 at 4:13 PM, Michael Brooks wrote:
> I would vote for it to be included in the Cordova documentation
I would vote for it to be included in the Cordova documentation (
docs.cordova.io).
Michael
On Thu, Feb 7, 2013 at 3:10 PM, Anis KADRI wrote:
> I don't know about getting started but I vote for it being part of
> docs.cordova.io
>
>
> On Thu, Feb 7, 2013 at 3:04 PM, Filip Maj wrote:
>
> > We h
Yes, each plugin should be responsible for its own tests. This is something
that we should practice with the core plugins and encourage with
third-party plugins.
I'm still playing catch up, but this is something that must be added to the
plugin spec IMO.
Michael
On Thu, Feb 7, 2013 at 12:48 PM,
Steve Gill and myself sat down on Friday and reviewed the state of the
documentation and where we need it to go.
The short-term goal is to host the documentation on
http://cordova.apache.org/docs and redirect with http://docs.cordova.io
The long-term goal is everything else - theming, organizatio
I don't know about getting started but I vote for it being part of
docs.cordova.io
On Thu, Feb 7, 2013 at 3:04 PM, Filip Maj wrote:
> We have none at the moment :)
>
> Any thoughts/recommendations on where it should go, what it should look
> like? Part of the getting started guide or no?
>
>
We have none at the moment :)
Any thoughts/recommendations on where it should go, what it should look
like? Part of the getting started guide or no?
I agree with window.plugins for everything that is not a polyfill.
On Thu, Feb 7, 2013 at 12:43 PM, Filip Maj wrote:
> Agree with everything Jesse said. cordova.plugins could be considered
> "safe", but not required. It's just JavaScript!
>
> On 2/6/13 6:27 PM, "Jesse" wrote:
>
> >> I would pr
and I would like to point you to this document which will help you set your
environment
https://git-wip-us.apache.org/
On Thu, Feb 7, 2013 at 12:45 PM, Filip Maj wrote:
> You should be committing to Apache repos:
> https://git-wip-us.apache.org/repos/asf/
>
> If you go to http://people.apache.
I don't think this feature would take that ability away..
If using the cordova-cli tools as an example of what happens, you have a
structure like:
Project
|-www <- your app assets
`-platforms <--- android, iOS, etc projects
Anything you put into www will be copied into the platforms/
I don't think we'd want to take away the ability to just copy in a file to
the www/ directory. I think it might be better for them to opt-in the files
they want to have included in this auto-inject system. Prototyping SGTM.
On Thu, Feb 7, 2013 at 3:36 PM, Filip Maj wrote:
> Good points Shaz a
This is definitely what I had envisioned as well..
On 2/7/13 11:13 AM, "Andrew Grieve" wrote:
>If someone wants to lead the charge on this angle of the plugin
>splitting-out, that would be awesome. On the priority list though, I think
>it's pretty low. Right now you have to set up the project f
Not sure.. Michael's had a busy week and he's had ideas on this one for a
while. Mike?
On 2/7/13 10:31 AM, "Marcel Kinard" wrote:
>Poking this thread with the release of 2.4.
>
>Where are we at?
>
>Is there anything I can do to help?
>
>-- Marcel Kinard
>
>On Jan 17, 2013, at 12:19 PM, Michael
You should be committing to Apache repos:
https://git-wip-us.apache.org/repos/asf/
If you go to http://people.apache.org/committer-index.html and search for
your last name, you'll see that you are a committer listed under the
cordova project.
I'm CC'ing Brian. Brian, can you check Paul's permissi
Agree with everything Jesse said. cordova.plugins could be considered
"safe", but not required. It's just JavaScript!
On 2/6/13 6:27 PM, "Jesse" wrote:
>> I would prefer cordova.plugins instead of directly on cordova.
>+1
>
>I agree, and like having core plugins live under cordova.plugins.*, bu
Good points Shaz and Andrew.
I'm up for trying it out (I think we're at a point where we should
prototype the approaches to get further).
The plugin.xml manifest lists web assets via elements. Couple q's relating to this:
- I guess we use the target attribute on all of these elements to
determi
The doc's not up-to-date, but I think we ended on consensus for the code
version. I've taken a stab at updating the wiki pages:
http://wiki.apache.org/cordova/CordovaAndGit -- Added the idea of having
both a master and a next branch
http://wiki.apache.org/cordova/CommitterWorkflow -- Added Jesse
If someone wants to lead the charge on this angle of the plugin
splitting-out, that would be awesome. On the priority list though, I think
it's pretty low. Right now you have to set up the project file, add the
JS, and then run the tests. This model will still work when plugins are
separated out.
Poking this thread with the release of 2.4.
Where are we at?
Is there anything I can do to help?
-- Marcel Kinard
On Jan 17, 2013, at 12:19 PM, Michael Brooks wrote:
>>
>> I've got Jenkins running locally, pulling from cordova-docs, polling daily,
>> and generating the docs. But the SVN Pub
With 2.5 starting, it appears time to poke this thread.
- Is the Google doc refreshed with the latest consensus?
- If so, should the Google doc be transferred to a wiki page?
- Have the necessary branches been created?
- Are we all in the boat, and understand how to row this beast?
-- Marcel Kina
I don't want to jump forward too far, but would it make sense to breakup
mobile-spec in a similar way so that the tests for a plugin are actually
located in the plugin's repo? Then the test and the function under test would
be synchronized. And it could potentially open the way for third-parties
Hi Anis,
Do you have an idea of what could go wrong with codova repositories access
rights?
in the mail i received there was :
Please note that until the Project Management Committee responsible for the
> project to which you were given group membership actually grants you access
> to the relev
https://issues.apache.org/jira/browse/INFRA-5839
On Thu, Feb 7, 2013 at 10:36 AM, Andrew Grieve wrote:
> Yep, agree. Until we can actually come up with something better, we need
> to support Media.
>
>
> On Wed, Feb 6, 2013 at 3:13 PM, Becky Gibson wrote:
>
>> Well, we still need an API/plugin
Yep, agree. Until we can actually come up with something better, we need to
support Media.
On Wed, Feb 6, 2013 at 3:13 PM, Becky Gibson wrote:
> Well, we still need an API/plugin for playing audio. The w3c spec is
> pretty involved. In the past Simon has suggested we try to unify around
> HT
If it's OK, because I don't plan to contribute often, I've just attached a
formatted patch.
If I start to do loads of bug fixes, I'll sort out proper forking. Depends
if I'm assigned to the project full time again or not!
>From 2279ccda9ada8ec5d7189eb3cbb7ae0f29626ef0 Mon Sep 17 00:00:00 2001
Fro
TASS tsss tsss :-)
-Original Message-
From: Anis KADRI [mailto:anis.ka...@gmail.com]
Sent: Wednesday, February 06, 2013 8:12 PM
To: dev@cordova.apache.org
Subject: Re: a Cordova Jake Error ?
The beauty of Mac OS X users and their case-insensitive filesystems :-)
On Wed, Feb 6, 2013 at
26 matches
Mail list logo