Time Tracker For Jira 1.3.0 Download For Mac

The PhoneGap Community has done it again. We are happy to announce the release of PhoneGap 1.3! In this release, we’ve made great progress with BlackBerry and Windows Phone.

For BlackBerry, we’ve added OSX support so now you can develop for BlackBerry on a Mac!

For Windows Phone, users can now sink their teeth into the full PhoneGap API, Windows Phone Getting Started Guide, more documentation updates and tons of plugins.

PhoneGap 1.3.0 is also available on the PhoneGap Build web service - by default, all new apps will be built with 1.3.0. Any existing apps will remain on 1.1.0, and users can choose between 1.1.0, 1.2.0 and 1.3.0 for building apps for five different platforms.

26 August 2019: release 3.1.2 available¶. This release works with Hadoop 3.x.y. You can look at the complete JIRA change.

Check out the release notes below to see all of the enhancements and fixes. Alternatively, you can view the commits on http://github.com/callback.

General PhoneGap Info

• A vote was held and a motion carried to rename Apache Callback incubator project to Apache Cordova. Plans to transition Callback to Cordova will take place for the PhoneGap 1.4 release.
• PhoneGap issue tracker moved to https://issues.apache.org/jira/browse/CB

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
• Add support for future menu plugin
• 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

Blackberry

• Added OSX support. You can now develop for BlackBerry on a Mac.
• Added download method to filetransfer
• 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

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
• Fixed CB-101 can’t access media in documents://subDir

Windows Phone

• Added Full PhoneGap API support
• Bug-fixes for XMLHttpRequest calls to local file system, especially important for jQuery Mobile apps
• Updates to the Visual Studio templates, now you can create a quick app that references the PhoneGap library via a dll. Or you can start with a bare-bones project and only add the functionality you need
• [Upcoming] wiki docs on how the App Hub static analyzer sees your code, and determines required permissions
• [Upcoming] getting started screen-casts
• GapView is a usercontrol, so you can use it in your existing Windows Phone app, you don’t have to start over to use PhoneGap
• Addressed issues with File API persistence + local storage
• Getting started guides, documentation updates, wiki updates
• Improvements for plugin architecture, plugins can come from any assembly
• New plugins!
  • FaceBook connect - supports the full graph API available to your phonegap app, consistent with the Android+iOS versions of the plugin
  • ChildBrowser - display external web content without leaving your app
  • PGSocialShare - share status updates and links to LinkedIn, Twitter, Windows Live + Facebook, all at the same time, and via accounts managed on the phone
  • PGMapLauncher - get directions to or from a location, or search near a location using BingMaps. Locations can be specified as lat/lon as well as text like “Steam Clock”, or the users current location
  • LiveTiles - update your app tile on the Metro home screen with relevant info and pictures

Jesse MacFadyen, a core developer for PhoneGap, recently blogged about his experience with bringing PhoneGap to Windows Phone. Read the full journey here. You can also read the Microsoft announcement here.

If you wish to follow or join in the development of this project, send an email to callback-dev-subscribe@incubator.apache.org to subscribe to the developer mailing list.

Disclaimer: These contribution guidelines are largely based on Apache Hivecontribution guidelines.

This page describes the mechanics of how to contribute software to ApacheDrill. For ideas about what you might contribute, please see open tickets inJira.

Code Contribution Steps

The following steps outline the process for contributing code to the Apache Drill project:

You may also be interested in the additional information at the end of this document.

Step 1: Get the source code.

First, you need the Drill source code. You can use Git to put the source code on your local drive. Most development is done on 'master.'

Step 2: Get approval and modify the source code.

Before you start, send a message to the Drill developer mailing list or file a bug report in JIRA describing your proposed changes. Doing this helps to verify that your changes will work with what others are doing and have planned for the project. Be patient, it may take folks a while to understand your requirements. For detailed designs, the Drill team uses this design document template.

Once your suggested changes are approved, you can modify the source code and add some features using your favorite IDE.

The following sections provide tips for working on the project:

Coding Convention

Please adhere to the points outlined below:

• All public classes and methods should have informative Javadoc comments. Do not use @author tags.
• Code should be formatted according to Sun's conventions, with the following exceptions:
  • Indent two (2) spaces per level, not four (4).
  • Line length limit is 120 chars, instead of 80 chars.
• Contributions should not introduce new Checkstyle violations.
• Contributions should pass existing unit tests.
• New unit tests should be provided to demonstrate bugs and fixes. JUnit 4.1 is our test framework which has the following requirements:
  • You must implement a class that contains test methods annotated with JUnit's 4.x @Test annotation and whose class name ends with Test.
  • Define methods within your class whose names begin with test, and call JUnit's many assert methods to verify conditions; these methods will be executed when you run mvn clean test.

Formatter Configuration

Setting up IDE formatters is recommended and can be done by importing thefollowing settings into your browser:

