<@U2X0FMBS9> Hi there! What are your plans regard...

# anko

[nickk]

@vyacheslav.gerasimov Hi there! What are your plans regarding AndroidX support in anko? 5 months ago I was told by @yan that you will complete work on AndroidX.
I am about to start a new project, and I am puzzled. I want to reuse anko code from another project, and I am hesitating.

@hhariri Don’t you feel that a 15.000 stars project deserves some love?

[hhariri]

I’ll talk to team to get some update.

[miha-x64]

Creating your own Anko View DSL function takes four lines of code. I mean, it's very easy to do yourself.

[nickk]

@miha-x64 You mean all that it takes for AndroidX support is 4 lines of code? And this is pending for more than a year?

[miha-x64]

Nope. I mean, you need support for a certain view — you write four lines and that's it.

[nickk]

@miha-x64 I’ve done this already. But I would like to understand if anko is officially “dead”, before using it in a new project.
And I am asking again, because I find it unbelievable that one of the most loved libraries is left to die slowly.

[nickk]

@miha-x64 Here is one example…

/** ****************************************************************
 *  Extend the anko DSL to support `ExpandableLayout`
 * ***************************************************************** */
inline fun ViewManager.expandableLayout(init: ExpandableLayout.() -> Unit = {}): ExpandableLayout {
    return ankoView({ ExpandableLayout(it) }, theme = 0, init = init)
}

[ribesg]

Use #splitties, whatever anyone says, Anko is dead.

[nickk]

You are probably right.
My issue is that I already have code in anko.
A small library on top of anko, and a lot of code that uses it…

louiscad is a very nice guy, but it is perfectly understandable that at some point he might not be able to maintain splitties.

[miha-x64]

Anyone at some point might not be able to maintain anything.
This does not matter while library helps you and solves your problems.

[louiscad]

Maintaining Splitties is easier for anyone than maintaining Anko because that latter one uses custom templates to generate Kotlin code, while the former is made from a more classic project structure (although optimized for the relatively high number of modules).

That means that if I die in 1 second, you should be safe discussing who's fork(s) will be the next Splitties versions, and that could be yourself.

[louiscad]

I'm also semi-automating repetitive tasks in Splitties, most with Kotlin scripts (releasing a new version, and creating a new module are already done), that allows me to provide long term support without taxing my personal time too much with chores.

[nickk]

@louiscad I hope you live long and well! And I think I am going to try to convert to splitties.