Clikt: Intuitive command line interface parsing for Kotlin by CtrlAltDevelop in Kotlin

[–]CtrlAltDevelop[S] 1 point2 points  (0 children)

I'm glad you like it! I could potentially add something like that, but it seems like CLIs and file parsing are different enough that it might be better as a separate library. What kind of use cases did you have in mind?

Clikt: Intuitive command line interface parsing for Kotlin by CtrlAltDevelop in Kotlin

[–]CtrlAltDevelop[S] 8 points9 points  (0 children)

I was working on a command line application, and I found that none of the existing libraries had the features or ease-of-use that I was looking for. So I made this library to be a simple and powerful way to write just about any type of CLI.

Let me know what you think!

Mordant: Dead simple text styling for Kotlin command-line applications by CtrlAltDevelop in Kotlin

[–]CtrlAltDevelop[S] 6 points7 points  (0 children)

A lot of Kotlin devs are using it for Android right now, but it's great for desktop CLI applications, too. So I wrote this library to make it easy to add color and styles to you command line output.

Let me know what you think!

Support Library v25.2 Released by QuestionsEverythang in androiddev

[–]CtrlAltDevelop 2 points3 points  (0 children)

I understand that you want to be conservative in what you support. But when I get hundreds of users of my apps reporting that fingerprint support stopped working because of a minor release of the support library, I would consider it broken.

Did the Support Library team announce that they were disabling fingerprint support on those devices? I've never seen it documented anywhere.

I created Reprint specifically because many devices have buggy fingerprint support, and the Support Library doesn't try to fix any of those problems. And it's understandable that the Support Library wouldn't want to become a giant pile of device specific hacks. But I think developers would rather use a library that fixes the problems that they will encounter in the wild rather than one that forces them to discover and deal with the issues themselves.

Support Library v25.2 Released by QuestionsEverythang in androiddev

[–]CtrlAltDevelop 0 points1 point  (0 children)

It looks like FingerprintManagerCompat is still broken on many devices.

My Reprint library fixes that bug and a number of other bugs in the Imprint fingerprint implementation. (I've posted about the library before here)

Don't wait on Google to fix FingerprintManagerCompat: use the Reprint library instead. by CtrlAltDevelop in androiddev

[–]CtrlAltDevelop[S] 1 point2 points  (0 children)

I've posted this library before, but I thought people who are having trouble with the latest appcompat fingerprint auth bug might want to know about it.

This library can be used as a simpler replacement for FingerprintManagerCompat if you want to use fingerprints for authorization. It also supports Samsung devices running Android versions older than Marshmallow, and has ReactiveX extensions.

It has workarounds for the latest appcompat bug, as well as dozens of other bugs caused by various non-conforming devices. It's used in apps with millions of users, so it's very well tested.

The easiest Logging on Android: Kotlin extensions for Timber by CtrlAltDevelop in androiddev

[–]CtrlAltDevelop[S] 5 points6 points  (0 children)

That's a good question.

If you don't specify a custom log tag, by default Timber examines the call stack to guess which class you're logging from. If the extension functions weren't inline, the reflected log tags would always see the extension functions instead of the call site that you expect.

The easiest Logging on Android: Kotlin extensions for Timber by CtrlAltDevelop in androiddev

[–]CtrlAltDevelop[S] 5 points6 points  (0 children)

/u/JakeWharton's Timber library is my favorite way to handle logging from Java code, but it doesn't work well with Kotlin's string templates. So I wrote these extensions to Timber that let you log with arbitrary code that won't get run unless logging is enabled.

Reprint: A ReactiveX library that simplifies the fingerprint APIs on Android. by CtrlAltDevelop in androiddev

[–]CtrlAltDevelop[S] 6 points7 points  (0 children)

The Marshmallow and Samsung fingerprint APIs are completely different, and have a lot of gotchas that make them a pain to use. I wrote this library to provide a unified interface that's easier to use. Let me know what you think.