* Add a mention in the packaging tutorial about Conveyor, with a feature comparison on a separate page.
Remove the link from the main page to the signing/notarization tutorial as it's already linked to from the main packaging tutorial in any case.
* Address review comments.
- Don't talk about jpackage.
- Put the features of the built in tasks first on the comparisons page.
- Remove discussion of JNI.
Additionally:
- Reformat the feature list so the summary comes first in bold.
- Point out that the feature list isn't complete.
* web: Support for transition in CSS api.
* Use proper name for Transitions class, fix formatting.
* web: add ExperimentalComposeWebApi on transitions CSS API.
* web: Add documentation for transitions CSS API.
* fix: Apply all suggested changes.
* web: Add unit tests to transitions CSS API.
* fix: Update documentation with new methods names.
* Temporary deprecate 3 overloads of StyleScope.borderWidth
The reason is wrong parameter names. The behaviour is still correct.
The idea is to fix the parameter names in 2.0 (which is more appropriate for breaking changes)
* Apply better deprecation and replacement approach
* improve the deprecation message
* fix
* add tests for deprecated borderWidth
Co-authored-by: Oleksandr Karpovich <oleksandr.karpovich@jetbrains.com>
CI uses root compose/gradlew, which doesn't call the child compose/frameworks/support/gradlew, in which we configure some env variables.
Now it is called.
All root tasks work as before.
* Add a "next steps" section to getting started docs
Users found this "getting started" tutorial by following the link on the Compose MPP landing page, but then didn't find any other docs. This change helps mitigate the problem by pointing users in a helpful direction after they've gone through the first tutorial.
* Update README.md
Co-authored-by: Igor Demin <igordmn@users.noreply.github.com>
* Restructure main page
Extract tutorials and example to separate sections.
Also add links to Android documentation. This documentation is very comprehensive comparing to our current documentation, that covers mainly desktop aspects.
Until we write our own docs, or unify Jetpack Compose docs with Google collaboration, it is better to have links to this documentation than not to have it.
* Update README.md
