commit | 72eed7797bce11469f14285b4d7be2ee4373a0e7 | [log] [tgz] |
---|---|---|
author | rniwa@webkit.org <rniwa@webkit.org@268f45cc-cd09-0410-ab3c-d52691b4dbfc> | Sat May 20 00:03:24 2017 +0000 |
committer | rniwa@webkit.org <rniwa@webkit.org@268f45cc-cd09-0410-ab3c-d52691b4dbfc> | Sat May 20 00:03:24 2017 +0000 |
tree | 912ac6304fd39e2b35e7e96cca5a44920f7685c2 | |
parent | e0fb99aa4e2f79d63e2e26f76046b36013b0321a [diff] |
Add a commit log viewer next to the analysis results viewer https://bugs.webkit.org/show_bug.cgi?id=172399 Reviewed by Chris Dumez. Add a commit log viewer next to the analysis results viewer, which visualizes the A/B testing results. Also linkify the revisions in the table that shows the status of each A/B testing job, and allow the prefix of "r" when associating a Subversion revision. Finally, Fixed a bug that the list of commits associated with the analysis task were not re-rendered when the list was updated by the user. * public/v3/components/analysis-results-viewer.js: (AnalysisResultsViewer): Added _selectorRadioButtonList as an instance variable. It's a list of radio buttons to select a configuration (A/B) with a commit set. It's added to update the checked status of radio buttons upon changing the currently selected test group. (AnalysisResultsViewer.prototype.setTestGroups): Update the selected range to that of the currently selected group. (AnalysisResultsViewer.prototype.render): Fill _selectorRadioButtonList with radio buttons. * public/v3/components/commit-log-viewer.js: (CommitLogViewer): Added _showRepositoryName as an instance variable. (CommitLogViewer.prototype.setShowRepositoryName): Added. (CommitLogViewer.prototype.render): Hide the repository name when _showRepositoryName is false. This is used in the newly added commit log viewer for the analysis results since we're showing a select element with all the names of repositories above this component. * public/v3/components/test-group-revision-table.js: (TestGroupRevisionTable.prototype._buildCommitCell): Linkify the revisions if possible. * public/v3/models/analysis-task.js: (AnalysisTask.prototype.associateCommit): Strip "r" at the beginning for a Subversion like r12345 since that's the format we use to show to the user. This makes copy & paste easier. * public/v3/pages/analysis-task-page.js: (AnalysisTaskResultsPane): Added a bunch of new instance variables to show and update the commit log viewer next to the analysis results viewer. (AnalysisTaskResultsPane.prototype.setPoints): Create the list of repositories to show details. (AnalysisTaskResultsPane.prototype.didConstructShadowTree): Re-render when the current selected test group changes since that may have updated the selected range for A/B testing. Also re-render when a new repository is selected to show details. (AnalysisTaskResultsPane.prototype.render): Update the list of repositories and the commit log viewer. (AnalysisTaskResultsPane.prototype._renderRepositoryList): Renders the list of repositories. (AnalysisTaskResultsPane.prototype._updateCommitViewer): Updates the commit log viewer given the range selected in the analysis results viewer. (AnalysisTaskResultsPane.htmlTemplate): Updated the template. (AnalysisTaskResultsPane.cssTemplate): Ditto. (AnalysisTaskTestGroupPane.cssTemplate): Add a little space between the list of results and the table of A/B testing jobs with revisions. (AnalysisTaskPage.prototype.render): Fixed the bug that the list of commits associated with the task is not updated when the list changes the task or the start point never changed when the list of commits associated with the task changed. Make the lazily evaluated function compare the actual list of commits so that it will invoke _renderCauseAndFixes when the list changes. (AnalysisTaskPage.prototype._renderCauseAndFixes): Now renders a specific list. git-svn-id: http://svn.webkit.org/repository/webkit/trunk@217173 268f45cc-cd09-0410-ab3c-d52691b4dbfc
WebKit is a cross-platform web browser engine. On iOS and macOS, it powers Safari, Mail, iBooks, and many other applications.
Visit WebKit Feature Status page to see which Web API has been implemented, in development, or under consideration.
Downloading Safari Technology Preview to test the latest version of WebKit.
Once your bug is filed, you will receive email when it is updated at each stage in the bug life cycle. After the bug is considered fixed, you may be asked to download the latest nightly and confirm that the fix works for you.
On Windows, follow the instructions on our website.
Run the following command to clone WebKit's Git SVN repository:
git clone git://git.webkit.org/WebKit.git WebKit
If you want to be able to commit changes to the repository, or just want to check out branches that aren’t contained in WebKit.git, you will need track WebKit's Subversion repository. You can run the following command to configure this and other options of the new Git clone for WebKit development.
Tools/Scripts/webkit-patch setup-git-clone
For information about this, and other aspects of using Git with WebKit, read the wiki page.
Run the following command to check out WebKit's subversion repository:
svn checkout https://svn.webkit.org/repository/webkit/trunk WebKit
Install Xcode and its command line tools if you haven't done so already:
xcode-select --install
Run the following command to build a debug build with debugging symbols and assertions:
Tools/Scripts/build-webkit --debug
For performance testing, and other purposes, use --release
instead.
You can open WebKit.xcworkspace
to build and debug WebKit within WebKit.
If you don't use a custom build location in Xcode preferences, you have to update the workspace settings to use WebKitBuild
directory. In menu bar, choose File > Workspace Settings, then click the Advanced button, select “Custom”, “Relative to Workspace”, and enter WebKitBuild
for both Products and Intermediates.
The first time after you install a new Xcode, you will need to run the following command to enable Xcode to build command line tools for iOS Simulator:
sudo Tools/Scripts/configure-xcode-for-ios-development
Without this step, you will see the error message: “target specifies product type ‘com.apple.product-type.tool’, but there’s no such product type for the ‘iphonesimulator’ platform.
” when building target JSCLLIntOffsetsExtractor
of project JavaScriptCore
.
Run the following command to build a debug build with debugging symbols and assertions for iOS:
Tools/Scripts/build-webkit --debug --ios-simulator.
Install the dependencies by running the following command:
Tools/gtk/install-dependencies
Then run the following command to build additional dependencies:
Tools/Scripts/update-webkitgtk-libs
Run the following command to build WebKit with debugging symbols for GTK+ port:
Tools/Scripts/build-webkit --debug --gtk
Note that the procedure for building a release tarball is different. For more information, see the wiki page.
For building WebKit on Windows, see the wiki page.
Run the following command to launch Safari with your local build of WebKit:
Tools/Scripts/run-safari --debug
The run-safari
script sets the DYLD_FRAMEWORK_PATH
environment variable to point to your build products, and then launches /Applications/Safari.app
. DYLD_FRAMEWORK_PATH
tells the system loader to prefer your build products over the frameworks installed in /System/Library/Frameworks
.
To run other applications with your local build of WebKit, run the following command:
Tools/Scripts/run-webkit-app <application-path>
Run the following command to launch iOS simulator with your local build of WebKit:
run-safari --debug --ios-simulator
In both cases, if you have built release builds instead, use --release
instead of --debug
.
Congratulations! You’re up and running. Now you can begin coding in WebKit and contribute your fixes and new features to the project. For details on submitting your code to the project, read Contributing Code.