File IO Encoding and Performance iOS
-
Key: CB-390
URL: https://issues.apache.org/jira/browse/CB-390
Project: Apache Callback
Issue Type: Bug
Components: iOS
Affects Versions: 1.5.0
[
https://issues.apache.org/jira/browse/CB-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lee Crossley updated CB-390:
Description: The performance of the Apache Callback / Cordova file IO
operations on iOS is causing problems
navigator.camera.getPicture() crashing on iOS after memory warning
--
Key: CB-391
URL: https://issues.apache.org/jira/browse/CB-391
Project: Apache Callback
Issue Type: Bug
[
https://issues.apache.org/jira/browse/CB-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Richard Kimber updated CB-391:
--
Description:
getPicture has become very unstable on previously working code, affecting both
Phonegap
android show/hidekeyboar events not triggered when fullscreen app
-
Key: CB-392
URL: https://issues.apache.org/jira/browse/CB-392
Project: Apache Callback
Issue Type: Bug
[
https://issues.apache.org/jira/browse/CB-330?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13239486#comment-13239486
]
Paul DeFalco commented on CB-330:
-
I was having trouble with trying to add a column to a table
Gord, any update on the status of Playbook?
On Thu, Mar 22, 2012 at 2:07 PM, gtan...@gmail.com wrote:
Also: tested the battery events on the playbook and they are working fine!
I would like to get this into master before the reorg happens.
Sent on the TELUS Mobility network with BlackBerry
Loading it on the playbook as we speak.
My event went late last night so gonna hack on this today
Sent on the TELUS Mobility network with BlackBerry
-Original Message-
From: Drew Walters deedu...@gmail.com
Date: Tue, 27 Mar 2012 09:32:42
To: callback-dev@incubator.apache.org;
Filetransfer boundary is broken without parameter.
--
Key: CB-393
URL: https://issues.apache.org/jira/browse/CB-393
Project: Apache Callback
Issue Type: Bug
Components: WP7
Hi Bryce,
Updating the guides of each platform should (ideally) be handled by each
platform's developers. Each JIRA issue should have a component for the
related platform. Learning from 1.5.0, we need to have these guides solid
before the 1.6.0 release.
Renaming of the assets is a very important
[
https://issues.apache.org/jira/browse/CB-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13239565#comment-13239565
]
Patrick Mueller commented on CB-388:
copied from
the open src docs def need to name cordova; the word phonegap has g2g
the phonegap dist, of course, is free to do whatever it wants. for
now, I can tell you, that dist is a blind straight copy of cordova
with a different pkg name and for the forseeable future it shall stay
way
lets not solve any
Only tricky part with renaming is in the guides we often reference
where to download (phonegap.com) and sometimes reference the phonegap
wiki. Hopefully we'll have an Apache hosted spot for download soon.
I'm tempted to remove references to the phonegap wiki.
FYI, I did take a stab at updating
from the W3C newsletter:
The Media Capture API Note Published
22 March 2012 | Archive
http://www.w3.org/News/2012#entry-9394
The Device APIs Working Group has published a Group Note of
The Media Capture API. This specification defined an
Application Programming Interface (API)
[
https://issues.apache.org/jira/browse/CB-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13239797#comment-13239797
]
Tim Kim commented on CB-303:
Hey there,
The updated guide looks pretty good so far but you may
I think image is just part of video (one frame of the video stream).
If you take a look at: http://www.w3.org/TR/2011/WD-webrtc-20111027/
and search for photo on the page, it looks like that is the intent.
Prob it works like this - when taking a photo, the video stream is
dumped to the canvas,
[
https://issues.apache.org/jira/browse/CB-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13239821#comment-13239821
]
Tim Kim commented on CB-303:
Oh ya,
5) The sdks also need Adobe Air to complete the install so
Yeah, we're behind there and battery. Probably others. I think the
plugins arch gives us a nice path to keep on top of this and
centralizes the problems to a place wherein anyone in the community
can pitch in to help.
On Tue, Mar 27, 2012 at 11:35 AM, Shazron shaz...@gmail.com wrote:
I think
I've done a replace PhoneGap with Cordova in APIs/samples/docs. Since some
images have PhoneGap in the captured image, and links still point to
PhoneGap site, I mention that Cordova used to be called PhoneGap - but
that's only in the user guides intro paragraph.
The content of the guides will
Hey
I've been working on the CordovaWebView branch, and I think we need to
discuss where to put the CallbackServer and PluginManager in the new
implementation. I'm OK with it being in the view, but I did have it in the
Client before, and I'm wondering what people's thoughts are on that. Also,
kill https://github.com/cordova/cordova-windows-phone
-
Key: CB-394
URL: https://issues.apache.org/jira/browse/CB-394
Project: Apache Callback
Issue Type: Task
Affects Versions: 1.6.0
kill https://github.com/cordova/cordova-bada
Key: CB-395
URL: https://issues.apache.org/jira/browse/CB-395
Project: Apache Callback
Issue Type: Task
Components: Bada
Affects
kill https://github.com/callback/callback-android
-
Key: CB-397
URL: https://issues.apache.org/jira/browse/CB-397
Project: Apache Callback
Issue Type: Task
Components: Android
[
https://issues.apache.org/jira/browse/CB-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brian LeRoux updated CB-398:
Description: ensure the apache mirror is up-to-date then kel it
Priority: Minor (was:
[
https://issues.apache.org/jira/browse/CB-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse MacFadyen resolved CB-394.
Resolution: Fixed
kill https://github.com/cordova/cordova-windows-phone
[
https://issues.apache.org/jira/browse/CB-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse MacFadyen reassigned CB-338:
--
Assignee: Sergey Grebnov (was: Jesse MacFadyen)
Online and Offline Events are not fired
[
https://issues.apache.org/jira/browse/CB-393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse MacFadyen reassigned CB-393:
--
Assignee: Sergey Grebnov (was: Jesse MacFadyen)
Filetransfer boundary is broken without
[
https://issues.apache.org/jira/browse/CB-337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse MacFadyen reassigned CB-337:
--
Assignee: Sergey Grebnov (was: Jesse MacFadyen)
Optional parameter behavior change in
[
https://issues.apache.org/jira/browse/CB-336?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse MacFadyen reassigned CB-336:
--
Assignee: Sergey Grebnov (was: Jesse MacFadyen)
Mediafile.getFormatData hits error call back
[
https://issues.apache.org/jira/browse/CB-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse MacFadyen resolved CB-358.
Resolution: Fixed
Need Notice file
Key: CB-358
The big theme this year has been migration to an architecture more
friendly to plugins with our ultimate goal of the end user being able
to compose their own version of Cordova with only the APIs they need.
Essentially our release would slowly strip down to webview+bridge and
then we'd maintain an
Thanks Fil - I'm all for fixing geolocation in iOS. There's several
jira issues for it, and I've been attempting to fix it as best I can,
but users are still reporting problems with it since it doesn't match
the native implementation of UIWebView.
On Mon, Mar 26, 2012 at 4:00 PM, Filip Maj
Add to 1.6-1.7
- More focus on docs, guides, examples, maybe native plugin API
- Advanced notice of what's planned to be deprecated and when, then get
community feedback before breaking compatibility
1.7
- CordovaView (Android)
1.6-2.x
- Emphasize testing to ensure no regression.
-
Ok, so I thought I had a process for committing to Apache git that works.
But, since I can't seem to cleanly submit to the mobile-spec repo I am
going to publicly admit my ignorance and ask for clarification.
My local clone of mobile spec was a mess so I created it again.
I cloned my fork of
[
https://issues.apache.org/jira/browse/CB-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joe Bowser resolved CB-397.
---
Resolution: Fixed
IT'S DEAD JIM!
kill https://github.com/callback/callback-android
[
https://issues.apache.org/jira/browse/CB-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse MacFadyen updated CB-112:
---
Fix Version/s: 1.7.0
Touch event support
---
Key: CB-112
[
https://issues.apache.org/jira/browse/CB-339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse MacFadyen updated CB-339:
---
Fix Version/s: 1.7.0
Able to create directory/file without parent directory
[
https://issues.apache.org/jira/browse/CB-112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse MacFadyen updated CB-112:
---
Fix Version/s: (was: 1.6.0)
Touch event support
---
Key:
[
https://issues.apache.org/jira/browse/CB-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse MacFadyen updated CB-289:
---
Fix Version/s: 1.7.0
Supress zoom and scroll in WP7
--
[
https://issues.apache.org/jira/browse/CB-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse MacFadyen updated CB-289:
---
Fix Version/s: (was: 1.6.0)
Supress zoom and scroll in WP7
--
[
https://issues.apache.org/jira/browse/CB-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse MacFadyen updated CB-111:
---
Fix Version/s: (was: 1.6.0)
Zoom and elastic pull effect
Assuming that the native WebView implementations across whatever platforms
adhere to the W3C Geo spec, then these native changes would line up our
implementation with what users are expecting in their browser.
I can help with tweaking the implementation on iOS, but would love if you
could
[
https://issues.apache.org/jira/browse/CB-334?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse MacFadyen updated CB-334:
---
Fix Version/s: (was: 1.6.0)
1.7.0
Nick Name Value change error when creating
[
https://issues.apache.org/jira/browse/CB-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse MacFadyen resolved CB-376.
Resolution: Unresolved
Currently it is not possible to remove the grey box in the IE9 WebBrowser
[
https://issues.apache.org/jira/browse/CB-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse MacFadyen updated CB-376:
---
Fix Version/s: (was: 1.6.0)
Selecting an element shows a grey-box
[
https://issues.apache.org/jira/browse/CB-335?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse MacFadyen updated CB-335:
---
Fix Version/s: (was: 1.6.0)
1.7.0
accelerometerOptions parameter ignores
Bryce you think we start moving to monthly sprints or just take on
less each sprint?
I'd rather we kept the release train style though perhaps move to odd
numbers fix bugs and even numbers are new features... though in the
case of other projects I rarely see this actually work as advertised.
On
Just wondering how we are handling copyright notices?
For example if a contributor wrote an API for Cordova and his employer's legal
department wants to him to include a copyright notice on the files. Does the
copyright notice go in the LICENSE or NOTICE file in the root or does it go
Yes, a merge commit is correct and expected behavior following a merge. It
is unlike a standard commit in that it has TWO parent commits.
This is why, as fellow PhoneGap hacker Andrew Lunny once said, merge
commits are for people who drink blended whiskey and listen to
Nickelback. No offense to
This one's pretty good too
http://blog.experimentalworks.net/2009/03/merge-vs-rebase-a-deep-dive-into-
the-mysteries-of-revision-control/
On 3/27/12 3:20 PM, Filip Maj f...@adobe.com wrote:
Yes, a merge commit is correct and expected behavior following a merge. It
is unlike a standard commit in
[
https://issues.apache.org/jira/browse/CB-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13240013#comment-13240013
]
Gopinath M.R. commented on CB-303:
--
One of the tricky part of Blackberry I struggled to get
Apple should be following W3C, although I don't know if they fixed
this bug yet, it's still unresolved for me in Radar:
http://openradar.appspot.com/radar?id=1160403 but based on what my
test on 5.1, they've fixed it.
Sure ping me on email/jabber let's set up a time.
On Tue, Mar 27, 2012 at 3:07
According to this: http://www.apache.org/legal/src-headers.html
1. If the source file is submitted with a copyright notice included in
it, the copyright owner (or owner's agent) must either:
1. remove such notices, or
2. move them to the NOTICE file associated with each applicable
project
Great overview Brian. Thanks for that!
I'd like to keep the short sprints going with the following focus points:
- take on less each sprint
- one project-wide milestone (movement towards an improved plugin
structure)
- one platform-specific milestone (adding new OS support, etc)
-
[
https://issues.apache.org/jira/browse/CB-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13240046#comment-13240046
]
Michael Brooks commented on CB-303:
---
*Gophinath M.R.:* Good catch. I've never experienced
Update BlackBerry Plugin Wiki article with warning of filename case-sensitivity
---
Key: CB-400
URL: https://issues.apache.org/jira/browse/CB-400
Project: Apache Callback
[
https://issues.apache.org/jira/browse/CB-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13240051#comment-13240051
]
Tim Kim commented on CB-303:
Ya sure. Also, if I remember correctly BB does not like special
In the recent past, releases have been about monthly - which was beneficial
to get fixes out to the community. However, this frequency seemed to take
precedence over getting larger changes completed and tested (lesson learned
from 1.5.0). For releases of substantial changes, it is better for the
[
https://issues.apache.org/jira/browse/CB-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13240053#comment-13240053
]
Filip Maj commented on CB-388:
--
Pat, let's start aggregating this thinking into a wiki article
Was gonna take a look at this today but looks like it's already merged :)
Thanks Becky! I love tests!
On 3/21/12 5:01 PM, Becky Gibson gibson.be...@gmail.com wrote:
I updated the automated media tests to try and play an invalid file name.
This checks that an appropriate error with the
Crash on iOS when taking multiple pictures
--
Key: CB-401
URL: https://issues.apache.org/jira/browse/CB-401
Project: Apache Callback
Issue Type: Bug
Components: iOS
Affects Versions:
[
https://issues.apache.org/jira/browse/CB-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Filip Maj updated CB-346:
-
Assignee: Filip Maj (was: Joe Bowser)
Contact find() should have sorting
--
[
https://issues.apache.org/jira/browse/CB-346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Filip Maj updated CB-346:
-
Component/s: (was: WP7)
(was: BlackBerry)
(was: Android)
I am going to assume then that will be merged in and we'll be making the
necessary native tweaks across the platforms we want to support.
ANDROID peeps: should we axe native geo code, or should we keep it around
and thus update the implementation to follow this new approach?
On 3/27/12 3:33 PM,
We should axe it/move it to its own plugins repo. Someone may want it, but
I don't want to make promises for it.
On Tue, Mar 27, 2012 at 4:55 PM, Filip Maj f...@adobe.com wrote:
I am going to assume then that will be merged in and we'll be making the
necessary native tweaks across the
I'd like time for testing, esp. creating a checklist so we don't
forget what needs to be updated each release - like getting started
guides, etc. For example if a platform maintainer is away, things
might get missed.
On Tue, Mar 27, 2012 at 4:22 PM, Bryce Curtis curtis.br...@gmail.com wrote:
In
So we'll keep it around (even though we won't override the implementation
that we get for free in the WebView), and thus we'll need to update the
native implementation. Gotcha. I will update the JIRA issue as such then.
On 3/27/12 4:57 PM, Joe Bowser bows...@gmail.com wrote:
We should axe
I would love a checklist like that! How about dropping in another section
to our CuttingReleases wiki article, I.e. Maintainer checklist before
cutting a release?
On 3/27/12 4:57 PM, Shazron shaz...@gmail.com wrote:
I'd like time for testing, esp. creating a checklist so we don't
forget what
[
https://issues.apache.org/jira/browse/CB-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Filip Maj updated CB-359:
-
Component/s: (was: CordovaJS)
webOS
iOS
Android
JavaScript +
[
https://issues.apache.org/jira/browse/CB-179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Filip Maj updated CB-179:
-
Component/s: webOS
Tagged webOS for integration.
Unified JavaScript project
Improve Contacts search taking a long time by using
(NSArray*)filteredArrayUsingPredicate:(NSPredicate*)predicate
-
Key: CB-402
URL:
[
https://issues.apache.org/jira/browse/CB-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13240079#comment-13240079
]
Shazron Abdullah commented on CB-402:
-
Predicate Programming Guide:
[
https://issues.apache.org/jira/browse/CB-388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13240102#comment-13240102
]
Patrick Mueller commented on CB-388:
It would be more useful to aggregate the thinking
73 matches
Mail list logo
