On the topic of IDE support my collage Gorkem has made a nice wizard in eclipse
that mimics the CLI have a look at this video
http://www.youtube.com/watch?v=QUyUUtmTYok
On 18 Oct,2013, at 4:29 , Maxime LUCE max...@somatic.fr wrote:
Great Bryan
Totally agree !!!
Cordialement.
Issue INFRA-6894 - add github mirror for cordova-registry,
cordova-registry-web https://issues.apache.org/jira/browse/INFRA-6894 has
been successfully created.
On Thu, Oct 17, 2013 at 7:32 PM, Brian LeRoux b...@brian.io wrote:
ya we want everything possible to be mirrored
On Thu, Oct 17,
Usually just having the JIRA number works, but i think for this case having
the platform would be nice
On Oct 17, 2013, at 10:41 PM, lmnbeyond lmnbey...@gmail.com wrote:
Hi guys,
Since plugin-related code are all grouped into its own repo, should we add
platform info in commit
Those two sound more like things the info command should be printing. Or do
you mean those should be part of plugins.Cordova.io?
On Oct 17, 2013 8:38 PM, purplecabbage purplecabb...@gmail.com wrote:
+ list platforms supported for each plugin
+ list all plugins available for a platform
Sent
On Oct 17, 2013, at 7:54 PM, Steven Gill stevengil...@gmail.com wrote:
So looks like want to to start including more data on
http://plugins.cordova.io.
Repo tag - points to repo where plugin lives
Issue tag - points to issue tracker (with component for jira)
Testing related (can get
Chiming in late here, but I thought Cordova-registry was a temporary repo
Anis had set up during development of the registry, but that it's now
folded into Cordova-plugman, and can be retired.
Does it hold the website?
Braden
On Oct 18, 2013 7:55 AM, David Kemp drk...@google.com wrote:
Issue
I may take a pass at a blog post or something highlighting the issues between
the two, that might be useful.
John M. Wargo
Mobile Platform Product Management
SAP | Charlotte, NC | USA
Office: +1 704.321.0265 | Mobile: +1 704.249.7476
Email: john.wa...@sap.com
Twitter: @johnwargo
-Original
Absolutely. That's ultimately my issue with this conversation - we're being too
absolute. I use the CLI with IDEs all the time and it never gives me issues.
It's not optimal, but I can get what I need done.
John M. Wargo
Mobile Platform Product Management
SAP | Charlotte, NC | USA
Office: +1
I mean, can I help you with this. Not quite sure where that 'u' came from.
John M. Wargo
-Original Message-
From: Wargo, John [mailto:john.wa...@sap.com]
Sent: Friday, October 18, 2013 9:51 AM
To: dev@cordova.apache.org
Subject: RE: config.xml discussion, we need to talk
Mike,
Can
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/14733/#review27193
---
Better is probably to switch to child_process.spawn instead, using
This thread is about what info is displayed on plugins.cordova.io
Sent from my iPhone
On Oct 18, 2013, at 5:43 AM, Lucas Holmquist lholm...@redhat.com wrote:
On Oct 17, 2013, at 7:54 PM, Steven Gill stevengil...@gmail.com wrote:
So looks like want to to start including more data on
On Oct 17, 2013, at 7:54 PM, Steven Gill stevengil...@gmail.com wrote:
So looks like want to to start including more data on
http://plugins.cordova.io.
Repo tag - points to repo where plugin lives
Issue tag - points to issue tracker (with component for jura)
+1 for these,
Testing
Awesome video!!
On Fri, Oct 18, 2013 at 3:43 AM, Erik Jan de Wit ede...@redhat.com wrote:
On the topic of IDE support my collage Gorkem has made a nice wizard in
eclipse that mimics the CLI have a look at this video
http://www.youtube.com/watch?v=QUyUUtmTYok
On 18 Oct,2013, at 4:29 ,
+1 for canonical repo location and Issue tracker (where available)
Other metadata that could be useful on the repo interface:
Description (1 line summary; possibly also a short 1 or 2 paragraph
description as well)
Docs link (if applicable)
Home page link (if applicable)
Author (I know it's
The repos exist on apache, but are empty.
Unless someone can clearly state that the repos ought to go away, I will
leave the INFRA ticket open.
If they are not going to be used, we should file a different ticket...
On Fri, Oct 18, 2013 at 8:57 AM, Braden Shepherdson bra...@google.comwrote:
Website should show the README.md that is a sibling of the plugin.xml file.
On Fri, Oct 18, 2013 at 10:56 AM, Lucas Holmquist lholm...@redhat.comwrote:
On Oct 17, 2013, at 7:54 PM, Steven Gill stevengil...@gmail.com wrote:
So looks like want to to start including more data on
Hi. I ended up skipping my Spanish class and signing onto the Youtube
broadcast. I took some longer note, feel free to skim through:
https://docs.google.com/document/d/1IVyfFZ-kCIkg1Cnftxfm3viXHpxpJ2zdVa8B1CK0qU0/(Was
going to paste them but they turned out a lot longer than I
remembered...)
I
Yes I meant plugins.xml
On Oct 18, 2013, at 5:43 AM, Lucas Holmquist lholm...@redhat.com wrote:
On Oct 17, 2013, at 7:54 PM, Steven Gill stevengil...@gmail.com wrote:
So looks like want to to start including more data on
http://plugins.cordova.io.
Repo tag - points to repo where
On Oct. 18, 2013, 2:09 p.m., Braden Shepherdson wrote:
Better is probably to switch to child_process.spawn instead, using the
option stdio: 'inherit' if we're in --verbose mode, and stdio: 'ignore'
when not verbose. That avoids buffering the output altogether, which we
don't really
plugin.xml metadata is looking more and more like a package.json (i.e. npm)
;-p
On Fri, Oct 18, 2013 at 11:40 AM, Steve Gill stevengil...@gmail.com wrote:
Yes I meant plugins.xml
On Oct 18, 2013, at 5:43 AM, Lucas Holmquist lholm...@redhat.com
wrote:
On Oct 17, 2013, at 7:54 PM,
i was just thinking the same thing :)
On Oct 18, 2013, at 12:06 PM, Carlos Santana csantan...@gmail.com wrote:
plugin.xml metadata is looking more and more like a package.json (i.e. npm)
;-p
On Fri, Oct 18, 2013 at 11:40 AM, Steve Gill stevengil...@gmail.com wrote:
Yes I meant
WOOOHOOO!! That's awesome!!!
On Fri, Oct 18, 2013 at 12:47 PM, Carlos Santana csantan...@gmail.comwrote:
I think the Cordova Gods are on my side this week !
I got approval from my company for travel funding.
travel['Kw Hotel And Conference Ctr']('105 King Street
Hi everyone,
As I said before, I'm working on the Windows 8.1 port of Cordova base on the
Windows 8 one.
I sent an email with my first thoughts about the improvements we have to do and
there are few.
In order to make platform addition easier in future, I created and resolved an
issue on JIRA
seems like a small change which would greatly increase the readability of
plugin history, and enable us to quickly generate platform specific
changelogs.
+1
On Thu, Oct 17, 2013 at 7:41 PM, lmnbeyond lmnbey...@gmail.com wrote:
Hi guys,
Since plugin-related code are all grouped into its
+1 to metadata for repo location.
However, I'm still not 100% why these plugins should live in the platform
repo? Its just an arbitrary container, right? I think the fact thats its
a plugin is more relevant than the fact that they only support ios. If
cordova-labs doesn't feel right, then why
There was a discussion earlier about removing the square brackets because
it did something funny with some tool, so I would remove the square
brackets.
On Thu, Oct 17, 2013 at 7:41 PM, lmnbeyond lmnbey...@gmail.com wrote:
Hi guys,
Since plugin-related code are all grouped into its own
+1 to repo / issue / website / docs etc metadata
-1 *for now* to dependencies at specific versions, and testing related
changes like mode, just because its not clear what the right solution to
these problems is. We do need to address it, but those topics will likely
move to separate discussions.
Erik that's great! Where can we download it?
On Oct 18, 2013 8:01 AM, Andrew Grieve agri...@chromium.org wrote:
Awesome video!!
On Fri, Oct 18, 2013 at 3:43 AM, Erik Jan de Wit ede...@redhat.com
wrote:
On the topic of IDE support my collage Gorkem has made a nice wizard in
eclipse that
I would hate to see plugins that are currently ios only get put there, and
then later have another platform supported. That would be ugly.
Can we at least insist that any plugin that goes in the ios platform have a
name like ios-* (likewise for other platforms)
On Fri, Oct 18, 2013 at 1:07 PM,
+1 to CB-1234:[ios] syntax
On Fri, Oct 18, 2013 at 10:39 AM, Ian Clelland iclell...@chromium.orgwrote:
One of the git tools will discard the bracketed items if they appear at the
beginning of the commit description (I think it's git-am, because it is
intended to apply patches from mailboxes,
If you namespace it to the platform, and later it makes sense to support it
on another device, you will have even more issues.
I think the best approach mentioned is the cordova-plugins repo which is
like the wild-west that is purplecabbage/phonegap-plugins except it is
managed by cordova
Alright, +1 to creating a cordova-plugins repo as an alternative to new
repos for every possible plugin (plugman and registry have for a while
supported git subdirectories so we don't need repo isolation). However, I
would also be fine with just using cordova-labs plugin branch, especially
once
Not feeling hot about the namespace thing - as Jesse said it might limit
us. Ok - if we do a cordova-plugins repo it won't be hard to move the
plugins branch to it with a filter-branch option, preserving history --
great.
I think a generic preferences plugin is ok (wouldn't be hard to convert
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/14681/
---
(Updated Oct. 18, 2013, 6:27 p.m.)
Review request for cordova.
Changes
John: If you decided to take a stab a blogging about it, please think about
blogging on the cordova site! We can all review it before publishing it too!
Erik: that video was awesome! Let me know when Gorkem does a release and I
can post it on the cordova twitter feed.
Michal: Could just be CLI
Sure we can debate the exact interface when it comes to it. Could use
predefined constants instead of strings to help with typing/discoverability:
navigator.cordovaPreferences.setPreference(win, fail,
navigator.cordovaPreferences.PREFERENCE-iOS-GapBetweenPages, 0);
On Fri, Oct 18, 2013 at 2:17
+1 for adding metadata but should more of the metadata be compulsory?
JBoss tools plugin discovery uses the cordova.io registry and some of the
plugins are missing a lot to. http://snag.gy/aAxjL.jpg is a screenshot
that shows how the case. http://snag.gy/J8rl6.jpg is a screenshot of a few
SinglePlatform vs MultiPlatform makes the most sense to me.
SinglePlatform = Focus on a single platform, and use plugman and the
platform scripts directly. Useful when you only have that particular device
to test on, or only have access to that device's marketplace. Also useful
for platform
On Fri, Oct 18, 2013 at 2:28 PM, Steven Gill stevengil...@gmail.com wrote:
John: If you decided to take a stab a blogging about it, please think about
blogging on the cordova site! We can all review it before publishing it
too!
Erik: that video was awesome! Let me know when Gorkem does a
When someone creates a vanilla iOS project from the CLI, the default app is
8 MB. It's obvious why this is so, the www/res folder includes all the
icons for all the platforms and is 8 MB.
Can we change this (why include all icons -- the www should be agnostic),
or is this a documentation problem.
I have created an issue to track the meta tag addition.
https://issues.apache.org/jira/browse/CB-5128
I agree with doing validation with plugman during publish time. We should
decide soon which ones are going to be mandatory and which ones will be
optional. Probably update the plugin spec + our
They should be in the merge folder under each platform instead of the www.
On Fri, Oct 18, 2013 at 11:52 AM, Shazron shaz...@gmail.com wrote:
When someone creates a vanilla iOS project from the CLI, the default app is
8 MB. It's obvious why this is so, the www/res folder includes all the
I'd love to have this fixed as part of CB-2606; There's a lot we could do
to make icons and splashscreens better.
On Fri, Oct 18, 2013 at 2:52 PM, Shazron shaz...@gmail.com wrote:
When someone creates a vanilla iOS project from the CLI, the default app is
8 MB. It's obvious why this is so,
I think SinplePlatform vs MultiPlatform is misleading because you can use
the CLI to do single platform development.
On Fri, Oct 18, 2013 at 11:51 AM, Jesse purplecabb...@gmail.com wrote:
SinglePlatform vs MultiPlatform makes the most sense to me.
SinglePlatform = Focus on a single platform,
I talked to Anis.
We are planning on moving the registry stuff into those repos. Continue
with the mirroring
On Fri, Oct 18, 2013 at 8:31 AM, David Kemp drk...@google.com wrote:
The repos exist on apache, but are empty.
Unless someone can clearly state that the repos ought to go away, I
IDE or cordova-cli ??
@purplecabbage
risingj.com
On Fri, Oct 18, 2013 at 12:02 PM, Steven Gill stevengil...@gmail.comwrote:
I think SinplePlatform vs MultiPlatform is misleading because you can use
the CLI to do single platform development.
On Fri, Oct 18, 2013 at 11:51 AM, Jesse
I like that better.
I know that both methods use the command line, but the cordova-cli has cli
in its name! We call the tool the cordova-cli so it might be more confusing
going away from that and calling it anything else. Not saying we shouldn't
be open to a name change though just because we
+1 to merges/
I don't mind the 8megs shipped with the default helloworld, but it should
not be copied into platform's www for sure.
-Michal
On Fri, Oct 18, 2013 at 3:01 PM, Ian Clelland iclell...@chromium.orgwrote:
I'd love to have this fixed as part of CB-2606; There's a lot we could do
to
Also, the images we use are ridiculous large considering we want people to
replace them.
@purplecabbage
risingj.com
On Fri, Oct 18, 2013 at 12:38 PM, Michal Mocny mmo...@chromium.org wrote:
+1 to merges/
I don't mind the 8megs shipped with the default helloworld, but it should
not be
Didn't think about merges -- +1 merges for moi
On Fri, Oct 18, 2013 at 12:41 PM, Jesse purplecabb...@gmail.com wrote:
Also, the images we use are ridiculous large considering we want people to
replace them.
@purplecabbage
risingj.com
On Fri, Oct 18, 2013 at 12:38 PM, Michal Mocny
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/14757/#review27201
---
Ship it!
Ship It!
- Anis Kadri
On Oct. 18, 2013, 7:59 p.m., Max
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/14757/#review27202
---
Ship it!
Looks Great!
- Steven Gill
On Oct. 18, 2013, 7:59
In response to Braden,
There are two (couch) apps to consider:
1) registry (which based on npmjs.org). I don't think we'll be
modifying this one very much but we might add in some API calls etc.
This is 'http://registry.cordova.io'
2) registry ui: this is the front-end for
I added some validation for plugin names (to follow
reverse-domain-name convention) a couple of weeks ago but there needs
to be more of it for sure.
On Fri, Oct 18, 2013 at 11:59 AM, Steven Gill stevengil...@gmail.com wrote:
I have created an issue to track the meta tag addition.
I have created an issue to keep track of the registry refactor.
https://issues.apache.org/jira/browse/CB-5130
On Fri, Oct 18, 2013 at 2:04 PM, Anis KADRI anis.ka...@gmail.com wrote:
I added some validation for plugin names (to follow
reverse-domain-name convention) a couple of weeks ago but
We need more suggestions!
Anis suggested picking to arbitrary names that don't reflect the workflows
but would be easy to refer to.
On Fri, Oct 18, 2013 at 12:41 PM, Michal Mocny mmo...@chromium.org wrote:
I use the IDE with the CLI and hope to make it better.
In my mind, the old way is
Brian suggested Project Development (CLI workflow) vs Platform Development
(bin/scripts)
On Fri, Oct 18, 2013 at 3:09 PM, Steven Gill stevengil...@gmail.com wrote:
We need more suggestions!
Anis suggested picking to arbitrary names that don't reflect the workflows
but would be easy to refer
The reason it's those plugins is, correct me if I'm wrong, but it is
implied we are supporting those. Months and months ago we already
encouraged[1] plugin authors to move out their plugins to their own repos
from phonegap-plugins because of:
* issue tracking
* user contributions (pull requests)
I think having a staging area for plugins is a good idea and leaving
cordova-labs as a prototyping area. Ideally we graduate plugins out of
cordova-plugins if they get any sort of traction at all and require
discreet issue tracking.
On Fri, Oct 18, 2013 at 1:31 PM, Anis KADRI
Ya, to me the difference is that one workflow embraces the native platform
and tooling (plugman and bin/scripts) while the other focuses on building a
web project (cli/merges/etc).
As a dev, if I'm ONLY worried about one platform (like a Cordova
implementor or many of our community folk) then
ya merges
also think we should redo that app to something more sane and tiny
On Fri, Oct 18, 2013 at 12:53 PM, Shazron shaz...@gmail.com wrote:
Didn't think about merges -- +1 merges for moi
On Fri, Oct 18, 2013 at 12:41 PM, Jesse purplecabb...@gmail.com wrote:
Also, the images we use
Builds are failing due to an inability to add plugins.
This started about 8:2pm with three plugman commits by Tim Kim
error text:
Fetching plugin from ../cordova-mobile-spec/dependencies-plugin...
Starting installation of org.cordova.mobile-spec-dependencies for
ios[Error: Different version
Hey there David,
I just committed a fix for mobile spec. I believe the problem was that the
engine tag in cordova-mobile-spec/dependencies-plugin/plugin.xml needed to
have a patch portion to the version.
On 18 October 2013 17:48, David Kemp drk...@chromium.org wrote:
Builds are failing due to
Hi Tim,
That has indeed fixed the master branch, but the 3.1 release branch still
has the problem. I currently always build with the latest tool chain
(plugman) so a non backward-compatible change to plugman will be an issue.
That would require that the fix to mobilespec be back-patched to 3.1 as
Hrmmm. Shoot. Funny how a '.0' can paint you into a corner.
I'm not sure if there are any easy solutions to this one since the code
always pulls the latest. I think what I'll do is add some logic such that
the new version-compare in plugman can handle differing version strings.
Unfortunately it's
Cross Platform - use Merge Flow
Single Platform - use Legacy Flow
Using Multi Platform or Cross Platform is also fine
Using Flow or Mode is also fine
On Friday, October 18, 2013, Brian LeRoux wrote:
Ya, to me the difference is that one workflow embraces the native platform
and tooling
I like merge-flow and legacy-flow
Sent from my iPhone
On Oct 18, 2013, at 6:59 PM, Carlos Santana csantan...@gmail.com wrote:
Cross Platform - use Merge Flow
Single Platform - use Legacy Flow
Using Multi Platform or Cross Platform is also fine
Using Flow or Mode is also fine
On
67 matches
Mail list logo