diff --git a/reference_manual/brushes/brush_settings/brush_tips.rst b/reference_manual/brushes/brush_settings/brush_tips.rst index 43f8ef2c6..0d365b23b 100644 --- a/reference_manual/brushes/brush_settings/brush_tips.rst +++ b/reference_manual/brushes/brush_settings/brush_tips.rst @@ -1,166 +1,163 @@ .. meta:: :description: How to use brush tips in Krita. .. metadata-placeholder :authors: - Wolthera van Hövell tot Westerflier - PMoonen - Scott Petrovic :license: GNU free documentation license 1.3 or later. .. index:: Brush tip, Brush Mask .. _option_brush_tip: ========== Brush Tips ========== .. image:: /images/brushes/Krita_Pixel_Brush_Settings_Popup.png .. _auto_brush_tip: Auto Brush ---------- The generic circle or square. These brush-tips are generated by Krita through certain parameters. Types ~~~~~ First, there are three mask-types, with each the circle and square shape: Default This is the ultimate generic type. The Fade parameter produces the below results. Of the three auto brushes, this is the fastest. .. image:: /images/brushes/Krita_29_brushengine_brushtips_default.png Soft This one's fade is controlled by a curve! .. image:: /images/brushes/Krita_2_9_brushengine_brushtips_soft.png Gaussian This one uses the gaussian algorithm to determine the fade. Out of the three auto brushes, this is the slowest. .. image:: /images/brushes/Krita_2_9_brushengine_brushtips_gaussian.png Parameters ~~~~~~~~~~ Diameter The pixel size of the brush. Ratio Whether the brush is elongated or not. .. image:: /images/brushes/Krita_2_9_brushengine_brushtips_ratio.png Fade this sets the softness of the brush. You can click the chain-symbol to lock and unlock these settings. Fade has a different effect per mask-type, so don't be alarmed if it looks strange, perhaps you have the wrong mask-type. .. image:: /images/brushes/Krita_2_9_brushengine_brushtips_default2b.png With fade locked. .. image:: /images/brushes/Krita_2_9_brushengine_brushtips_default_3.png With fade separately horizontal and vertical. Angle This changes the angle a which the brush is at. .. image:: /images/brushes/Krita_2_9_brushengine_brushtips_angle.png Spikes This gives the amount of tips related to the ratio. .. image:: /images/brushes/Krita_2_9_brushengine_brushtips_spikes.png Density This determines how much area the brush-covers over its size: It makes it noisy. In the example below, the brush is set with density 0%, 50% and 100% respectively. .. image:: /images/brushes/Krita_2_9_brushengine_brushtips_density.png Randomness This changes the randomness of the density. In the example below, the brush is set with randomness 0%, 50% and 100% respectively. .. image:: /images/brushes/Krita_2_9_brushengine_brushtips_randomness.png Spacing This affects how far brushes are spaced apart. In the below picture, the three examples on the left are with spacing 0, 1 and 5. Auto (spacing) Ticking this will set the brush-spacing to a different (quadratic) algorithm. The result is fine control over the spacing. In the below picture, the three examples on right are with auto spacing, 0, 1 and 5 respectively. .. image:: /images/brushes/Krita_2_9_brushengine_brushtips_spacing.png Smooth lines This toggles the super-smooth anti-aliasing. In the below example, both strokes are drawn with a default brush with fade set to 0. On the left without smooth lines, and the right with. Very useful for inking brushes. This option is best used in combination with Auto Spacing. .. image:: /images/brushes/Krita_2_9_brushengine_brushtips_default_2.png Precision This changes how smooth the brush is rendered. The lower, the faster the brush, but the worse the rendering looks. You'd want an inking brush to have a precision of 5 at all times, but a big filling brush for painting doesn't require such precision, and can be easily sped up by setting precision to 1. Auto (precision) This allows you to set the precision linked to the size. The first value is the brush size at which precision is last 5, and the second is the size-difference at which the precision will decrease. For example: A brush with ''starting brush size'' 10 and ''delta'' 4, will have... - precision 5 at size 10 - precision 4 at size 14 - precision 3 at size 18 - precision 2 at size 22 - precision 1 at sizes above 26. .. _predefined_brush_tip: Predefined Brushes ~~~~~~~~~~~~~~~~~~ .. image:: /images/brushes/Krita_Predefined_Brushes.png If you have used other applications like :program:`GIMP` or :program:`Photoshop`, you will have used this kind of brush. :program:`Krita` is (mostly) compatible with the brush tip definitions files of these applications: abr Gimp autobrush tip definitions. :ref:`file_gbr` Gimp single bitmap brush tip. Can be black and white or colored. :ref:`file_gih` Gimp Image Hose brush tip: contains a series of brush tips that are painted randomly or in order after each other. Can be black and white or colored. :program:`Krita` does not yet support all the parameters yet. abr Photoshop brush tip collections. We support many of the features of these brush files, though some advanced features are not supported yet. Note that the definition of ABR brushes has been reverse engineered since Adobe does not make the specification public. We strongly recommend every :program:`Krita` user to share brush tips in GBR and GIH format and more complex brushes as :program:`Krita` presets. All predefined brush tips are shown in one selector. There are four more options that influence the initial bitmap brush tip you start painting with: Scale Scales the brush tip. 1.0 is the native size of the brush tip. This can be fairly large! When painting with variable size (for instance governed by pressure), this is the base for the calculations. Rotation Initial rotation of the brush tip. Spacing Distance between the brush tip impressions. Brush Mode '''''''''' - Mask For colored brushes, don't paint the actual colors, but make a grayscale brush tip that will be colored by your selected foreground/background color. Lighter areas will be interpreted as more transparent. Color Use the fully colored brush tip. Lightness + .. versionadded:: 4.3 + Similar to mask, except maintaining the lightness differences in the brush tip. Transparency stays the same as it does in colored mode, but darker tones will be in the tone of the current foreground color. There are three sliders here, to control the exact feel of the current brush tip in this mode: - .. versionadded:: 4.3 - - Similar to mask, except maintaining the lightness differences in the brush tip. Transparency stays the same as it does in colored mode, but darker tones will be in the tone of the current foreground color. There are three sliders here, to control the exact feel of the current brush tip in this mode: - Neutral point This is the lightness level that will be the same as your current foreground color. Higher values than this will be lighter versions of the current foreground color, and lower, darker versions of the current color. Brightness Makes the tip as a whole brighter or darker. Contrast Increase the contrast between dark and light areas in the tip. - + These features can be used to mimic the feeling of impasto, or to create a variety of sparkle effects. diff --git a/untranslatable_pages/release_krita.rst b/untranslatable_pages/release_krita.rst index dd9a89a8f..07ae44912 100644 --- a/untranslatable_pages/release_krita.rst +++ b/untranslatable_pages/release_krita.rst @@ -1,203 +1,206 @@ .. meta:: :description: Releasing Krita .. metadata-placeholder :authors: - Dmitry Kazakov :license: GNU free documentation license 1.3 or later. - + .. _release_krita: ========================== Making a release ========================== .. contents:: Before the release ------------------ 1. Coordinate with #kde-promo 2. Notify translators of string freeze! 3. Verify that the release notes page is done, like https://krita.org/en/krita-4-2-release-notes/ Update version in source code ----------------------------- 1. !! REMOVE THE SURVEY LINK !! (or, if this is a beta, make a survey and update the survey link) 2. update the version of krita.xmlgui 3. update the CMakeLists.txt version 4. update the snapcraft.yaml file 5. update the appstream screenshots 6. update org.kde.krita.appdata.xml 's release tag Create the tarball ------------------ Create and push the tag ~~~~~~~~~~~~~~~~~~~~~~~ . Set the tag: `git tag -a v4.2.9-beta1 -m "Krita 4.2.9 Beta1"` 2. Push the tag: `git push origin refs/tags/v4.2.9-beta1:refs/tags/v4.2.9-beta1` 3. If you need to change the tag position (not recommended): .. code:: # remove the previous tag git push origin :refs/tags/v4.2.9-beta1 # make a new tag locally git tag -a v4.2.9-beta1 -m "Krita 4.2.9 Beta1" # push the new tag git push origin refs/tags/v4.2.9-beta1:refs/tags/v4.2.9-beta1 # all Krita developers now have to refetch tags to # get the updated tag position git fetch origin --tags Create the tarball ~~~~~~~~~~~~~~~~~~ 1. Check out kde-dev-scripts: `git clone kde:kde-dev-scripts` 2. Go into the createtarball folder, update the information in the 'config.ini' file to reflect the right tag and version number. It should look like that: .. code:: + [krita] gitModule = yes gitTag = v4.2.9 mainmodule = extragear-graphics submodule = krita version = 4.2.9 translations= yes docs = no kde_release = no 3. Create the tarball: `./create_tarball_kf5.rb -n -a krita` 4. Check that created archive has 'po' folder and it actually has translations 5. The scripts creates an .xz tarball, but our AppImage builder requires a traditional .gz tarball, so you need to create a .gz version of the tarball manually: .. code:: - tar cfz krita-4.2.9-beta1.tar.gz --group=root --owner=root krita-4.2.9-beta1 + + tar cfz krita-4.2.9-beta1.tar.gz --group=root --owner=root krita-4.2.9-beta1 6. Sign both tarballs: .. code:: + gpg --output krita-4.2.9-beta1.tar.gz.sig --detach-sign krita-4.2.9-beta1.tar.gz gpg --output krita-4.2.9-beta1.tar.xz.sig --detach-sign krita-4.2.9-beta1.tar.xz - 7. Upload tarballs to files.kde.org, where builders can fpick them up: * https://files.kde.org/krita/.release/$version/krita-$version.tar.gz * https://files.kde.org/krita/.release/$version/krita-$version.tar.xz * https://files.kde.org/krita/.release/$version/krita-$version.tar.gz.sig * https://files.kde.org/krita/.release/$version/krita-$version.tar.xz.sig Make Windows, Linux and OSX packages ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 8. Request three release builds on binary-factory.kde.org, after starting each build,go to "Console Output" section, click on "Input Requested" and choose a tarball version to build. * https://binary-factory.kde.org/job/Krita_Release_Windows32_Build/ * https://binary-factory.kde.org/job/Krita_Release_Windows64_Build/ * https://binary-factory.kde.org/job/Krita_Release_Appimage_Build/ 9. When builds are ready, downloads them and check: * Krita starts * Localization works * Python plugins are available * Basic painting and most recently fixed bugs are fixed 10. Sign both AppImages: .. code:: + gpg --detach-sign --output krita-4.2.9-beta-x86_64.appimage.sig krita-4.2.9-beta-x86_64.appimage gpg --detach-sign --output gmic_krita_qt-x86_64.appimage.sig gmic_krita_qt-x86_64.appimage 11. Build an OSX package 12. Now you should have 15(!) files in your release folder 13 Generate an md5sum.txt file for all of them: .. code:: md5sum ./* > md5sum.txt 12. Upload 15(!) files to download.kde.org (or ask sysadmins to do that using this manual ftp://upload.kde.org/README): * krita-4.2.9-beta1.tar.gz * krita-4.2.9-beta1.tar.gz.sig * krita-4.2.9-beta1.tar.xz * krita-4.2.9-beta1.tar.xz.sig * gmic_krita_qt-x86_64.appimage * gmic_krita_qt-x86_64.appimage.sig * krita-4.2.9-beta1-x86_64.appimage * krita-4.2.9-beta1-x86_64.appimage.sig * krita-x64-4.2.9-beta1-dbg.zip * krita-x64-4.2.9-beta1-setup.exe * krita-x64-4.2.9-beta1.zip * krita-x86-4.2.9-beta1-dbg.zip * krita-x86-4.2.9-beta1-setup.exe * krita-x86-4.2.9-beta1.zip * krita-4.2.9-beta1.dmg 12. Now the folder on download.kde.org should have 15(!) files. Check if you missed something (and you surely did! :) ). Release coordination ~~~~~~~~~~~~~~~~~~~~ 1. Mail KDE release coordination 2. Send release notes for future Krita versions to news@publisher.ch 3. Create bugzilla version: https://bugs.kde.org/editversions.cgi?product=krita Or file a sysadmin ticket for that. 4. [only for a major release] Warn kde sysadmins that we're going to release and that krita.org is going to take load. Just file a ticket on phabricator. PR and Communications --------------------- Pre-release ~~~~~~~~~~~ 1. Update Kiki page 2. Update press pack and page 3. Verify if manual pages are updated, if not annoy @woltherav and add undocumented features to Krita: Manual 4. Notify people that they can start making release demonstrations. Release ~~~~~~~ 1. Update download page 2. Publish the announcement and release notes Post-release ~~~~~~~~~~~~ * tumblr (wolthera) * BlenderArtists (wolthera) * deviantart (wolthera) * VK (dmitry) * blendernation (boud) * twitter (boud) * facebook (boud) * 3dpro (boud) * reddit (raghukamath) Notes ===== Additional info can be found here: https://phabricator.kde.org/T10762