It's been a busy couple of weeks at Textualize. We've been building apps with Textual, as part of our dog-fooding week. The first app, Frogmouth, was released at the weekend and already has 1K GitHub stars! Expect two more such apps this month.
Less than a week since the last release, and we have a new API to show you.
This is a surprisingly large release, given it has been just 7 days since the last version (and we were down a developer for most of that time).
What's new in this release?
Textual 0.16.0 lands 9 days after the previous release. We have some new features to show you.
A (reasonable) criticism of async is that it tends to proliferate in your code. In order to await something, your functions must be async all the way up the call-stack. This tends to result in you making things async just to support that one call that needs it or, worse, adding async just-in-case. Given that going from def to async def is a breaking change there is a strong incentive to go straight there.
Before you know it, you have adopted a policy of "async all the things".
We've just pushed Textual 0.15.0, only 4 days after the previous version. That's a little faster than our typical release cadence of 1 to 2 weeks.
What's new in this release?
Textual version 0.14.0 has landed just a week after 0.13.0.
Note
We like fast releases for Textual. Fast releases means quicker feedback, which means better code.
What's new?
Every widget in Textual, be it a button, tree view, or a text input, runs an asyncio task. There is even a task for scrollbar corners (the little space formed when horizontal and vertical scrollbars meet).
It's been just 9 days since the previous release, but we have a few interesting enhancements to the Textual API to talk about.
We released Textual 0.10.0 25 days ago, which is a little longer than our usual release cycle. What have we been up to?