Return-Path: X-Original-To: apmail-cordova-dev-archive@www.apache.org Delivered-To: apmail-cordova-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 44FEA10698 for ; Sat, 27 Jul 2013 02:45:11 +0000 (UTC) Received: (qmail 29832 invoked by uid 500); 27 Jul 2013 02:45:11 -0000 Delivered-To: apmail-cordova-dev-archive@cordova.apache.org Received: (qmail 29596 invoked by uid 500); 27 Jul 2013 02:45:10 -0000 Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cordova.apache.org Delivered-To: mailing list dev@cordova.apache.org Received: (qmail 29588 invoked by uid 99); 27 Jul 2013 02:45:09 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 27 Jul 2013 02:45:09 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mattlantz@gmail.com designates 209.85.128.50 as permitted sender) Received: from [209.85.128.50] (HELO mail-qe0-f50.google.com) (209.85.128.50) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 27 Jul 2013 02:45:03 +0000 Received: by mail-qe0-f50.google.com with SMTP id q19so480181qeb.9 for ; Fri, 26 Jul 2013 19:44:42 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:references:from:content-type:x-mailer:in-reply-to :message-id:date:to:content-transfer-encoding:mime-version; bh=DnyztEBxOlRzPjaiduQqSGzf+5wio/mTgrJajnt4zA0=; b=PK97KGrsXCuK0kvDGwid9GoNEfuwWGg51a3SkYT9J+TnkfjcFeSmGuAzxnW69RHYoc RcWDNiU3PIKgob9CxWM8pMilgBTagbNzzWkzL2YXWoF55d8fw8keyZAN1mAKBkQbe81M URRBLItzMQc0zlWwCdtmrucm2Zqj0fdZ0upMIWHyEwq3V/ZDuuddl9hJsYdUb+p8flKB keA/wGrkgxCeWKVyofTIVyF7xJOkzsmGI1fXRCOpDnOFh6Zi9ndNVAptAPY3GWKzu4BQ fB3FQJFDjPadMcZRarL9/S/iXYnACnJNMh69bFvlrsnQTm0XAA3UCusS6RNrRrkOL29u QgJQ== X-Received: by 10.224.163.16 with SMTP id y16mr18550388qax.54.1374893082459; Fri, 26 Jul 2013 19:44:42 -0700 (PDT) Received: from [192.168.0.11] (CPE0026f3219790-CM0026f321978d.cpe.net.cable.rogers.com. [99.236.231.186]) by mx.google.com with ESMTPSA id l15sm4486845qav.13.2013.07.26.19.44.41 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Fri, 26 Jul 2013 19:44:41 -0700 (PDT) Subject: Re: BlackBerry Doc Issues References: From: "M. Lantz" Content-Type: text/plain; charset=us-ascii X-Mailer: iPhone Mail (10B329) In-Reply-To: Message-Id: <68C5CE12-BAE8-4D66-AE69-A29D86376379@gmail.com> Date: Fri, 26 Jul 2013 22:44:42 -0400 To: "dev@cordova.apache.org" Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (1.0) X-Virus-Checked: Checked by ClamAV on apache.org Sure thing fil. Ill look at the code too. My schedule is starting to look li= ghter so I can look at what I can bite off.=20 M. Lantz On 2013-07-26, at 8:29 PM, Filip Maj wrote: > Can you file issues in cordova for that Matteh? >=20 > On 7/26/13 11:27 AM, "Matt Lantz" wrote: >=20 >> I noticed a bunch of those doc update awesome! >>=20 >> I found another issue, on blackberry at least, not sure if anyone is >> looking at this but the navigator.notification.vibrate doesn't work. It >> appears that vibrate now belongs to navigator not notification. >>=20 >> Also having trouble with beep() >>=20 >> On 26 July, 2013 at 1:56:30 PM, Bryan Higgins (bryan@bryanhiggins.net) >> wrote: >>=20 >> There are some docs issues which are causing a lot of frustration for BB1= 0 >>=20 >> users of Cordova . The most severe being that the platform name in the >> docs >>=20 >> is "blackberry" rather than "blackberry10" [1]. >>=20 >>=20 >> There were also two merge commits [2] which blew away a bunch of >>=20 >> enhancements to the platform guide and our instructions to add NDK tools >> to >>=20 >> PATH. I think this needs more attention as it appears to affect other >>=20 >> platforms as well. >>=20 >>=20 >> Once these have been resolved, is it possible to re-spin a build of docs >>=20 >> for 3.0.0? >>=20 >>=20 >> [1] https://issues.apache.org/jira/browse/CB-4327 >>=20 >>=20 >> [2] https://issues.apache.org/jira/browse/CB-4347 >>=20 >>=20 >> Thanks, >>=20 >> Bryan >=20