Hehe, I'm already dogfooding such a thing where I don't even need the

onCreateOptionsMenu

callback. BTW, the sample should already have

addItem

for menu, and a few other extensions. If not, it's a matter of time, once I'm done with the most important documentation parts.

I've written menu extensions for Anko some time ago: https://github.com/Kotlin/anko/pull/324/files

Should I make yet another split named

menu

?

@louiscad first you should release 3.0, but creating a feature request in the issues, yes!

Is this the correct way using

start

and bundle extras with

BundleSpec

?

start<MyActivity> {
    MyActivity.ExtrasSpec.weight = weight
    MyActivity.ExtrasSpec.height = height
}

Is there any way to use the views dsl without constantly invoking

add()

for nesting

verticalLayout {
        add(textView {
            textResource = R.string.some_text
        }, lParams())
}

Coming from other dsl’s it feels a bit cumbersome to me, I’d expect to be able to write something like

verticalLayout {
    textview {
        textResource = R.string.some_text
    }
}

Am I missing something? I don’t have much experience with android

Hello dear Views DSL users, I just submitted a feature request for first-class support of IDE preview in Android Studio, you can star the issue as I'm pretty sure you'd like it: https://issuetracker.google.com/issues/155554920

Hello folks, do I have any users already using Kotlin 1.4-M2 or planning to?

Hello! Is there a DSL for creating

ColorStateList

in code? I mean not loading from resources (

colorSL

), but actually specifying states and colors manually.

Hello, for the users of the

permissions

split, I made a feature request to allow me to tell Android Studio and lint that a permission has been verified to be granted. Your stars will be appreciated: https://issuetracker.google.com/issues/158721540

@louiscad What is your roadmap to release 3.0 version?

dip(value: Int): Int
dp(value: Int): Float

This looks counterintuitive to me. Also, I miss (Float) -> Int overload: having Float dp makes much more sense than having Float pixels.

And this is just horrible amount of indirection…

return viewFactory(V::class.java

🙀

Why do you need an XML layout (which prevents shrinking) and why

Context.recyclerView()

and

View.recyclerView()

have different behaviour? https://github.com/LouisCAD/Splitties/blob/8782cbb5d039a553ed2c5cf795eb53a86146ce91/modules/views-dsl-recyclerview/src/androidMain/kotlin/splitties/views/dsl/recyclerview/RecyclerView.kt#L27

Is splitties in version 3.0.0-alpha06 expected to compile without issues with Kotlin 1.4? I am unable to compile project after updating from Kotlin 1.3.70:

Caused by: java.lang.IllegalStateException: Couldn't obtain compiled function body for public final inline fun <get-progressBar>(): splitties.views.dsl.core.styles.ProgressBarAndroidStyles defined in splitties.views.dsl.core.styles.AndroidStyles[PropertyGetterDescriptorImpl@4d0bbd88]
	at org.jetbrains.kotlin.codegen.inline.InlineCodegen$Companion.getCompiledMethodNodeInner(InlineCodegen.kt:579)
	at org.jetbrains.kotlin.codegen.inline.InlineCodegen$Companion.createInlineMethodNode$backend(InlineCodegen.kt:543)
	at org.jetbrains.kotlin.codegen.inline.InlineCodegen.performInline(InlineCodegen.kt:143)
	... 74 more

If any of you are using dev versions, you can update to 3.0.0-dev-077. It's very close to the next official release. I finally got a reliable publishing process that checks the artifacts are not corrupted after upload and before publishing. The Kotlin 1.4 compatible release is near.

The Kotlin 1.4 compatible release is even more near since publication of the version

3.0.0-dev-105

succeeded, validating the hardened publishing process (that validates every artifact can be resolved in an actual multiplatform project before publishing). Feel free to try upgrading your projects to Kotlin 1.4 and use this version. I have some more work before a proper release, but I'm on good track!

📢📢📢 Splitties 3.0.0-beta01 is here! It got a lot of new stuff since alpha06 (look at alpha07 changes too), especially for Views DSL users and coroutines users. It works with Kotlin 1.4 and it enters the KMM game with iOS, macOS, watchOS, Windows and Linux compatibility for several splits (see the README). Take the time to read about the changes here: https://github.com/LouisCAD/Splitties/releases Also, if you like my work, please consider picking a sponsoring tier on GitHub sponsors so I can work towards dedicating more day time on it (rather than night time besides a full-time job) ❤️

Changed the short description to: "A collection of hand-crafted extensions for your Kotlin projects."

I have a problem (in both

3.0.0-dev-105

and

3.0.0-beta01

) with assembling custom build type. I have alpha build type declared in

app

module as follows:

buildTypes {
    getByName("alpha") {
        applicationIdSuffix = ".alpha"
        versionNameSuffix = "-alpha"
    }
}

I'm not able to see view dsl preview with beta01. So i have reverted alpha07. The design preview remains white.

Thanks for

UnreliableToastApi

warning. Nice approach!

Which is the preferred method / extension to update layoutparams of a view?

Hello, how can i create a pendingIntent with extrasSpecs? Thanks

What's the best translation of this into splitties' code?

android:textAppearance="?attr/textAppearanceSubtitle1"

Tried to find somthing like

styledResourceId(R.attr.textAppearanceSubtitle1)

, but no luck.

@louiscad Do you have any plans to move from jcenter() repository? It looks like that only few days are left before total shutdown, and I suppose splitties will become unavailable.

Removing

splitties-coroutines

from my Kotlin Native project fixed an error caused by (I think) the difference in kotlinx.coroutines version it was compiled against

Do you folks declare view_ids.xml like this or simply write 1, 2, 3 etc?

@louiscad Do you think views dsl is still a valid way to go or should one just use jetpack compose if they want to break free from xml?