Yep, delete em.
On 22 October 2014 12:50, Andrew Grieve agri...@chromium.org wrote:
On Wed, Oct 22, 2014 at 12:52 PM, Josh Soref jso...@blackberry.com
wrote:
There are a number of branches in cordova-js.
I think there should be two kinds of branches:
1. Release branches (or tags that
I wonder how it solves the problems of serving the
correct version of cordova.js and cordova_plugin.js depending on the
version of the native code that is installed on the different versions of
the mobile App in production.
When you connect to the IP that's being served by connect-phonegap,
Should cordova-plugman be renamed to node?
- The cordova-plugman version returning node's version sounds like a bug.
It should be Plugman's NPM version number so far as I know.
Yep, Braden is correct. That is totally a bug. Filed here:
https://issues.apache.org/jira/browse/CB-6023
On 11
Howdy,
I think there are too many default engines defined.
for instance
engine name=cordova-android version==1.8.0 /
is essentially the same as
engine name=cordova version==1.8.0 platform=android /
Could someone remind the reason for having platform specific default
engine names? If
Ya the cordova serve command isn't working for me either.
Just did these steps:
npm install cordova -g
cordova create foo
cd foo
cordova platform add ios
cordova serve ios
// says it's now serving on http://0.0.0.0:8000/
// browse to localhost:8000
// see '404 Not Found'
On 12 November 2013
Hrm, looks like the version script is having trouble finding where the
www/cordova.js file is located. The issue is if you try calling the version
script from different levels of the cli created project, it won't be able
to resolve where the cordova.js file should be.
On 6 November 2013 13:10,
=694451fc702a9d700b9d9f7c6fc6e3e78da20b7d;hb=19cfe94a5a64379a4a3cd6cfaf2acaecb6d24671
On 6 November 2013 13:31, Tim Kim timki...@gmail.com wrote:
Hrm, looks like the version script is having trouble finding where the
www/cordova.js file is located. The issue is if you try calling the version
Howdy all,
I like Carlos' suggestions in this jira ticket for dealing with Windows
scripts:https://issues.apache.org/jira/browse/CB-5187
Appending a .bat or using cmd /c seem pretty easy fixes in this case. I'm
+1 either way.
I propose to think about 'cordova' engine settings (in
Hey David,
I just uploaded a patch that should hopefully things for ya. Let me know if
there are any more problems.
On 18 October 2013 18:51, Tim Kim timki...@gmail.com wrote:
Hrmmm. Shoot. Funny how a '.0' can paint you into a corner.
I'm not sure if there are any easy solutions
Woo!
On 21 October 2013 15:59, David Kemp drk...@google.com wrote:
Looks like it fixed it!
On Oct 21, 2013 4:40 PM, Tim Kim timki...@gmail.com wrote:
Hey David,
I just uploaded a patch that should hopefully things for ya. Let me know
if
there are any more problems.
On 18
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 string format detected
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
well. Not sure if that has any other side-effects.
On Fri, Oct 18, 2013 at 8:59 PM, Tim Kim timki...@gmail.com wrote:
Hey there David
works. I will post the blog here
On Sep 26, 2013 4:59 PM, Tim Kim timki...@gmail.com wrote:
You don't have access to this review request.
This review request is private. You must be a requested reviewer,
either
directly or on a requested group, and have permission to access
You don't have access to this review request.
This review request is private. You must be a requested reviewer, either
directly or on a requested group, and have permission to access the
repository in order to view this review request.
Ya, same here
On 26 September 2013 16:37, Shazron
Fil, I still remember the times we were up late at night hacking away on
CMPT assignments. You turned out to be a hell of a coder!
Enjoy Saucelabs!
On 30 August 2013 13:17, David Kemp drk...@google.com wrote:
Good Luck in your new endeavour!
On Fri, Aug 30, 2013 at 2:31 PM, Filip Maj
Hey gang,
I believe the good people at google were wanting to hack on plugin registry
but were unsure how to set it up. Here are some instructions to get this
ole bucket of bolts going:
How to get plugin registry going locally
1) Install couchdb:
at 3:07 PM, Filip Maj f...@adobe.com wrote:
Wiki page!
On 8/19/13 2:55 PM, Tim Kim timki...@gmail.com wrote:
Hey gang,
I believe the good people at google were wanting to hack on plugin
registry
but were unsure how to set it up. Here are some instructions to get this
ole bucket
And the wiki link: https://wiki.apache.org/cordova/PluginDiscovery
On 19 August 2013 16:13, Tim Kim timki...@gmail.com wrote:
Eh, it's in the wiki now. The problem with the readme is which project
should get it. And since the instructions involve piecing multiple
repos/tech together, I think
+1
On 14 August 2013 12:44, Filip Maj f...@adobe.com wrote:
Looks good to me!
On 8/14/13 11:49 AM, Andrew Grieve agri...@chromium.org wrote:
Ian's put together a wiki page on how to store version numbers in our
repos:
https://wiki.apache.org/cordova/PlatformVersionScripts
I'd like to
Ya, it does an engine/version check but only for cordova js - it currently
does nothing about the os/sdk versions of the platform you're deving for. I
was thinking about handling the check for os/sdk within the engine tag or
the platform tag in plugin.xml, but I think that the platform tag is
the
Hey gang,
I also need to make some function in DirectoryManager public for the file
api. We cool with that too?
The ones in question:
testFileExists
getFreeDiskSpace
testSaveLocationExists
Looking like we should definitely make DirectoryManager as a public api
now.
On 11 June 2013 12:51, Joe
Hey gang,
So I'm trying to rip out the android network plugin, but it appears the
android exec relies on the network plugin for online/offline events.
How is this not a problem for the rest of the platforms? That's the
first thing that I'm wondering right now.
I think ios' deviceready event also doesn't fire, but I'm not sure if it's
for the same reasons - haven't gone down that rabbit hole yet.
As for bb10, I'm not sure anymore since it
+1
It'd be nice to look up a particular discussion if you weren't in one.
On 1 June 2013 17:56, Filip Maj f...@adobe.com wrote:
The Infra guys posted about some new features they've worked on (the
git-JIRA commenting is one that Shaz already got working for us), and
there's one where we can
Congratulations, Grieve family!
On 31 May 2013 07:05, Bryan Higgins br...@bryanhiggins.net wrote:
Congrats!!!
On Fri, May 31, 2013 at 10:03 AM, Steven Gill stevengil...@gmail.com
wrote:
Congrats Andrew!!!
On Fri, May 31, 2013 at 7:00 AM, Andrew Grieve agri...@chromium.org
Hey gang,
So I'm working on the engine tag for plugman and I've come across a bit of
a problem. For those who don't know, the engine tag is for checking whether
a plugin needs a certain version of Cordova to work. It's one of the last
outstanding features for the plugman spec that has yet to be
@cordova.apache.org
Reply To: dev@cordova.apache.org
Subject: Re: Standardising How to Get Cordova Version in a Project
Why don't we defer to each platform how to read the version - return it
in
a script? kinda like bin/check_reqs
On Thu, May 2, 2013 at 2:18 PM, Tim Kim timki
Done and done.
On 19 April 2013 14:21, Filip Maj f...@adobe.com wrote:
Probably a retag since we use the contents of VERSION to interpolate the
framework version string into the JS-only platforms' JS.
On 4/19/13 2:16 PM, Tim Kim timki...@gmail.com wrote:
Hey gang,
I noticed
, nor master.
Am I going crazy or is there something else going on? :/
On Fri, Apr 19, 2013 at 2:34 PM, Tim Kim timki...@gmail.com wrote:
Done and done.
On 19 April 2013 14:21, Filip Maj f...@adobe.com wrote:
Probably a retag since we use the contents of VERSION to interpolate
NOOO
On 19 April 2013 17:15, Shazron shaz...@gmail.com wrote:
You checked in merge conflicts. e.g.
+ HEAD
2.5.0
+===
+2.7.0rc1
+
On Fri, Apr 19, 2013 at 5:14 PM, Tim Kim timki...@gmail.com wrote:
Ok, it should be good to go now.
On 19 April 2013 16:59, Shazron shaz
the right section. If
you gtg I can take care of it
On Fri, Apr 19, 2013 at 5:24 PM, Jesse purplecabb...@gmail.com wrote:
Hurry! It's Friday.
@purplecabbage
risingj.com
On Fri, Apr 19, 2013 at 5:19 PM, Tim Kim timki...@gmail.com wrote:
NOOO
On 19
Braden I have merged master and the future branch:
https://github.com/timkim/plugman/tree/future_master_merge
I think it's about ready to merge back in to future. I've gotten the
android-one-install and the ios-config-xml-install (minus one weird test I
don't understand) working.
On 10 April
Awesome!
On 6 April 2013 08:16, Ken Wallis kwal...@blackberry.com wrote:
So awesome to see this go live, thanks Bryan. Looking forward to seeing
progress towards this being merged into the Apache repos!
Sent from my BlackBerry Z10 smartphone.
From: Bryan Higgins
Sent: Saturday, April 6,
Hey Braden,
I'm working on getting the plugman future branch tests running and I
noticed a couple of things:
1) Removal of moving the assets to the www/:
https://git-wip-us.apache.org/repos/asf?p=cordova-plugman.git;a=commit;h=eeb5f0104f449ae5cac6045786874559fe1edf50
Are we not doing this
Hrm, not sure. I'll have to check on monday on device.
On 23 March 2013 11:11, Andrew Grieve agri...@google.com wrote:
bump
On Wed, Mar 20, 2013 at 4:16 PM, Andrew Grieve agri...@google.com wrote:
The docs:
Speaking of logos, I was planning on making another 8 bit sticker for the
next PhoneGap day. The PlugMan character is still in the works :D
[image: Inline images 1]
+1 for the future md as well. It looks great.
I'm also working on a branch of cordova cli trying to get it integrating
with plugman
+1
However, I think we may need a better property/value pair name than
just cordova_version:
plugin_versions. This is because I feel like there is a implicit idea that
this particular plugin will work on a specific version of Cordova, but for
all platforms. Whereas in reality, most of the plugins
I agree with the BlackBerry scripts must do. Most of the BlackBerry stuff
should be pretty simple. If you took all the existing ant commands and
what's in the cordova scripts already, you're most of the way there.
However, I'm not sure what log would look like. I think there's a way to
ssh your
Ya I do pretty much that same thing that Fil does but for BlackBerry. I'm
not sure where the speed up would be for the BlackBerry side.
On 26 February 2013 13:18, Filip Maj f...@adobe.com wrote:
I copy over the built cordova.xxx.js file to my project www/ folder as
cordova.js and overwrite
I've tagged BlackBerry but the media tests still crash the mobile spec auto
test. Not much we can do about this right now since we're still waiting on
BlackBerry to get back to us on this issue:
https://github.com/blackberry/BB10-WebWorks-Framework/issues/606
It also might be the case that this
I don't mind either way, but I think we should have at least an idea what
the cordova-blackberry10 repo should look like before we create it.
To separate them right now would mean creating two very similar
cordova-blackberry repos (everything the same except some build scripts).
And then later on,
On 2013-02-12, at 9:36 AM, Brian LeRoux b...@brian.io wrote:
Ah crap. Well, my thinking is just repackage it anyhow. (Not a world
ending bug tracking nightmare.)
On Mon, Feb 11, 2013 at 11:40 PM, Tim Kim timki...@gmail.com wrote:
Someone had brought it up through the google groups
Hey gang,
So it appears I forgot to push out a commit to update the version number
in the BlackBerry repo, but accidently tagged 2.4.0 anyways. Should I force
re-tag the repo?
Also, the download on phonegap.com for the BlackBerry repo was kinda messed
up anyways. In that the robson tool didn't
[
https://issues.apache.org/jira/browse/CB-2355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13571072#comment-13571072
]
Tim Kim commented on CB-2355:
-
https://git-wip-us.apache.org/repos/asf?p=cordova-blackberry.git
[
https://issues.apache.org/jira/browse/CB-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13569031#comment-13569031
]
Tim Kim commented on CB-2300:
-
Fixed here:
https://git-wip-us.apache.org/repos/asf?p=cordova
[
https://issues.apache.org/jira/browse/CB-2300?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Kim resolved CB-2300.
-
Resolution: Fixed
./bin/create script for BlackBerry should employ parameters consistent with
other
[
https://issues.apache.org/jira/browse/CB-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13569116#comment-13569116
]
Tim Kim commented on CB-2287:
-
I made some updates to the JS. This fixes some but not all
[
https://issues.apache.org/jira/browse/CB-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13569132#comment-13569132
]
Tim Kim commented on CB-2287:
-
Ok, it's in there now.
https://git-wip-us.apache.org/repos/asf?p
[
https://issues.apache.org/jira/browse/CB-2205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Kim reassigned CB-2205:
---
Assignee: Filip Maj (was: Tim Kim)
adding Blackberry platform throws an error -- running cordova-client
[
https://issues.apache.org/jira/browse/CB-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13566919#comment-13566919
]
Tim Kim commented on CB-2287:
-
I got Gord to help raise an issue on github/irc:
https
[
https://issues.apache.org/jira/browse/CB-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13565954#comment-13565954
]
Tim Kim commented on CB-2287:
-
Ok, I managed to get about all but three tests passing
[
https://issues.apache.org/jira/browse/CB-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13564654#comment-13564654
]
Tim Kim commented on CB-2287:
-
Ok, so it looks like the problem has to do with a few really
[
https://issues.apache.org/jira/browse/CB-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13560176#comment-13560176
]
Tim Kim commented on CB-2287:
-
I think it's due to the Media section. I just tried running each
[
https://issues.apache.org/jira/browse/CB-2287?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13560194#comment-13560194
]
Tim Kim commented on CB-2287:
-
Hrm, I was playing around in web inspector and did g = new Media
The relevant bug for it is here:
https://issues.apache.org/jira/browse/CB-2167
There are sub-bugs for BB and WP. Not sure if anyone has the intention of
addressing this for this release?
I've been busy working on some plugman stuff so I won't be able to get to
the BB one for this release.
[
https://issues.apache.org/jira/browse/CB-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Kim resolved CB-2247.
-
Resolution: Fixed
Update JavaScript for BlackBerry
Key: CB
[
https://issues.apache.org/jira/browse/CB-2247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13559264#comment-13559264
]
Tim Kim commented on CB-2247:
-
Fixed here:
https://git-wip-us.apache.org/repos/asf?p=cordova
[
https://issues.apache.org/jira/browse/CB-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13559267#comment-13559267
]
Tim Kim commented on CB-2257:
-
Fixed here:
https://git-wip-us.apache.org/repos/asf?p=cordova
[
https://issues.apache.org/jira/browse/CB-2257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Kim resolved CB-2257.
-
Resolution: Fixed
Tag BlackBerry
--
Key: CB-2257
URL: https
[
https://issues.apache.org/jira/browse/CB-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13547354#comment-13547354
]
Tim Kim commented on CB-1868:
-
Apparently this was done quite some time ago in this commit:
https
[
https://issues.apache.org/jira/browse/CB-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Kim resolved CB-1868.
-
Resolution: Fixed
bb min reqs
---
Key: CB-1868
URL: https
[
https://issues.apache.org/jira/browse/CB-1283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13547406#comment-13547406
]
Tim Kim commented on CB-1283:
-
Doing some gardening here and setting this to closed until
[
https://issues.apache.org/jira/browse/CB-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13547416#comment-13547416
]
Tim Kim commented on CB-1251:
-
The api needed to get contacts still hasn't been exposed. Setting
[
https://issues.apache.org/jira/browse/CB-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Kim resolved CB-1251.
-
Resolution: Unresolved
Create Contacts Api for Playbook
I ran it. I think I forgot to to post to that 2.3.0 thread that I did.
On 4 January 2013 07:13, Marcel Kinard cmarc...@gmail.com wrote:
Just curious, did someone run mobile-spec on BB for 2.3.0? Drew wasn't
able to get to that task.
-- Marcel Kinard
--
Timothy Kim
[
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: CB
[
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
[
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://git-wip-us.apache.org/repos/asf?p=cordova
Tim Kim created CB-2105:
---
Summary: Mis-linked getting started guide for BlackBerry
Key: CB-2105
URL: https://issues.apache.org/jira/browse/CB-2105
Project: Apache Cordova
Issue Type: Bug
[
https://issues.apache.org/jira/browse/CB-2105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13542322#comment-13542322
]
Tim Kim commented on CB-2105:
-
A minor spelling change changed the link to the getting started
Thanks for the catch, Becky! Should be fixed now.
On 2 January 2013 11:26, Ken Wallis kwal...@rim.com wrote:
Confirmed, 'BlackBerry'
--
Ken Wallis
Product Manager – BlackBerry WebWorks
Research In Motion
(905) 629-4746 x14369
From: Filip Maj
Oh - I created one already and fixed it. Do we actually need to rename the
directory? I thought we just needed the list of headers in this file
docs/en/edge/guide/getting-started/index.md needed to match the new
spelling change.
On 2 January 2013 11:29, Becky Gibson gibson.be...@gmail.com wrote:
Ok cool :)
On 2 January 2013 11:45, Becky Gibson gibson.be...@gmail.com wrote:
Whatever works! I always forget how the docs magic works until I have to
make a change. Thanks.
On Wed, Jan 2, 2013 at 2:37 PM, Tim Kim timki...@gmail.com wrote:
Oh - I created one already and fixed it. Do
I couldn't resist.
http://qkme.me/3sew80
On 2 January 2013 11:56, Filip Maj f...@adobe.com wrote:
I am working out some kinks in a script I am putting together to create
the JIRa issues for tagging a release (instead of spending ~20 mins every
release manually doing that).
Therefore,
[
https://issues.apache.org/jira/browse/CB-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13542565#comment-13542565
]
Tim Kim commented on CB-2106:
-
This is a clone of this issue which has been resolved.
https
[
https://issues.apache.org/jira/browse/CB-2106?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Kim resolved CB-2106.
-
Resolution: Duplicate
BlackBerry Getting Started link broken
[
https://issues.apache.org/jira/browse/CB-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13532708#comment-13532708
]
Tim Kim commented on CB-1987:
-
Fixed here:
https://git-wip-us.apache.org/repos/asf?p=cordova
[
https://issues.apache.org/jira/browse/CB-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Kim resolved CB-1987.
-
Resolution: Fixed
Update JavaScript for BlackBerry
Key: CB
[
https://issues.apache.org/jira/browse/CB-1996?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13532711#comment-13532711
]
Tim Kim commented on CB-1996:
-
Fixed here:
https://git-wip-us.apache.org/repos/asf?p=cordova
[
https://issues.apache.org/jira/browse/CB-1996?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Kim resolved CB-1996.
-
Resolution: Fixed
Update www/ Application for BlackBerry
[
https://issues.apache.org/jira/browse/CB-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13532712#comment-13532712
]
Tim Kim commented on CB-2005:
-
Fixed here:
https://git-wip-us.apache.org/repos/asf?p=cordova
[
https://issues.apache.org/jira/browse/CB-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Kim resolved CB-2005.
-
Resolution: Fixed
Tag BlackBerry
--
Key: CB-2005
URL: https
tests failing, as explained in
another thread)
On Thu, Dec 13, 2012 at 5:21 PM, Tim Kim timki...@gmail.com wrote:
I'm also running into some errors with bb10 and discussing some webworks
trouble shooting with RIM.
On 13 December 2012 17:13, Shazron shaz...@gmail.com wrote:
See
[
https://issues.apache.org/jira/browse/CB-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13510644#comment-13510644
]
Tim Kim commented on CB-1954:
-
Hey Julien,
The fix should be in the next rc release which I
On 3 December 2012 18:05, Nukul Bhasin m...@nukulb.com wrote:
you will need the OS update, we broke compatibility :(
but it was necessary
Ah, no worries. That's what beta is for :)
Works now!
--
Timothy Kim
[
https://issues.apache.org/jira/browse/CB-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Kim resolved CB-1853.
-
Resolution: Fixed
Add device.model to the Device API
--
Key
[
https://issues.apache.org/jira/browse/CB-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13510212#comment-13510212
]
Tim Kim commented on CB-1954:
-
Hey there,
Thanks for filing the ticket. I've a fix here:
https
[
https://issues.apache.org/jira/browse/CB-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13510213#comment-13510213
]
Tim Kim commented on CB-1874:
-
Hey there,
That's because the set custom headers were
[
https://issues.apache.org/jira/browse/CB-1954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Kim resolved CB-1954.
-
Resolution: Fixed
Header support for PhoneGap's FileTransfer (Upload
[
https://issues.apache.org/jira/browse/CB-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Kim resolved CB-1874.
-
Resolution: Fixed
On my BlackBerry 9300, when i use API fileTransfer.Upload, headers are
ingnored
Oh sorry, I thought you were talking about something else. My mistake!
On 3 December 2012 10:42, Josh Soref jso...@rim.com wrote:
Tim Kim wrote:
Is it?
I keep seeing questions being popped up about people looking for
webworks.js
even if they developing for bb5-7/playbook.
Usually
Oh wait, realised it was an OS update as well. Let me update that and see
if that works!
On 3 December 2012 17:08, Tim Kim timki...@gmail.com wrote:
Hey Gord,
I'm getting some weird errors trying to launch an app on bb10 with the new
sdk. The first time I make an app, it installs onto
Thanks for the heads up, Gord!
On 30 November 2012 07:40, Gord Tanner gtan...@gmail.com wrote:
The BlackBerry 10 SDK and OS versions were updated this week, this
broke compatibility the previous SDK. Until BlackBerry 10 is released we
will have to keep on the bleeding edge to ensure device
[
https://issues.apache.org/jira/browse/CB-1953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13506135#comment-13506135
]
Tim Kim commented on CB-1953:
-
It appears that this change was the culprit:
https://git-wip
[
https://issues.apache.org/jira/browse/CB-1909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13505016#comment-13505016
]
Tim Kim commented on CB-1909:
-
https://git-wip-us.apache.org/repos/asf?p=cordova-blackberry.git
[
https://issues.apache.org/jira/browse/CB-1909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Kim resolved CB-1909.
-
Resolution: Fixed
Update www/ Application for BlackBerry
[
https://issues.apache.org/jira/browse/CB-1918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Kim resolved CB-1918.
-
Resolution: Fixed
Tag BlackBerry
--
Key: CB-1918
URL: https
[
https://issues.apache.org/jira/browse/CB-1370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13505052#comment-13505052
]
Tim Kim commented on CB-1370:
-
I'm going to be closing this issue. The issues with geolocation
I am running into some issues with the js for bb playbook. I'm still trying
to wrap my head around this, but it appears that the requestFileSystem
object isn't being clobbered by the blackberry/plugin/air/requestFileSystem
one. It instead loads the common one and tried to exec which causes it to
[
https://issues.apache.org/jira/browse/CB-1900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13504214#comment-13504214
]
Tim Kim commented on CB-1900:
-
Updated javascript:
https://git-wip-us.apache.org/repos/asf?p
1 - 100 of 120 matches
Mail list logo
