We add the Cargo.lock for the release so that the tagged commit has it,
this will be usefull for the C++ users who build from source with a
tagged version of slint. Because we want to reduce the likelyhood that
they get compilation error in a dependent crate
This will be reverted after the release.
The interpreter now creates the window typically in show(), so similar
to commit a8fcb5acd6 make show() return a
promise and invoke show() from within the event loop.
Amends d98c6773e1
After commit 7df902b53c, the winit window
is not created when calling show() anymore but it's now created at
component creation time. That means the event loop workaround removed
in 459f810bd8 is now needed at
construction time.
Since this is a winit and wasm specific issue, it's now dealt with in
the wasm interpreter implementation, by invoking the creation from the
event loop from there and returning a promise in the API.
This changes the API therefore: create() can only be called after the
event loop is running.
We add the Cargo.lock for the release so that the tagged commit has it,
this will be usefull for the C++ users who build from source with a
tagged version of slint. Because we want to reduce the likelyhod that
they get compilation error in a dependent crate
This will be reverted after the release.
We add the Cargo.lock for the release so that the tagged commit has it,
this will be usefull for the C++ users who build from source with a
tagged version of slint. Because we want to reduce the likelyhod that
they get compilation error in a dependent crate
This will be reverted after the release.
All the snippets are now in the common sphinx "book", where we don't
know about the target language anymore. So for now let's let the user
expand the details tag based on what they want.
We can resurrect this code from the archive later if needed.
add Cargo.lock and set the version number in the docs
We add the Cargo.lock for the release so that the tagged commit has it,
this will be usefull for the C++ users who build from source with a
tagged version of slint. Because we want to reduce the likelyhod that
they get compilation error in a dependent crate
This will be reverted after the release.
We add the Cargo.lock for the release so that the tagged commit has it,
this will be usefull for the C++ users who build from source with a
tagged version of slint. Because we want to reduce the likelyhod that
they get compilation error in a dependent crate
This will be reverted after the release.