• IntelliJ IDEA formatter: settings jar
• Eclipse: formatter xml

Understanding Maven

You can use the Maven Java build tool to build Drill. To get started with Maven, see the Maven tutorial.

To build Drill with Maven, run the following command:

Step 3: Get your code reviewed and committed to the project.

This section describes the GitHub pull request-based review process for Apache Drill.

Note

JIRA remains the primary site for discussions on issues. We are not using the GitHub issue tracker.

The following steps outline the code review and commit process required to contribute new code to the Apache Drill project:

1. The contributor writes the code that addresses a specific JIRA report as a contribution to the Apache Drill project.
2. The contributor organizes (squashes) their code into commits that segregate out refactoring/reorg, as necessary, to enable efficient review. The following list identifies how to combine code into commits:
   
   • Combine WIP and other small commits together.
   • Address multiple JIRAs, for smaller bug fixes or enhancements, with a single commit.
   • Use separate commits to allow efficient review, separating out formatting changes or simple refactoring from core changes or additions.
   • Rebase this chain of commits on top of the current master.
     

     Note

     The discussion that is automatically copied over from GitHub adds the review process into the Apache infrastructure. The final commit ends up in the Apache Git repo, which is the critical part. As such, there is no requirement to have your intermediate work placed anywhere outside of the GitHub pull request.

     
     

3. The contributor opens a pull request against the GitHub mirror, based on the branch that contains their work, which has been squashed together as described in step 2.

   • Open the pull request against this repo: https://github.com/apache/drill/
   • Mention the JIRA number in the heading of the pull request, like “DRILL-3000” to automatically link to JIRA.
   • For more information about pull requests, see Using Pull Requests.

4. The contributor asks a committer who has experience with the affected component for review.This information can be found in the component owners section of JIRA, or by running git blame on the primary files changed in the pull request. For pull requests that affect multiple areas, send a message to the dev list to find a reviewer.

5. The contributor sets the Reviewer field to the assigned reviewer and marks the status as REVIEWABLE.

   Crimson Text Font. Download the Crimson Text font by Sebastian Kosch. The Crimson Text font has been downloaded 67,023 times. Download crimson text font with roman style. Download free fonts for Mac, Windows and Linux. All fonts are in TrueType format. Fontsup.com is a great collection of free fonts. Below you can download free crimson text font. This font uploaded 4 November 2014. Crimson Text font viewed 2015 times and downloaded 673 times. See preview crimson text font, write comments, or download crimson text font for free. This font available for Windows 7 and Mac OS in TrueType(.ttf) and OpenType(.otf) format. Crimson text font.

6. The reviewer reviews the pull request in GitHub and adds comments or a +1 to the general discussion if the pull request is ready to commit.

   • If there are issues to address, the reviewer changes the JIRA status to 'In Progress.'
   • If the reviewer gives a +1, the reviewer adds a 'ready-to-commit' label to the Labels field in the Jira. The contributor should continue to step 9 in this process.

7. The contributor addresses review comments. This can be done with new commits on the branch or with work made on the branch locally, squashed into the commit(s) posted in the original pull request and force pushed to the branch the pull request is based on.

8. Return to step 5.

9. A Drill committer completes the following steps to commit the patch:

   • If the master branch has moved forward since the review, rebase the branch from the pull request on the latest master and re-run tests.

   • If all tests pass, the committer amends the last commit message in the series to include 'this closes #1234', where 1234 is the pull request number, not the JIRA number. This can be done with interactive rebase. When on the branch issue:

   • Change where it says “pick” on the line with the last commit, replacing it with “r” or “reword”. It replays the commit giving you the opportunity the change the commit message.

   • The committer pushes the commit(s) to the Apache repo (the GitHub repo is just a read-only mirror).

   • The committer resolves the JIRA with a message like 'Fixed in <Git commit SHA>'.

Additional Information

Where is a good place to start contributing?

After getting the source code, building and running a few simple queries, oneof the simplest places to start is to implement a DrillFunc. DrillFuncs are the way that Drill expresses all scalar functions (UDF or system).

First you can put together a JIRA for one of the DrillFuncs that we don't yet have, but should (referencing the capabilities of something like Postgres
or SQL Server). Then try to implement one.

See this example DrillFunc:

Also, you can visit the JIRA issues and implement one of those too.

More contribution ideas are located on the Contribution Ideas page.

What are the JIRA guidelines?

Please comment on issues in JIRA, making their concerns known. Please alsovote for issues that are a high priority for you.

Please refrain from editing descriptions and comments if possible, as editsspam the mailing list and clutter JIRA's 'All' display, which is otherwisevery useful. Instead, preview descriptions and comments using the previewbutton (on the right) before posting them. Keep descriptions brief and savemore elaborate proposals for comments, since descriptions are included inJIRA's automatically sent messages. If you change your mind, note this in anew comment, rather than editing an older comment. The issue should preservethis history of the discussion.

See Also