* Add Minesweeper example application
* Upgrade to mpp
* Compile for web and macos
* Fix unit tests
* Commonization and housekeeping
* Build for UIKit
* Update validateExamples.sh
* add BouncingBalls example to falling-balls-mpp
* add new bouncing balls at click position instead of a random coordinates
* review improvements
Co-authored-by: Oleksandr Karpovich <oleksandr.karpovich@jetbrains.com>
* web: add example for dom-based-composables usage in plain JS
* web: add example for dom-based-composables usage in plain JS (review improvements)
Co-authored-by: Oleksandr Karpovich <oleksandr.karpovich@jetbrains.com>
* move to kotlin 1.6.10-RC and corresponding compose commit
* Update path to the karma plugin we are patching
* Add ExperimentalComposeWebStyleApi
what worries me that this actually shows that there are some cases where without any changes apart version compiler people will have to worry about such annotations
* update kotlin version in templates to adopt 1.6.10-RC
* web: move ComposableWithNullableTypeParameter.kt to passing test cases
* update kotlin version in other places
* update imageviewer example: add OptIn for experimental API
* move compose
* move to kotlin 1.6.10 and corresponding compose
* move to kotlin 1.6.10 and corresponding compose
* move to 1.0.1-rc2
* move to 1.0.1-rc2 (todoapp)
Co-authored-by: Oleksandr Karpovich <oleksandr.karpovich@jetbrains.com>
Co-authored-by: Shagen Ogandzhanian <shagen.ogandzhanian@jetbrains.com>
Remove:
```
__LATEST_COMPOSE_RELEASE_VERSION__
__KOTLIN_COMPOSE_VERSION__
System.getenv("COMPOSE_TEMPLATE_COMPOSE_VERSION")
```
They pollute templates/examples.
Now, all paths where we need to change the version are hardcoded in the script.
Usage:
```
./replace.sh 1.0.0-rc6
```
This script is planned to run on CI
In the future I will add support for changing Kotlin version
Aleksandr Veselov
Alexey Tsvetkov
Oleksandr Karpovich
Shagen Ogandzhanian
akurasov
Alexander Gorshenev
Igor Demin
Igor Demin
Igor Demin
Nikolay Igotti
Oleksandr Karpovich
Nikolay Igotti
breandan