Yesterday I made a post on Reddit about my Spotify Landing Page Clone: https://www.reddit.com/r/Kotlin/s/kVBtwUVPuZ And I got a comment that I don't have an answer to since I haven't used Kobweb yet. So if someone here has used both Kobweb and Kilua, could you please help me with the question asked in the attached image? Basically, how is Kilua different from Kobweb?

Kilua 0.0.19 is out https://github.com/rjaros/kilua/releases/tag/0.0.19

We now have new optional

kilua-jetpack

module, with implementation of

Modifier

,

Box

,

Row

,

Column

,

Arrangement

,

Alignment

and adaptive layouts, familiar to Android Compose (or Kobweb!) users. Many thanks to @Ghasem Shirdel for his contributions in this new module.

Also, TailwindCSS 4 is now supported.

@Shubham Singh I'm implementing a new

kilua-animation

module, with composables similar to those we can find in

compose-animation

(including

animateFloatAsState

and

animateColorAsState

). I'm testing this with your SpotifyClone app and it seems to work quite well (although "spring" animation engine is a bit different and some physics based animations have a bit different timings). I'll make a PR after I release new Kilua version.

I've published 0.0.20 and it's broken 😞 I've messed up something with packaging production builds. I will have to release new version once again ...

I've decided to temporarily disable Micronaut support in Kilua RPC and Kilua. Production builds are not working and I can't even try to fix that because of dependencies conflicts.

@Shubham Singh As promised earlier I've opened a pull request in your

SpotifyClone

app.

I've been also working on the SSR version of your app, but I've found some issues which are making the process a bit harder. These are not Kilua issues but more of general SSR problems. First, you are generating random content and it is generated directly in a view layer, like this: https://github.com/shubhamsinghshubham777/SpotifyClone/blob/main/src/commonMain/kotlin/components/MainBody.kt#L161

Hey @Robert Jaros, first of all thanks you for providing us Kilua, definitely adopted it after a fast migration from kvision. I have trouble using lazy-layouts module from Kilua (js target), the error in the screenshot happen when using

items()

function from

LazyDsl

After some thinking about https://github.com/rjaros/kilua-rpc/issues/1 I've decided to remove Guice from Kilua RPC. In the next release we will have Koin modules for all servers (except Spring and Micronaut). Also there will be modules to work without any DI (with manual service registration). Any Guice users here - please protest 😉

Kilua 0.0.22 is out https://github.com/rjaros/kilua/releases/tag/0.0.22

This is really a major upgrade. The framework is now based on

kotlin-wrappers

bindings for js, browser and web API. My own, experimental common bindings have been removed. Some code was completely redesigned, most notably routing API. There are also some important changes in the SSR engine. Spring and Vert.x examples have been simplified to keep compatibility with latest dependencies (both

vertx-plugin

and

spring-dependency-management-plugin

have been removed). All examples are using now

es2015

target and

per-file

output granularity. Of course a lot of bugs were fixed as well.

Kilua 0.0.23 is out https://github.com/rjaros/kilua/releases/tag/0.0.23

Now testing Kotlin 2.2.0-Beta1 and Compose 1.8.0-beta02.

Kilua 0.0.24 is out https://github.com/rjaros/kilua/releases/tag/0.0.24

Kilua 0.0.25 is out https://github.com/rjaros/kilua/releases/tag/0.0.25

There is new

kilua-leaflet

module for interactive maps. Most code of the module is directly ported from KVision.

I have published a new, free plugin for IntelliJ IDEA - a project wizard for my Kilua framework. The plugin allows you to easily start a new web project with Kilua. You can choose a project type (frontend or fullstack), web targets (K/JS, K/Wasm or both), select optional modules and decide whether to generate SSR code, test sources and i18n code with gettext plugin and *.po translations. The plugin is open source and of course written in Kotlin - you can check the sources in the GitHub repository. This is an initial release, there might be some bugs - any feedback is welcomed. Slack Conversation

Hi @Robert Jaros, Just wanted to check do we have any option at the moment to specify metadata(keywords, title, desc, openGraph etc.) about the page specific to a particular route just like we have in next js ?

Hey! Just curious, what is the reason for having kilua-rpc instead of using [kotlinx-rpc](https://github.com/Kotlin/kotlinx-rpc). So far, I setup kotlinx and it works quite well.

Hi @Robert Jaros, I was looking into SsrRouters and found that we have multiple routers. I was checking the AsyncSsrRouter and SimpleSsrRouter So we should use AsyncSsrRouter if we are fetching some async data?:

This router will defer the rendering on the server until some asynchronous
* operation (e.g. fetching data) is finished.

If we use SimpleSsrRouter even when fetching data, then what impact it will have?

This router can be used to directly declare UI components for each route,
* which will be rendered on the server immediately for every request.

I understood their definitions, but can u tell us what exactly are theses differences, when they do make sense and when we should use each one? Does it means, if we are fetching some async data, then we should prefer AsyncSsrRouter else SimpleSsrRouter

As an FYO, I am running into KT-77004 on the compileDevelopmentExecutableKotlinWasmJs task when running wasmJsBrowserDevelopmentRun. This is occurring on a project built from the Kilua IntelliJ plugin. There are some notes on possible causes and workarounds on the ticket, but the exception doesn't help in the slightest to identify where the problems is. No line, filename, module or other detail at all.

I'm looking for advice on building navigation for the admin panel, which includes many pages organized into a multilevel navigation tree. My goal is to avoid writing related code in multiple places. Ideally, it should be possible to reconstruct routes and the nav bar from the injected`ListPage`However, I am also okay with the route file. At first glance, the real-world example could work fine at a single level, as I could automate filling both routes and the nav bar. However, I have no idea what to do with the second level, as this example contains code in both places (#1 and #2). What I dislike is that the code in both places must match precisely. Maybe I could use compose navigator assuming it will work with kilua and I could set multilevel router. Just an idea, but if I could get a navigation tree model from `kilua-routing`and when I could reconstruct the nav bar from it.

Kilua RPC 0.0.35 brings back Micronaut support https://github.com/rjaros/kilua-rpc/releases/tag/0.0.35

Kilua 0.0.26 is out https://github.com/rjaros/kilua/releases/tag/0.0.26

Testing Compose 1.9.0.

The routing API has been completely redesigned to better support SSR features.

And Micronaut support is also back.

@Sunil Kumar just tested SSR metadata with my project and it works as expected - please make sure you are testing production SSR build. I'm just leaving for a short holiday and I'll be back on Sunday (if you need any assistance).