| commit | 5cf880d64315f295c8d5fb2b99925c81affbedb1 | [log] [tgz] |
|---|---|---|
| author | Michael Weghorn <m.weghorn@posteo.de> | Fri Nov 07 23:54:33 2025 +0100 |
| committer | Michael Weghorn <m.weghorn@posteo.de> | Mon Nov 10 23:11:25 2025 +0100 |
| tree | 5307732d4ebed98c8a85c35e03a84da8d446114a | |
| parent | 530c6ccb42cc6a67efe648b6f16ea0c5ce03e14e [diff] |
tdf#169318 extension mgr: Pass parent to TheExtensionManager::createDialog So far, TheExtensionManager::m_xParent was holding the parent window passed in the first call to TheExtensionManager::get, and would use that when creating a dialog in TheExtensionManager::createDialog. Refactor this to instead pass the parent directly to TheExtensionManager::createDialog and drop TheExtensionManager::m_xParent. This addresses the problem mentioned in earlier commit Change-Id: Ieb7d7b564140b34ff5875d2e26a777b9932cfa2d commit d5eb72a31ebb3687d9d53dab7e8128825a9bae8f Author: Michael Weghorn <m.weghorn@posteo.de> Date: Fri Nov 7 14:23:57 2025 +0100 tdf#169318 tdf#127201 extension mgr: Set dialog parent, make modal : > A remaining problem is that the parent for the > dialog in use is only set the first time the > dialog is opened, which can be seen e.g. as follows: > > 1) start Writer > 2) "Tools" -> "Extensions" > > -> Dialog opens modally on top of the Writer window > as expected > > 3) create another Writer doc > 4) close the first Writer window > 5) "Tools" -> "Extensions" > > -> The dialog doesn't open modally on top of the > Writer window and the problem described in tdf#169318 > is still reproducible. > > Consistently setting the passed parent will have to be > addressed separately in the dialog implementation itself. Now, the dialog opens properly modally on top of the second Writer window in step 5. With this commit in place, it's now also more obvious that no parent is currently set for UpdateRequiredDialog, as UpdateRequiredDialogService::execute passes an empty Reference for the parent (that was previously the default arg used for TheExtensionManager::get). Change-Id: Ifc06f093038812e262b5f35881701601b588bf19 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/193617 Tested-by: Jenkins Reviewed-by: Michael Weghorn <m.weghorn@posteo.de>
LibreOffice is an integrated office suite based on copyleft licenses and compatible with most document formats and standards. Libreoffice is backed by The Document Foundation, which represents a large independent community of enterprises, developers and other volunteers moved by the common goal of bringing to the market the best software for personal productivity. LibreOffice is open source, and free to download, use and distribute.
A quick overview of the LibreOffice code structure.
You can develop for LibreOffice in one of two ways, one recommended and one much less so. First the somewhat less recommended way: it is possible to use the SDK to develop an extension, for which you can read the API docs and Developers Guide. This re-uses the (extremely generic) UNO APIs that are also used by macro scripting in StarBasic.
The best way to add a generally useful feature to LibreOffice is to work on the code base however. Overall this way makes it easier to compile and build your code, it avoids any arbitrary limitations of our scripting APIs, and in general is far more simple and intuitive - if you are a reasonably able C++ programmer.
These are the current minimal operating system and compiler versions to run and compile LibreOffice, also used by the TDF builds:
Java is required for building many parts of LibreOffice. In TDF Wiki article Development/Java, the exact modules that depend on Java are listed.
The baseline for Java is Java Development Kit (JDK) Version 17 or later.
The baseline for Python is version 3.11. It follows the version available in SUSE Linux Enterprise Desktop and the Maintenance Support version of Red Hat Enterprise Linux.
If you want to use Clang with the LibreOffice compiler plugins, the minimal version of Clang is 12.0.1. Since Xcode doesn't provide the compiler plugin headers, you have to compile your own Clang to use them on macOS.
You can find the TDF configure switches in the distro-configs/ directory.
To setup your initial build environment on Windows and macOS, we provide the LibreOffice Development Environment (LODE) scripts.
For more information see the build instructions for your platform in the TDF wiki.
Each module should have a README.md file inside it which has some degree of documentation for that module; patches are most welcome to improve those. We have those turned into a web page here:
However, there are two hundred modules, many of them of only peripheral interest for a specialist audience. So - where is the good stuff, the code that is most useful. Here is a quick overview of the most important ones:
| Module | Description |
|---|---|
| sal/ | this provides a simple System Abstraction Layer |
| tools/ | this provides basic internal types: Rectangle, Color etc. |
| vcl/ | this is the widget toolkit library and one rendering abstraction |
| framework/ | UNO framework, responsible for building toolbars, menus, status bars, and the chrome around the document using widgets from VCL, and XML descriptions from /uiconfig/ files |
| sfx2/ | legacy core framework used by Writer/Calc/Draw: document model / load/save / signals for actions etc. |
| svx/ | drawing model related helper code, including much of Draw/Impress |
Then applications
| Module | Description |
|---|---|
| desktop/ | this is where the main() for the application lives, init / bootstrap. the name dates back to an ancient StarOffice that also drew a desktop |
| sw/ | Writer |
| sc/ | Calc |
| sd/ | Draw / Impress |
There are several other libraries that are helpful from a graphical perspective:
| Module | Description |
|---|---|
| basegfx/ | algorithms and data-types for graphics as used in the canvas |
| canvas/ | new (UNO) canvas rendering model with various backends |
| cppcanvas/ | C++ helper classes for using the UNO canvas |
| drawinglayer/ | View code to render drawable objects and break them down into primitives we can render more easily. |
Use the "..." form if and only if the included file is found next to the including file. Otherwise, use the <...> form. (For further details, see the mail Re: C[++]: Normalizing include syntax ("" vs <>).)
The UNO API include files should consistently use double quotes, for the benefit of external users of this API.
loplugin:includeform (compilerplugins/clang/includeform.cxx) enforces these rules.
Beyond this, you can read the README.md files, send us patches, ask on the mailing list libreoffice@lists.freedesktop.org (no subscription required) or poke people on IRC #libreoffice-dev on irc.libera.chat - we're a friendly and generally helpful mob. We know the code can be hard to get into at first, and so there are no silly questions.
PVS-Studio - static analyzer for C, C++, C#, and Java code.