@louiscad What do you think about adding overload for

view.dip()

to be able to deal with floating values where needed. Because without that you have to use your own helper or write extra code:

elevation = dip(4).toFloat()

dp

(1️⃣ ),

dip

(2️⃣) or both (0️⃣)?

It is not directly connected with Splitties, but as it is about moving from xml, I'll ask here 🙂 The most common practice to have some set of colors is to put them into

colors.xml

file (something like

<color name="colorBlack">#000000</color>

) But is there any better way having in mind that we try to eliminate xml files in our projects? 🙂 I'm thinking about some helper class with constant values:

const val Black = 0x000000.toInt()

Does it sound reasonable? Is it somehow better than xml? Or it really doesn't matter in practice? What do you think?

Here's another one I like better because it allows setting insets for both top and bottom (important as setting a window inset listener replaces any previously set one):

enum class InsetType { None, Padding, Margin }
fun View.inset(top: InsetType = None, bottom: InsetType = None)

Hi there. Is there something in Splitties like anko’s

selector

? It was pretty basic, but in many cases it was just what I needed. I do not see something similar. This means I would have to use the RecycleView DSL to create something similar? Actually,

RecyclerView

is an overkill. I would go for a custom alert.

I got an interesting question from Ben Manes @louiscad https://github.com/jmfayard/buildSrcVersions/pull/117

Hello. I was unable to find a shortcut for

.withStyledAttributes(attr) { getResourceId(it, 0) }

. Should I create a PR? None of the files below look suitable, should I create a new one? https://github.com/LouisCAD/Splitties/tree/8782cbb5d039a553ed2c5cf795eb53a86146ce91/modules/resources/src/androidMain/kotlin/splitties/resources

Looks like View DSL lacks

space()

.

Hello #splitties any idea about

startActivityForResult

? I think is not implemented yet

Hey, @louiscad! Using splitties for the first time now. Testing on AlertDialogs. Wish me luck xD

How can I avoid using

appctx

module? Just found it thanks to Analyze APK. For some reason I can't even see it in 'merged manifest' or 'external libraries'. I understand the motivation but don't want Android to create one more component and and to have one more singleton.

Hello, with the permissions on Splitties, is there a way to check if the permissions have been granted on the settings part? For example, location permissions, an app can have the permissions granted but gps not enabled or turned on, is there a way to prompt with the dialog and enable gps?

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! Is there a DSL for creating

ColorStateList

in code? I mean not loading from resources (

colorSL

), but actually specifying states and colors manually.

@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

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