50GB of caches in branches is still being created. This doesn't
eliminate them all but makes a decent dent. This stops the more useful
master branch cache being evicted.
1. Removed the cron job that ran autofix.ci every morning to warm the cache.
2. A new reusable 'build_and_test_reusable.yaml' can be used by both ci.yaml and nightly snapshots.
3. Reduce ci.yaml build_and_test to macos-14 rust stable, ubuntu 22.04 rust 1.88 and windows 2022 rust beta.
4. With the nightly run on the free CI macos-14 rust nightly, ubuntu 22.04 nightly and windows 2022 rust 1.18.
* Install gettext on MacOS instead of compiling from source
1. Removes the attempt to install Ninja as it's included in the github
runner macos-xx images.
2. Brew install gettext and sets the env so it can be used during
compilation. This makes no difference on cached runs, but speeds up
uncached and initial runs.
* No need to install gettext
This adds an option so any job can opt out of using the cache. It defaults to using the cache so right now everything that was using the cache will continue to do so.
The second change is that as we are well over the 10GB cache limit. So we will no longer save the cache created in a PR branch. As only the master branch cache is shared this PR branch cache could only benefit subsequent runs of the same PR. If this turns out to slow PR's down it can be easily turned off later.
Error in CI:
```
Chocolatey v2.4.3
Upgrading the following packages:
llvm
By upgrading, you accept licenses for the packages.
A newer version of llvm (v20.1.7) is already installed.
Use --allow-downgrade or --force to attempt to install older versions.
Chocolatey upgraded 0/1 packages. 1 packages failed.
See the log for details (C:\ProgramData\chocolatey\logs\chocolatey.log).
Failures
- llvm - A newer version of llvm (v20.1.7) is already installed.
Use --allow-downgrade or --force to attempt to install older versions.
```
This ammends 4823ffa490
The instance passed to close_popup() was not the same as the one passed
to show_popup(), when called from another component. Fix this by
determining the instance in BuiltinFunction::ClosePopupWindow the same
way as in BuiltinFunction::ShowPopupWindow.
This issue was covered by popup_window_close.slint's JS test, but it was
commented out because we used to run the Node.js tests on Linux with Qt,
for which the popup testing doesn't work the same way in terms of
synthetic event delivery.
We decided to change that, also in light of the nodejs binaries we
upload to the NPM registry also being built without Qt support anyway.
This permits running additional popup window tests, providing test
coverage for the interpreter, some of which needed light syntax fixes.
Co-authored-by: Olivier Goffart <olivier.goffart@slint.dev>
Fixes#7318
Only the interpreter is implemented so far
MacOs won't work yet because we don't disable the default winit menubar
The viewer don't support removing the MenuBar yet
Replaces the use of NPM with PNPM. This should make it quick and easy to update any of the dependencies as dependabot will now see everything in one go.
Updated the version from 1.1 to 1.2
Renamed the header to "Slint Royalty-free Desktop, Mobile, and Web Applications License"
Added definition of "Mobile Application" and grant of right
Moved "Limitations" to 3rd section and "License Conditions - Attributions" to 2nd section
Added flexibility to choose between showing "MadeWithSlint" as a dialog/splash screen or on a public webpage
Moved the para on copyright notices to section under "Limitations"
* Extend the cspell word list
* Remove those extensions from individual source files
* white-list licenses and such as we should not meddle with those
* Fix spelling
This doesn't require a windowing system, just Linux and Vulkan drivers
that supports the display extensions.
It's called linuxkms as soon this will go beyond Vulkan and also support
EGL and perhaps dumb buffers for software rendering.
Long paths cause build issues on Windows.
- Enable support for long paths in git checkouts. The GH action runners
have the path limits disabled in the registry (good), but git needs to
know that it can use the right APIs.
- Move the cargo checkouts to the same drive as Slint, so that the
relative paths computed from the slint build dir to the cargo source
tree (as part of the skia build) don't include a drive letter (which
breaks the ninja buid).
* Add "slintpad" to cspell white list for all languages
* Mention online_editor to slintpad rename in CHANGELOG
* Move tools/online_editor into tools/slintpad
* Update github actions accordingly
Co-authored-by: Olivier Goffart <olivier@woboq.com>
Sometimes updates to packages break in the GH provided virtual machines, as
witnessed in current CI breakage. Let's let GH decide when to install security updates.
The two tests provide somewhat limited value at this time: The Firefox
tests were green before, but we think that should not have been the case
as firefox does not accept the imports in the webworker when serving
with vite in dev mode -- which we did.
Trying to change the test to use the actual generated site fails for
unknown reason: Cypress claims the page reported by `vite prefix` as up
is returning 404 in CI. It works fine locally:-/
