| commit | 20e1c3d2f35afba1adf0e5852a83a753efaf500d | [log] [tgz] |
|---|---|---|
| author | Michael Weghorn <m.weghorn@posteo.de> | Tue Feb 18 20:29:20 2025 +0100 |
| committer | Michael Weghorn <m.weghorn@posteo.de> | Wed Feb 19 22:41:50 2025 +0100 |
| tree | 6dbd565cac229da1929384f419b73cd2d50ee4ca | |
| parent | f310b47ead5bf4a85a1c93d15b3c5f78f6675f7a [diff] |
tdf#130857 Let Formatter:m_aOutputHdl convert double to text So far, the Formatter:m_aOutputHdl output handler set via Formatter::SetOutputHdl did not receive any parameter and had the responsibility to set the text based on the current value, i.e. first retrieve the current value, then convert it to a text representation, and then set that text in the formatter. Change semantics so that the method instead receives the (double) value to format as a parameter and returns the formatted string. Passing the current value as a double and using the returned string to update the text is now the responsibility of the only caller, Formatter::ImplSetValue. Adjust the naming accordingly: * Formatter:m_aOutputHdl -> Formatter::m_aFormatValueHdl * Formatter::SetOutputHdl -> Formatter::SetFormatValueHdl This is similar to the change done elsewhere in commit 76396a371eb7dfef79963d00fea54a989f54fbbc Author: Michael Weghorn <m.weghorn@posteo.de> Date: Sat Feb 15 13:44:50 2025 +0100 tdf#130857 weld: Abstract from "input"/"output" SpinButton signals (and changes referenced from its commit message) and is one step towards supporting value <-> text conversion in QtInstanceFormattedSpinButton as well. No change in behavior is intended by this commit. Change-Id: I6b3fbccc89b89446a1ea367a80aeed3a7b583298 Reviewed-on: https://gerrit.libreoffice.org/c/core/+/181911 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.