The goal is to create a workflow that allows building the plugin on
GitHub and uploading it to the server, making the plugin available
in the QtCreator Extension Manager.
Added registerPlugin.js script:
- This script creates a plugin.json file compatible with the server API.
- The file can be sent to the server, requiring TOKEN_QT in GitHub
secrets and API_URL set in the script.
Updated main build_cmake script:
- Added a state that generates plugin.json and includes it in artifacts
and releases.
- Gives possibility use GitHub releases directly in QtCreator to load
the plugin, even if the plugin data wasn't uploaded to the server.
Added ./build directory to .gitignore.
To use workflow:
- Create in github repository->settings->Secrets and variables->Actions
->Repository secrets new TOKEN and set the value from your Qt Account
- Add to the Repository secrets API_URL from your Qt Account
- In github reposytory->Settings->Actions->General->Workflow permissions
->Read and write permissions set to true
- Create relase tag in format "vx.x.x" e.g. "v0.0.1" by git tag v0.0.1
- Push chages and tag git push --tag origin main
Change-Id: I2135e0684bd3560736ecf7be1d25199713661c39
Reviewed-by: Marcus Tillmanns <marcus.tillmanns@qt.io>
Creator 14.0.0 effectively assumed "less then Qt 6 is Qt 5", even if it
is (incompatible) Qt 4.
We are now falling back to the expensive version extraction for anything
less then Qt 6 but it gets the distinction between 4 and 5 right again.
The check (once per debugger session) happens now unconditionally again
for Qt 5 and earlier and is arguably a performance regression for
Qt 5 / Creator 14 users, but it's not worse then Creator 13 where we
didn't have the shortcut mechanism
For master we should consider extending the qtVersionPing() to also
provide a cheap distinction between Qt 4 and Qt 5.
Change-Id: I4073395280fdf137e89c834bf014b9f31d74a1cd
Fixes: QTCREATORBUG-31355
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
They are still meant to be shipped.
Change-Id: Ice6cf566638463fd49df79ee787de53cfd3e188b
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
Reviewed-by: hjk <hjk@qt.io>
In order to run a non-dark theme on a system where a dark theme is set,
Qt Creator overrides the dark application palette which is set by Qt.
The override palette is defined in light-palette.inc.
This change fixes the AlternateBase role to be just a bit darker than
Base.
Fixes: QTCREATORBUG-31226
Change-Id: Idca65198d1b2b8876ca580f2a0d3ba19dd03805d
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
If there is just a spelling error in the source text that can be fixed
without changing the text's semantics, we can do that after string
freeze without interfering with the work of translators that might
already have run lupdate and started translating, by adding an english
translation file.
This should never be used to fix the meaning of the string in any way,
and should be dissolved into the tr() calls (+ fixing source tags in
translations) before the next string freeze.
Change-Id: If72505b0ca22c35ef41c0cfabed669a800315f20
Reviewed-by: Leena Miettinen <riitta-leena.miettinen@qt.io>
Reviewed-by: Christian Stenger <christian.stenger@qt.io>
Reviewed-by: hjk <hjk@qt.io>
- "Schriftart" is the graphical style
- "Zeichensatz" is a collection of characters, similar to what printers
had, used for typesetting
- "Zeichenkodierung" is character encoding
- "Schriftschnitt/Schriftstil" is a variant of a "Schriftart", like
weight, italic etc.
- "Schriftfamilie" is the collection of all "Schriftstile" of a
"Schriftart"
"Schriftschnitt/stil" seems to be the most direct translation of "font",
but keep it simple and just use "Schrift".
Change-Id: I8705dda02879a69fe94c529a96644d6ba4efe706
Reviewed-by: Robert Löhning <robert.loehning@qt.io>
Unfortunately we are not very consistent with "remove" versus "delete"
in English either.
Anyway, default the translation of "remove" to "entfernen" (like for
breakpoints etc), except where it obviously refers to deleting files
where we use "löschen".
Change-Id: I4898fe4c85fe0372d6cd314dd71e9583f8084480
Reviewed-by: Robert Löhning <robert.loehning@qt.io>
%5 is the executable's path so translating "at" to "an" does not fit.
Change-Id: I3135164ba2b7d12d9cf685efcde5b695dfb5021f
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
Check explicitly for the presence of "lib/cmake/QtCreator" directory in
order to validate a QtCreatorBuild path.
Change-Id: Ifb3a09d459ceead8c9d49a5779127f95319bd053
Reviewed-by: Eike Ziller <eike.ziller@qt.io>
Reviewed-by: Marcus Tillmanns <marcus.tillmanns@qt.io>
* Load lite workspace in lite mode
* Do not write workspace related settings to user configuration when
in lite mode
Task-number: QDS-13169
Change-Id: I65c23fff271b4aa9bfd52d3c002eb801cb87d854
Reviewed-by: Thomas Hartmann <thomas.hartmann@qt.io>
