What about adding another root function to allow directly bind the state (like other components have)? It would simplify this:

root = root("root") {}.bind(Store) { s ->
  if (s.appInitialized) {
    simplePanel { ... }
  } else {
    div { content = "Loading..." }
  }
}

I'm still getting used to the way the IR compiler mangles field names. Should the tabulator module work with Kotlin models? I feel like my column definitions are going to be referencing field names that don't exist on the generated object.

Hi.. I can see the enumvalue for horizontal line in enum class TAG HR("hr") and it is annotated as unused in its open class. How to add an HR tag in kvision? Cant see an example to provide the initialAttributes and consumer for this TAG. Need to use a custom tag? Any clue?

Hi, Has anyone tried the responsive layout in Kvision tabulator? I gave this, but could not see the any changes when I see it various screen sizes..

options = TabulatorOptions(
                        layout = Layout.FITCOLUMNS,
                        responsiveLayout = ResponsiveLayout.COLLAPSE,.....

Hello guys, im playing with your example projects. First of all, thank you for the number of examples and the documentation. I’m afraid I’m missing something. In a fullstack app like “twees-fullstak-ktor”, the backend delivers the static frontend part (html+js) right? When I start “backendRun”, where can I reach the html endpoint?

I'll be giving an online talk about KVision on this Friday (04.06, 18:00 UTC+02) during Polish Tricity KUG meeting. I'll be talking in English (at least try to 😉). Feel invited if you are interested 🙂 https://www.facebook.com/events/366253874817192

Is there a card container class in KVision?

My talk will be here soon: https://www.facebook.com/groups/tricity.kotlin.user.group/permalink/2813615058950855

Is there a way to see a kvision preview (like compose or something else)? I don't want to wait every time a project is compiling 😢

This message was deleted.

I'm starting first experiments with KVision 5 features. We can discuss some breaking ideas.

Hi everyone! I can’t seem to get to work source maps under the latest KVision release (4.8.1), using the LEGACY JS compiler. Taking as base the

fomantic

example (I suppose could be any other example too), I’ve done as instructed in the docs:

To enable source maps you need to remove line sourceMaps = false from your build.gradle.kts file and remove line config.devtool = 'eval-cheap-source-map' from webpack.config.d/webpack.js file.

and enabled legacy compiler by setting under gradle.properties:

kotlin.js.compiler=legacy

But I’m not able to get source maps working. I think they were working on 4.1.0, which is the latest version I tried before updating. To test, I make a simple console.log() on App.kt and then I get the following error when clicking the line number on the console:

Could not load content for <webpack://fomantic/../src/main/kotlin/com/example/App.kt?f474> (HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME)

Is anyone having this issue as well?

Please provide a comment in the interface that value should be pushed first-time when observer set

are there plan about integration with jetpack compose web?

Hello all! Just played around with kvision for the first time and I really like it. I was able to get a Tabulator table with a couple of filtering methods (search and date) up and running pretty quickly. The mechanism for getting my data was a local json file in the resources directory:

fun get(): Array<TestClassFailures> {
    return Json.decodeFromDynamic(Results.serializer(), io.kvision.require("test_failures.json")).testClassFailures
}

This was great for testing, but I’d like to move away from this. Unfortunately my json data isn’t available via a REST api to just pull it down. The reality is much more “primitive”. I have an S3 bucket that just occasionally gets a new json file added to it. I’d like the resulting application built from the kvision project to pull this new file in (they would be sat at the same level, so the json file would be added to the “index” folder). I’ve tried replacing the json file that gets added to .zip that gets generated when the application is built, but this seems to be ignored. The json file appears to be injected into the .js files directly. It this possible?

@Robert Jaros I'm trying to understand the style {} block behaviour. It wasn't hard to figure out, but seemed surprising

I found most of the examples are using Redux for state management. But one

StateFlow

. Is it safe to use? I mean long term support

I'm evaluating KVision for our internal IS. And I have a question: would it be possible to use Material UI with Kvision. I see you have support for React, but I don't see any mention/example hot to connect your Observables with React state.

Hi. How is it meant to deal with component states? Do I need to store everything in global app store? The use case is a

main

component with several children. All children have identical functionality and are effectively a parent-child view. Where am I supposed to store

selected child in parent view

data, so it would survive

main

component refresh on global state update?

The migration guide for KV5 is ready. Please let me know if you find any other problems with the migration. https://kvision.gitbook.io/kvision-guide/part-1-fundamentals/migration/migration-from-4.x-to-5.x

@Robert Jaros, why have you chosen to implement your own Observable value, instead of using StateFlow? Only because you don't want to require coroutines with your lib or there are other reasons?

I have an application based on KVision 4.7.1. When I try to run it I get the following message:

[webpack-cli] Invalid configuration object. Object has been initialized using a configuration object that does not match the API schema.
 - configuration has an unknown property '_assetEmittingWrittenFiles'. These properties are valid:
   object { bonjour?, client?, compress?, dev?, firewall?, headers?, historyApiFallback?, host?, hot?, http2?, https?, liveReload?, onAfterSetupMiddleware?, onBeforeSetupMiddleware?, onListening?, open?, port?, proxy?, public?, setupExitSignals?, static?, transportMode?, watchFiles? }

(From what I know) I have not changed any build configurations. When I check out an earlier commit, that used to work, I get the same error. Have you got any ideas what can be wrong?

FYI, the latest kvision intellij plugin doesn't work...also tried on the latest AS canary. Get a 404...

What's the word on using KVision with something like Koin for dependency injection on the API/backend? I was thinking to try it out

Just had no time to fix all the examples.

Hey, I have a problem where this class:

@Serializable
data class EntryRecord(
    val id: Int?,
    @Contextual val creationDate: Date?,
    val contractType: String,
    val contractNumber: String,
    val pricePrepaid: Int,
    var pricePrepaidConfirmed: Boolean,
    val priceTotal: Int,
    var priceTotalConfirmed: Boolean,
    val additionalInfo: String?
)

Is serialized to this string:

"{"_id":null,"_creationDate":null,"_contractType":"Test","_contractNumber":"Test","_pricePrepaid":20099,"_pricePrepaidConfirmed":false,"_priceTotal":400095,"_priceTotalConfirmed":false,"_additionalInfo":""}"

Why is kotlin adding

_

in front of every field name? How do I get rid of this?

AppScope.launch {
            DataAccess.getRecords().catch {
                Toast.error("Błąd pobierania danych z serwera")
            }.then { records ->
                println("Records: $records")
                val filtered = ArrayList<EntryRecord>()
                for(record in records.unsafeCast<List<EntryRecord>>()) {
                    if(!record.pricePrepaidConfirmed || !record.priceTotalConfirmed) {
                        filtered.add(record)
                    }
                }

records variable is of type kotlin.Unit apparently...

I get “Automatic publicPath is not supported in this browser” when trying to load a script programmatically in kvision 5. I had never run into this before upgrading to kvision 5 (I was on a very old version), and figured out that this is a webpack 5 issue. Has anyone else run into this, and if so what did you do to fix it?

Is there an event fired when modal is closed? I need to do some action when modal is closed by

closeIcon

od pressing ESC key?