commit | 4fd540cbfc40da6f2f25ec4c757a9924c24a2161 | [log] [tgz] |
---|---|---|
author | weinig@apple.com <weinig@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc> | Mon Jun 29 20:31:18 2020 +0000 |
committer | weinig@apple.com <weinig@apple.com@268f45cc-cd09-0410-ab3c-d52691b4dbfc> | Mon Jun 29 20:31:18 2020 +0000 |
tree | 110568f61d2ba672ef4c7f7eb7ed086a4db94ad4 | |
parent | ccd1580bbeb4dc7cad63fdedfcf3204946de604b [diff] |
Remove remaining makeSimpleColorFrom* variants https://bugs.webkit.org/show_bug.cgi?id=213706 Reviewed by Darin Adler. Source/WebCore: Removed makeSimpleColorFromFloats and makeSimpleColorFromCMYKA. - Updated callers that need to pass floats to use makeSimpleColor(SRGBA { ... }); - Updated callers that don't need to pass floats, mostly compile time constant SimpleColors to use makeSimpleColor(...), passing in 0-255 based component values. - Updated callers of makeSimpleColorFromCMYKA to use makeSimpleColor(toSRGBA(CMYKA { ... })). This required adding CMYKA type to ColorTypes.h and moving conversion SRGBA to ColorUtilities with the other color conversion code. - Added deduction guides for color types to allow component type deduction. This allows us to write: function(SRGBA { redFloat, greenFloat, blueFloat, alphaFloat }) reather than the more cumbersome: function(SRGBA<float> { redFloat, greenFloat, blueFloat, alphaFloat }) - Added operator==/operator!= for each color type. Only used by CMYKA at the moment, but generally useful, so added for all of them. For all types convertable to ColorComponents, the implementation uses the conversion to ColorComponents to avoid redundancy. * html/canvas/CanvasRenderingContext2DBase.cpp: (WebCore::CanvasRenderingContext2DBase::setStrokeColor): (WebCore::CanvasRenderingContext2DBase::setFillColor): Update to call new typed color based CanvasStyle functions. (WebCore::CanvasRenderingContext2DBase::setShadow): Use makeSimpleColor rather than makeSimpleColorFromFloats/makeSimpleColorFromCMYKA. * html/canvas/CanvasStyle.cpp: (WebCore::CanvasStyle::CanvasStyle): Replace constructors taking raw floats with ones taking typed colors (SRGBA<float>/CMYKA<float>) to make it more clear what the parameters mean. (WebCore::CanvasStyle::isEquivalentColor const): Compare the cmyka components using new operator== implementation for CMYKA<float>. (WebCore::CanvasStyle::isEquivalent const): (WebCore::CanvasStyle::isEquivalentRGBA const): Deleted. (WebCore::CanvasStyle::isEquivalentCMYKA const): Deleted. Replace isEquivalentRGBA/isEquivalentCMYKA with overloaded isEquivalent. (WebCore::CanvasStyle::applyStrokeColor const): (WebCore::CanvasStyle::applyFillColor const): Update for new names of CMYKA members. * html/canvas/CanvasStyle.h: Use SRGBA<float> and CMYKA<float> to simplify interfaces * page/DebugPageOverlays.cpp: * page/linux/ResourceUsageOverlayLinux.cpp: (WebCore::ResourceUsageOverlay::platformInitialize): Use makeSimpleColor rather than makeSimpleColorFromFloats, allowing for constant expression creation of SimpleColors. * platform/graphics/Color.cpp: (WebCore::Color::lightened const): (WebCore::Color::darkened const): Use makeSimpleColor(SRGBA { ... }) rather than makeSimpleColorFromFloats. (WebCore::Color::luminance const): Fix comment. (WebCore::blendWithoutPremultiply): Use makeSimpleColor(...) rather than makeSimpleColorFromFloats. * platform/graphics/ColorTypes.h: (WebCore::operator==): (WebCore::operator!=): - Add deduction guides and operator==/operator!= for each color type. - Add CMYKA type. No conversion to ColorComponents yet, as ColorComponents only works with 4 component colors, not ones with 5 like CMYKA. * platform/graphics/ColorUtilities.cpp: (WebCore::toSRGBA): Move conversion from CMYKA to SRGBA from makeSimpleColorFromCMYKA to here. * platform/graphics/ColorUtilities.h: (WebCore::convertPrescaledToComponentByte): (WebCore::convertToComponentByte): Use std::round rather than std::lroundf, since it will have the same result and it reads nicer. * platform/graphics/SimpleColor.cpp: (WebCore::makeSimpleColorFromCMYKA): Deleted. * platform/graphics/SimpleColor.h: (WebCore::makeSimpleColor): (WebCore::makeSimpleColorFromFloats): Deleted. - Removed makeSimpleColorFromFloats and makeSimpleColorFromCMYKA. - Added constexpr overload of makeSimpleColor taking a const SRGBA<uint8_t>&. - Fixed forward declaration of makeSimpleColor that was taking ColorComponents to actually take an SRGBA<float>, which is what the inline implementation actually takes. * platform/graphics/avfoundation/InbandTextTrackPrivateAVF.cpp: (WebCore::makeSimpleColorFromARGBCFArray): * platform/graphics/cairo/GradientCairo.cpp: (WebCore::interpolateColorStop): * platform/graphics/cg/ColorCG.cpp: (WebCore::makeSimpleColorFromCGColor): * platform/graphics/win/PlatformContextDirect2D.cpp: (WebCore::PlatformContextDirect2D::brushWithColor): Use makeSimpleColor(SRGBA { ... }) rather than makeSimpleColorFromFloats. * platform/graphics/mac/ColorMac.mm: (WebCore::makeSimpleColorFromNSColor): * platform/ios/ColorIOS.mm: (WebCore::colorFromUIColor): Use makeSimpleColor(SRGBA { ... }) rather than makeSimpleColorFromFloats. Casting to float is needed, as the input types are CGFloat which is double in 64-bit environments and won't automatically narrow with the new types. * platform/ios/LegacyTileCache.mm: (WebCore::LegacyTileCache::colorForGridTileBorder const): * rendering/RenderLayer.cpp: (WebCore::RenderLayer::beginTransparencyLayers): Use makeSimpleColor rather than makeSimpleColorFromFloats, allowing for constant expression creation of SimpleColors. * rendering/RenderThemeIOS.mm: (WebCore::RenderThemeIOS::paintCheckboxDecorations): (WebCore::RenderThemeIOS::paintRadioDecorations): (WebCore::RenderThemeIOS::paintMenuListButtonDecorations): (WebCore::RenderThemeIOS::paintSystemPreviewBadge): Use Color::black/Color::white.colorWithAlpha(...) rather than makeSimpleColorFromFloats, allowing for constant expression creation of SimpleColors. Source/WebKit: * UIProcess/API/wpe/WebKitColor.cpp: (webkitColorToWebCoreColor): Use makeSimpleColor(SRGBA { ... }) rather than makeSimpleColorFromFloats. * WebProcess/Inspector/WebInspectorClient.cpp: (WebKit::WebInspectorClient::showPaintRect): * WebProcess/WebPage/FindController.cpp: (WebKit::FindController::drawRect): Use makeSimpleColor rather than makeSimpleColorFromFloats, allowing for constant expression creation of SimpleColors. git-svn-id: http://svn.webkit.org/repository/webkit/trunk@263688 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.
On macOS, download Safari Technology Preview to test the latest version of WebKit. On Linux, download Epiphany Technology Preview. On Windows, you'll have to build it yourself.
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
or
git clone https://git.webkit.org/git/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.
If you don‘t want to use Git, 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 Xcode.
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
For production builds:
cmake -DPORT=GTK -DCMAKE_BUILD_TYPE=RelWithDebInfo -GNinja ninja sudo ninja install
For development builds:
Tools/gtk/install-dependencies Tools/Scripts/update-webkitgtk-libs Tools/Scripts/build-webkit --gtk --debug
For more information on building WebKitGTK+, see the wiki page.
For production builds:
cmake -DPORT=WPE -DCMAKE_BUILD_TYPE=RelWithDebInfo -GNinja ninja sudo ninja install
For development builds:
Tools/wpe/install-dependencies Tools/Scripts/update-webkitwpe-libs Tools/Scripts/build-webkit --wpe --debug
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
.
If you have a development build, you can use the run-minibrowser script, e.g.:
run-minibrowser --debug --wpe
Pass one of --gtk
, --jsc-only
, or --wpe
to indicate the port to use.
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.