aboutsummaryrefslogtreecommitdiffstats
path: root/subprojects/frontend/types
Commit message (Collapse)AuthorAge
* feat(web): file open and saveLibravatar Kristóf Marussy2024-02-24
| | | | In-place saving is only supported in Chromium.
* refactor(web): use filesystem access API when availableLibravatar Kristóf Marussy2024-02-23
|
* refactor(language): name disambiguationLibravatar Kristóf Marussy2024-02-02
| | | | | | * Use fully qualified names starting with :: (as in C++) to unambiguously refer to an element. * Name shadowing within modules.
* chore(deps): Java 21Libravatar Kristóf Marussy2023-12-03
| | | | Also bumps other dependencies.
* chore: clarify permissing licensingLibravatar Kristóf Marussy2023-08-24
| | | | | | | | | | | | For permissive licenses like MIT and BSD, OR EPL doesn't make sense, because the copyright original permission notice must be retained at all times. For code simply copied with minimal modifications that are unrelated to Refinery, we can just use the plain MIT license or BSD-3-clause license. For code with complex modifications related to Refinery, we can instead use the MIT AND EPL-2.0 SPDX expression, which forces downstream users to retain the original MIT notices as required by the MIT license, but also extends Refinery's copyleft to our modifications.
* chore: add copyright headersLibravatar Kristóf Marussy2023-04-15
| | | | | | | | | | | | | | Make sure we obey the REUSE (https://reuse.software) specification and the origin, copyright owner, and license of all files are clearly marked. The whole project is under the EPL-2.0, except for trivial files where copyright is not applicable that are marked with the CC0-1.0 license. Moreover, code included from third parties is also available under the respective license. chore: add CONTRIBUTORS.md List all authors and supporting organizations in accordance with the REUSE specification.
* feat(web): backend URL configurationLibravatar Kristóf Marussy2022-11-10
| | | | | | | | To point the frontend to a backend server, update the config.json file in the website root. The config.json is generated automatically in debug mode and when running from a standalone jar.
* feat(frontend): overlay window controlsLibravatar Kristóf Marussy2022-08-21
| | | | | Might need manual intervention in browsers, e.g. https://docs.microsoft.com/en-us/microsoft-edge/progressive-web-apps-chromium/how-to/window-controls-overlay#enable-the-window-controls-overlay-api-in-microsoft-edge
* chore(deps): bump frontend dependenciesLibravatar Kristóf Marussy2022-08-15
|
* refactor(frontend): move from Webpack to ViteLibravatar Kristóf Marussy2022-08-12
Also overhaulds the building and linting for frontend assets.