GitLab

First batch of Python code standard compliance. Most of these are line length violations.

Differential Revision: https://phabricator.kde.org/D18708

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

- translate visibile strings in Python plugins
- avoid string puzzles
- avoid extra exclamation marks, since it is not a game
- style fixes

- translate visibile strings in Python plugins
- avoid string puzzles
- avoid contractions ("don't" -> "do not", etc)
- avoid extra exclamation marks, since it is not a game
- style fixes
- spell "JSON", and "URL" correctly

- translate visibile strings in Python plugins
- avoid string puzzles
- avoid extra exclamation marks, since it is not a game
- style fixes

- translate visibile strings in Python plugins
- avoid string puzzles
- avoid contractions ("don't" -> "do not", etc)
- avoid extra exclamation marks, since it is not a game
- style fixes
- spell "JSON", and "URL" correctly

In case of conflict in i18n, keep the version of the branch "ours"
To resolve a particular conflict, "git checkout --ours path/to/file.desktop"

Windows support will come later as discussed in
https://phabricator.kde.org/D12838. To compile use the
-DENABLE_PYTHON_2 flag. Python 3 is still the default.

For the plugins to work correctly we need the tollius and pathlib
modules through pip.

Differential Revision: https://phabricator.kde.org/D12838

Note that this changes the libkis scripting api. The Extension
class now has two methods: setup and createActions. Old code
was like this:

from PyQt5.QtGui import *
from PyQt5.QtWidgets import *
from krita import *

def hello():
    QMessageBox.information(QWidget(), "Test", "Hello World")

class HelloExtension(Extension):

  def __init__(self, parent):
      super().__init__(parent)

  def setup(self):
      action = Krita.createAction("Hello")
      action.triggered.connect(hello)

Krita.instance().addExtension(HelloExtension(Krita.instance()))

New code is like this:

from PyQt5.QtGui import *
from PyQt5.QtWidgets import *
from krita import *

def hello():
    QMessageBox.information(QWidget(), "Test", "Hello World")

class HelloExtension(Extension):

  def __init__(self, parent):
      super().__init__(parent)

  def setup(self):
      pass

  def createActions(self, window):
      action = window.createAction("Hello")
      action.triggered.connect(hello)

Krita.instance().addExtension(HelloExtension(Krita.instance()))

This also adds a new parameter to createAction: the menu location. This
is a path separated by /, for instance tools/scripts. Note that this
path must exist, otherwise a crash will happen. The paths are defined in
krita4.xmlgui...

BUG:391705

Note: we're still leaking Action objects created in Window::createAction;
that's the next fix.

CCMAIL:kimageshop@kde.org

This way, the python plugins aren't hidden underneath the actual
python plugin, making them easier to find and work with.