On Wed, Jan 2, 2013 at 11:05 PM, Michal Mocny mmo...@chromium.org wrote:
On Wed, Jan 2, 2013 at 7:27 PM, Andrew Grieve agri...@chromium.org
wrote:
From my understanding of git, there's nothing special about the master
branch, except that it's what gets checked out when someone doesn't
Aside from bug fixes, are there ideas on what you think will be tackled
for 2.4? I suspect at least some of you have ideas in your head that I
haven't fully seen written here. I'm just looking for a high-level
bullet list. I'm not looking for promises, instead just to set some
rough
On Thu, Jan 3, 2013 at 9:43 AM, Andrew Grieve agri...@chromium.org wrote:
On Wed, Jan 2, 2013 at 11:05 PM, Michal Mocny mmo...@chromium.org wrote:
On Wed, Jan 2, 2013 at 7:27 PM, Andrew Grieve agri...@chromium.org
wrote:
From my understanding of git, there's nothing special about the
[
https://issues.apache.org/jira/browse/CB-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13543176#comment-13543176
]
Jasper commented on CB-1807:
Hi Andrew / Joe
I tested the changeset by applying it to 2.2 on
[
https://issues.apache.org/jira/browse/CB-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13543180#comment-13543180
]
Chad Crowell commented on CB-2102:
--
Hi Shazron - just wondering if there is any activity on
[
https://issues.apache.org/jira/browse/CB-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13543193#comment-13543193
]
Andrew Grieve commented on CB-1807:
---
No, it should say none in that case. Can you try this
[
https://issues.apache.org/jira/browse/CB-2127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse MacFadyen resolved CB-2127.
-
Resolution: Fixed
Update JavaScript for WP8
-
Key:
[
https://issues.apache.org/jira/browse/CB-2120?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Kim resolved CB-2120.
-
Resolution: Fixed
Update JavaScript for BlackBerry
Key:
Go with Anis' (imhotep) plugman tool as the defacto plugin installation
tool, until we get it into an Apache repo (probably cordova-cli?). It was
based on Andrew's plugin spec and pluginstall tool but started deviating
slightly once we (Cordova) wanted to support more robust use cases
There are always bug fixes and issues that can easily take up one's time
for any given platform. It's a constant battle :)
I will be focusing around the cli tooling and putting more work into the
plugin specification + the plugin tooling, with the goal being to achieve
the light core and
I think we should add a Guide for Plugin Packaging --- things will
move quicker, and b/c src is more canonical it is more likely to
encourage contrib.
On Thu, Jan 3, 2013 at 11:46 AM, Filip Maj f...@adobe.com wrote:
Go with Anis' (imhotep) plugman tool as the defacto plugin installation
tool,
Why not iterate on the existing Plugin Development Guide [1] ?
http://docs.phonegap.com/en/2.2.0/guide_plugin-development_index.md.html#Pl
ugin%20Development%20Guide
On 1/3/13 11:55 AM, Brian LeRoux b...@brian.io wrote:
I think we should add a Guide for Plugin Packaging --- things will
move
[
https://issues.apache.org/jira/browse/CB-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13543244#comment-13543244
]
Jasper commented on CB-1807:
I have replaced the cordova.android.js with the 2.3.0rc2 one. I can
I thought this meant we move the JS out of CordovaJS and start moving
it into plugin packages.
On Thu, Jan 3, 2013 at 12:02 PM, Filip Maj f...@adobe.com wrote:
time? If so, I disagree. The reason we tag the JS and need consensus on it
[
https://issues.apache.org/jira/browse/CB-1807?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13543249#comment-13543249
]
Andrew Grieve commented on CB-1807:
---
Okay, thanks for giving that a go. I'll test it out on
Our general goal for Cordova 3.x is composability. Extending the core
should be trivially simple, with tools for discovering, adding,
removing, creating, validating, and publishing Plugin Packages. This
will make creating downstream distributions easier, developers using
Cordova won't be building
ave
-Mensaje original-
De: brian.ler...@gmail.com [mailto:brian.ler...@gmail.com] En nombre de
Brian LeRoux
Enviado el: jueves, 03 de enero de 2013 21:35
Para: dev@cordova.apache.org
Asunto: the great seperatino of concerns
Our general goal for Cordova 3.x is composability. Extending the
[
https://issues.apache.org/jira/browse/CB-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shazron Abdullah updated CB-2102:
-
Component/s: iOS
Sorry I missed this since it wasn't tagged iOS. Looking at it now.
This would mean the next steps would be:
- BlackBerry support for Plugman
- Windows Phone support for Plugman
Jesse and I sent pull requests to Lunny's original pluginstall repo for
support for both blackberry and wp7 a LONG time ago. At the time there was
more focus from Lunny on PhoneGap
Our CorePlatforms wiki article [1] has this:
Core: These are the main platforms supported by the Apache Cordova project.
* iOS
* Android
* BlackBerry
* Windows Phone
* Bada
Sunset: These are platforms considered to be on their way out of general
consumer availability. We offer code, but
In parallel, we'd look at moving core plugins out into individual
repos. We should take this slow, and start w/ something simple, like
org.apache.cordova.geolocation (which will help us move Coho and
Robson tools to make this transition transparent to the users
downloading downstream
Sorry about this. I'm absolutely trying to drive correct spelling, but it's
sometimes rather hard to find fallout that's beyond what I can see.
Glad that it's fanning out properly (unfortunately with some minor bumps as we
go).
-Original Message-
From: Tim Kim
Hey All,
Just a quick update not that some of the commit messages referenced
directly (from the Pull Request) may have changed (i.e. been rebased), in
case you are wondering why they do not work anymore (if anyone is still
checking out this thread, that is). :-)
(pull request link again) -
[
https://issues.apache.org/jira/browse/CB-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13543345#comment-13543345
]
Shazron Abdullah commented on CB-2102:
--
Found the culprit, it's an iOS CordovaJS
[
https://issues.apache.org/jira/browse/CB-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Kim resolved CB-2142.
-
Resolution: Fixed
Tag BlackBerry
--
Key: CB-2142
URL:
[
https://issues.apache.org/jira/browse/CB-2142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13543348#comment-13543348
]
Tim Kim commented on CB-2142:
-
Fixed here:
[
https://issues.apache.org/jira/browse/CB-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shazron Abdullah updated CB-2102:
-
Comment: was deleted
(was: Found the culprit, it's an iOS CordovaJS problem. This line is always
What does schedule for removal mean? Perhaps we can tie removal to some
specific metric that we might be able to assist with? BB7 will remain a fairly
large base of devices for a while, particularly in emerging markets and
enterprise, where I think we will continue to see a large focus on
[
https://issues.apache.org/jira/browse/CB-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13543351#comment-13543351
]
Shazron Abdullah commented on CB-2102:
--
Deleted my last comment. It's a combination:
On
[
https://issues.apache.org/jira/browse/CB-2125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herm Wong resolved CB-2125.
---
Resolution: Fixed
Update JavaScript for webOS
---
Key: CB-2125
[
https://issues.apache.org/jira/browse/CB-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herm Wong resolved CB-2147.
---
Resolution: Fixed
Tag webOS
-
Key: CB-2147
URL:
[
https://issues.apache.org/jira/browse/CB-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13543368#comment-13543368
]
Shazron Abdullah commented on CB-2102:
--
The viewcontroller is nil:
Certainly, if RIM can provide some % numbers of people using each OS,
that'd be helpful! Kind of like the Android OS pie chart breakdown of
users across different OS versions.
In the past, at some point we decided to stop supporting BB OS 5 and 4.6,
and removed those Cordova implementations. Just
Sounds like a plan. I'll do some digging on what plans we will have on
publishing market numbers, publically or otherwise. ;)
Thanks.
--
Ken Wallis
Product Manager – BlackBerry WebWorks
Research In Motion
(905) 629-4746 x14369
From: Filip Maj
[
https://issues.apache.org/jira/browse/CB-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13543381#comment-13543381
]
Shazron Abdullah commented on CB-2102:
--
Ok, here's what's happening. This user-agent
Sorry about the duplicate bug - I should have either have pulled master and
rebuilt or checked the already filed tickets!
On Wed, Jan 2, 2013 at 2:49 PM, Tim Kim timki...@gmail.com wrote:
Ok cool :)
On 2 January 2013 11:45, Becky Gibson gibson.be...@gmail.com wrote:
Whatever works! I
[
https://issues.apache.org/jira/browse/CB-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13543399#comment-13543399
]
Shazron Abdullah commented on CB-2102:
--
I set the UA back to what is expected, and now
[
https://issues.apache.org/jira/browse/CB-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13543404#comment-13543404
]
Shazron Abdullah commented on CB-2102:
--
Note: On iOS 5.1 everything is fine :/
[
https://issues.apache.org/jira/browse/CB-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13543405#comment-13543405
]
Shazron Abdullah commented on CB-2102:
--
More notes:
When I put in the workaround (set
[
https://issues.apache.org/jira/browse/CB-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13543415#comment-13543415
]
Chad Crowell commented on CB-2102:
--
Thanks for all your hard work. At this point, is the
[
https://issues.apache.org/jira/browse/CB-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13543417#comment-13543417
]
Joe Bowser commented on CB-1700:
This issue appears to still exist. The gallery fix appears
[
https://issues.apache.org/jira/browse/CB-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13543423#comment-13543423
]
Shazron Abdullah commented on CB-2102:
--
That is my recommendation, use the iframe bridge
Would love more #'s on Bada and BB before we get too aggressive. I
updated the Horizon section to Firefox OS. (Ubuntu is supported by way
of our Qt codebase.)
On Thu, Jan 3, 2013 at 2:44 PM, Ken Wallis kwal...@rim.com wrote:
Sounds like a plan. I'll do some digging on what plans we will have on
[
https://issues.apache.org/jira/browse/CB-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13543427#comment-13543427
]
Joe Bowser commented on CB-2093:
I can reproduce this without using Picasa using the Samsung
[
https://issues.apache.org/jira/browse/CB-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13543431#comment-13543431
]
Joe Bowser commented on CB-2093:
I don't get crazy exceptions, I just get this instead!
[
https://issues.apache.org/jira/browse/CB-2093?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13543430#comment-13543430
]
Joe Bowser commented on CB-2093:
Also reproducible on Nexus 7 with stock gallery app.
[
https://issues.apache.org/jira/browse/CB-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13543433#comment-13543433
]
Shazron Abdullah commented on CB-2102:
--
No, it's not a problem with loading PDFs.
The idea has been proposed that we even add an ./emulate folder for
Ripple to consume ---tests, docs, src, and emulation all into the
Package format.
On Thu, Jan 3, 2013 at 3:11 PM, Michael Brooks mich...@michaelbrooks.ca wrote:
@fil @dave, yes to both test suite and docs.
On Thu, Jan 3, 2013
[
https://issues.apache.org/jira/browse/CB-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13543442#comment-13543442
]
Shazron Abdullah edited comment on CB-2102 at 1/4/13 12:08 AM:
---
[
https://issues.apache.org/jira/browse/CB-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13543442#comment-13543442
]
Shazron Abdullah commented on CB-2102:
--
Re-cap.
Problem:
This problem only occurs on
Read this and weep:
https://issues.apache.org/jira/browse/CB-2102?focusedCommentId=13543442page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-13543442
tl;dr
If you have a multi-page app, and you use iOS 6, you must use iframe bridge
mode.
On Wed, Jan 2, 2013 at 3:07
Amended:
If you have a multi-page app, and you use InAppBrowser, and you use iOS 6,
you must use iframe bridge mode.
On Thu, Jan 3, 2013 at 4:10 PM, Shazron shaz...@gmail.com wrote:
Read this and weep:
[
https://issues.apache.org/jira/browse/CB-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13543442#comment-13543442
]
Shazron Abdullah edited comment on CB-2102 at 1/4/13 12:12 AM:
---
[
https://issues.apache.org/jira/browse/CB-2102?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shazron Abdullah updated CB-2102:
-
Labels: InAppBrowser iOS6 (was: InAppBrowser)
Priority: Major (was: Minor)
Gord created CB-2156:
Summary: Add support for InAppBrowser to BlackBerry 10
Key: CB-2156
URL: https://issues.apache.org/jira/browse/CB-2156
Project: Apache Cordova
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/CB-2157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gord reassigned CB-2157:
Assignee: Gord (was: Tim Kim)
Add support for Contacts API in BlackBerry 10
Gord created CB-2157:
Summary: Add support for Contacts API in BlackBerry 10
Key: CB-2157
URL: https://issues.apache.org/jira/browse/CB-2157
Project: Apache Cordova
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/CB-2121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shazron Abdullah resolved CB-2121.
--
Resolution: Fixed
Fix commit - http://git-wip-us.apache.org/repos/asf/cordova-ios/commit/4cd8467b
iOS passes all mobile-spec tests. Tagged 2.3.0
On Wed, Jan 2, 2013 at 5:06 PM, Filip Maj f...@adobe.com wrote:
Just automated the task creation in a script. I think its better to have
this option below (where 8 people waste 10 seconds each) rather than to
have one person spend 30+ minutes
Docs are done.
On Thu, Jan 3, 2013 at 7:06 PM, Shazron shaz...@gmail.com wrote:
iOS passes all mobile-spec tests. Tagged 2.3.0
On Wed, Jan 2, 2013 at 5:06 PM, Filip Maj f...@adobe.com wrote:
Just automated the task creation in a script. I think its better to have
this option below
[
https://issues.apache.org/jira/browse/CB-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13543501#comment-13543501
]
Michael Brooks commented on CB-2151:
[Commit
[
https://issues.apache.org/jira/browse/CB-2151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Brooks resolved CB-2151.
Resolution: Fixed
Tag Docs
Key: CB-2151
URL:
K, everything is tagged (incl. mobile-spec). All that's left is the source
gen! /me pokes Steve
On 1/3/13 5:20 PM, Michael Brooks mich...@michaelbrooks.ca wrote:
Docs are done.
On Thu, Jan 3, 2013 at 7:06 PM, Shazron shaz...@gmail.com wrote:
iOS passes all mobile-spec tests. Tagged 2.3.0
[
https://issues.apache.org/jira/browse/CB-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13543600#comment-13543600
]
Darryl Champagne commented on CB-1700:
--
If I remember correctly, after testing, the
[
https://issues.apache.org/jira/browse/CB-1700?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Darryl Champagne updated CB-1700:
-
Attachment: CameraExif.patch
Since the formatting was not preserved in the comment, here is the
65 matches
Mail list logo
