FYI, I added support for download to BB.
On Tue, Dec 13, 2011 at 9:29 AM, Simon MacDonald <simon.macdon...@gmail.com> wrote: > I don't think we should publicize the download functionality of > FIleTransfer until it is supported on BB and Windows. Plus it needs to > be added to the docs as well. > > Simon Mac Donald > http://hi.im/simonmacdonald > > > > On Tue, Dec 13, 2011 at 5:52 AM, Steven Gill <stev...@adobe.com> wrote: >> Tagged Symbian, webOS and Bada to 1.3.0rc2. Just missing iOS and PG-docs >> now. I believe this means we are in the code freeze/testing process and >> are on schedule to release this Friday! >> >> Thanks to the commit logs + Shaz & Jesse, I have compiled a change log I >> will include when I package up 1.3. Take a quick read through and feel >> free to add/change anything. >> >> I am also going to be updating >> http://wiki.phonegap.com/w/page/28291160/roadmap-planning and going to try >> and make it the de-facto place for what features are coming in future >> releases. If anyone wants to help out, feel free to jump in. Great way to >> get involved in the project even if you are not working on the source code. >> >> -Steve >> >> General >> * PhoneGap issue tracker moved to https://issues.apache.org/jira/browse/CB >> * Callback being renamed to Cordova >> >> Blackberry >> * Added support for Playbook >> * Updated PluginResult Exceptions to use latest naming scheme. >> * Fixed a memory leak issue with WebWorks >> * Added Lifecycle changes and app.js functionalitly >> * Added activity and progress notification functionality >> >> Android >> * Added download method to filetransfer >> * made getEntry of FileUtils public in order to avoid duplicate code in >> FileTransfer >> * FileTransfer returns JSONObject with code, source and target for upload >> and download >> * Fix for CB-17: WebView caching resized pictures >> * Fix for issue #281 of phonegap/phonegap-android: Detect for >> localStorage if Java has disabled it >> * Fix for phonegap-android issue #261: Wrong application scale >> * Fix for Issue #33: onReceivedError incorrectly sets openExternal to true >> * Remove addWhiteList from public API >> * Remove WebViewReflect.java from Android >> * Fix for CB-104: Capture not returning an error code on cancel >> * Changed createCaptureFile to explicitly check for PNG and to throw an >> IllegalArgumentException if it is not a JPEG nor a PNG >> * Change based on new message passing API in IPlugin *needs claification* >> * Remove PhoneGap.stringify, replace with JSON.stringify >> * Fixed: Don't fire resume upon init - only when returning from background >> * Fixed: Backbutton should go back in appview history before going back in >> our history stack. >> * Added onMessage(id, data) to the plugin API >> * Deprecated addService(). >> * Refactored the backHistory() code so calling navigator.app.backHistory() >> has consistent behavior with the backbutton >> * Added onload attribute to plugin in plugins.xml to create the plugin at >> load time instead of lazy loading >> * Fixed bug with showing loadingDialog property. >> * Fixed Issue #23 - Crash when using splash screen. >> * Changed API to postMessage() to call a plugin's onMessage() method. >> * Optimized enumerations >> >> Windows >> * bug-fixes for XHR requests to local file system, especially important >> for jQuery Mobile apps >> * bug-fixes for issues with File API and persistence >> * getting started guides, documentation updates, wiki updates >> * improvements for plugin architecture (plugin can come from any assembly) >> * Added plugins! >> * FaceBook connect ( full graph API available to your phonegap app, >> consistent with the Android+iOS versions of the plugin ) >> * ChildBrowser >> * PGSocialShare ( status updates + links to linkedIn, Twitter, >> WindowsLive + Facebook ) >> * PGMapLauncher - get directions to/from a location, or search near a >> location using BingMaps >> >> iOS >> * Added download method to filetransfer, interface is the same like on >> Android >> * When playing audio from remote URL, stop as soon as download fails and >> make loading cacheable. >> * Fixed #197 errors on repeated getCurrentPosition calls. If the location >> services were off when getCurrentPosition was called, turn them off again >> after the position is received. >> * Don't force an orientation change unless the current orientation is >> unsupported >> * Fixed callback/callback-ios#15 - Xcode 3.2.6 Linker error when Build for >> Active Architecture Only = YES >> * Fixed callback/callback-ios#23 - on app resume, it always throws either >> an offline/online event even though the online state never changed >> * Fixed warning - implicit conversion of UIInterfaceOrientation to >> UIDeviceOrientation (which are equivalent, for the two Portraits and two >> Landscape orientations) >> * Fixed callback/callback-ios#22 - Removed unused DetectPhoneNumber and >> EnableAcceleration values in PhoneGap.plist >> * Fixed CB-96 PGWhitelist does not handle IPv4 host addresses with >> wild-cards >> * Added 'resign' and 'active' lifecycle events. >> >> >> >> >> On 11-12-12 8:40 PM, "Filip Maj" <f...@adobe.com> wrote: >> >>>BlackBerry tagged 1.3.0rc2 >>> >>>On 11-12-12 8:12 PM, "Jesse" <purplecabb...@gmail.com> wrote: >>> >>>>Windows Phone repo is tagged 1.3.0rc2 >>>> >>>> >>>>On Mon, Dec 12, 2011 at 1:54 PM, Simon MacDonald >>>><simon.macdon...@gmail.com>wrote: >>>> >>>>> I just tagged Android to 1.3.0rc2 which is basically unchanged from >>>>> 1.3.0rc1. I'm going to send out my rough test plan either later today >>>>> or early tomorrow. >>>>> >>>>> Simon Mac Donald >>>>> http://hi.im/simonmacdonald >>>>> >>>>> >>>>> >>>>> On Thu, Dec 8, 2011 at 8:15 PM, Steven Gill <stev...@adobe.com> wrote: >>>>> > Just a reminder that code freeze and rc2 will be on Monday. I am >>>>>going >>>>> > make a blog post for the changes in 1.3 when we release on Friday. >>>>> > >>>>> > I will take a look at the short logs and issue tracker, but was >>>>>wondering >>>>> > if any of you have anything to add other than general bug fixes. >>>>> > >>>>> > Also thinking about doing a post on how to upgrade from 1.2 to 1.3. >>>>> > >>>>> > -Steve >>>>> > >>>>> > On 11-12-07 12:44 PM, "Brian LeRoux" <b...@brian.io> wrote: >>>>> > >>>>> >>we need to be consistent on tag naming when we automate release >>>>>building >>>>> >> >>>>> >> >>>>> >>On Wed, Dec 7, 2011 at 2:04 AM, Jesse <purplecabb...@gmail.com> >>>>>wrote: >>>>> >>> Windows Phone has been tagged >>>>> >>> https://github.com/callback/callback-windows-phone/tags >>>>> >>> However, It is tagged 1.3.rc1 >>>>> >>> >>>>> >>> On Thu, Dec 1, 2011 at 1:57 PM, Filip Maj <f...@adobe.com> wrote: >>>>> >>> >>>>> >>>> + ... 1 ? >>>>> >>>> >>>>> >>>> On 11-12-01 1:11 PM, "Simon MacDonald" <simon.macdon...@gmail.com> >>>>> >>>>wrote: >>>>> >>>> >>>>> >>>> >Do we need to vote on this? Sorry couldn't resist. >>>>> >>>> > >>>>> >>>> >Simon Mac Donald >>>>> >>>> >http://hi.im/simonmacdonald >>>>> >>>> > >>>>> >>>> > >>>>> >>>> >On Thu, Dec 1, 2011 at 4:09 PM, Michael Brooks >>>>> >>>> ><mich...@michaelbrooks.ca>wrote: >>>>> >>>> > >>>>> >>>> >> Simon - I agree. I really like a release schedule that uses >>>>>release >>>>> >>>> >> candidates and reserves a few days for solid testing. I >>>>>appreciate >>>>> >>>>you >>>>> >>>> >> suggesting it for 1.3.0! >>>>> >>>> >> >>>>> >>>> >> Ken - There's a JIRA and GitHub ticket for the issue, so we can >>>>> >>>>move the >>>>> >>>> >> conversation there. I could use some help testing it once the >>>>>patch >>>>> >>>>is >>>>> >>>> >>in >>>>> >>>> >> place. >>>>> >>>> >> >>>>> >>>> >> Michael >>>>> >>>> >> >>>>> >>>> >> On Thu, Dec 1, 2011 at 1:05 PM, Simon MacDonald >>>>> >>>> >> <simon.macdon...@gmail.com>wrote: >>>>> >>>> >> >>>>> >>>> >> > I have no problem with the change of tag name or you getting >>>>>code >>>>> >>>>into >>>>> >>>> >> the >>>>> >>>> >> > release by the 12th. I'm just thinking we need to leave a few >>>>> days >>>>> >>>> >>13-15 >>>>> >>>> >> to >>>>> >>>> >> > do some testing and make sure we haven't broken anything. >>>>> >>>> >> > >>>>> >>>> >> > Simon Mac Donald >>>>> >>>> >> > http://hi.im/simonmacdonald >>>>> >>>> >> > >>>>> >>>> >> > >>>>> >>>> >> > On Thu, Dec 1, 2011 at 4:03 PM, Michael Brooks >>>>> >>>> >><mich...@michaelbrooks.ca >>>>> >>>> >> > >wrote: >>>>> >>>> >> > >>>>> >>>> >> > > I like it Simon. >>>>> >>>> >> > > >>>>> >>>> >> > > I'd suggest tagging as "1.3.0rc1" instead of "1.3.0_rc1" >>>>> >>>> >> > > >>>>> >>>> >> > > I would like to squeak in OS X support for BlackBerry. >>>>>Should I >>>>> >>>>have >>>>> >>>> >> this >>>>> >>>> >> > > completed by Monday December 5th or Monday December 12th? >>>>> >>>> >> > > >>>>> >>>> >> > > Michael >>>>> >>>> >> > > >>>>> >>>> >> > > On Thu, Dec 1, 2011 at 12:44 PM, Simon MacDonald >>>>> >>>> >> > > <simon.macdon...@gmail.com>wrote: >>>>> >>>> >> > > >>>>> >>>> >> > > > Hey all, >>>>> >>>> >> > > > >>>>> >>>> >> > > > For the upcoming 1.3 release can we throw down a few >>>>>dates? >>>>> >>>>Our >>>>> >>>> >>last >>>>> >>>> >> > > > release, 1.2, was tagged and released the same day. I >>>>>can't >>>>> >>>>say >>>>> >>>> >>for >>>>> >>>> >> > > certain >>>>> >>>> >> > > > but I'm guessing the rush was to get it out before the >>>>>Adobe >>>>> >>>> >> > announcement >>>>> >>>> >> > > > but we are lucky we didn't have major problems with that >>>>> >>>>release >>>>> >>>> >>as >>>>> >>>> >> we >>>>> >>>> >> > > were >>>>> >>>> >> > > > a bit light on end to end testing. >>>>> >>>> >> > > > >>>>> >>>> >> > > > Since we are thinking about releasing 1.3 on December >>>>>16th I >>>>> >>>> >>thought >>>>> >>>> >> > I'd >>>>> >>>> >> > > > work back a bit to identify some milestones. >>>>> >>>> >> > > > >>>>> >>>> >> > > > Dec 5th - Tag all repos as 1.3.0_rc1 >>>>> >>>> >> > > > Dec 12th - Tag all repos as 1.3.0_rc2 and implement a >>>>>code >>>>> >>>>freeze >>>>> >>>> >> > > > Dec 13th - Dec 14th - testing, testing, testing >>>>> >>>> >> > > > Dec 15th - Tag all repos as 1.3.0 >>>>> >>>> >> > > > Dec 16th - package and release PhoneGap 1.3 >>>>> >>>> >> > > > >>>>> >>>> >> > > > Basically we shouldn't be adding new code the week of the >>>>> 12th >>>>> >>>> >>unless >>>>> >>>> >> > we >>>>> >>>> >> > > > have broken something that we discover doing regression >>>>> >>>>testing. >>>>> >>>> >> > > > >>>>> >>>> >> > > > These are only suggestions folks but what do you think >>>>>about >>>>> a >>>>> >>>> >>little >>>>> >>>> >> > > more >>>>> >>>> >> > > > process this time around? >>>>> >>>> >> > > > >>>>> >>>> >> > > > Simon Mac Donald >>>>> >>>> >> > > > http://hi.im/simonmacdonald >>>>> >>>> >> > > > >>>>> >>>> >> > > >>>>> >>>> >> > >>>>> >>>> >> >>>>> >>>> >>>>> >>>> >>>>> > >>>>> >>> >>
