update status in README

This commit is contained in:
🪞👃🪞 2024-10-25 01:15:55 +03:00
parent 708531571a
commit 2b4c37e6a7

View file

@ -1,18 +1,22 @@
> [!WARNING]
>
> As of 2024-09-10, I'm working hard to bring this project back
> to a usable state (as seen e.g. [here](https://mastodon.social/@unspeaker/112752419822653484)).
> As of 2024-10-25, I'm on track to releasing `tek 0.2.0` sometime in December 2024.
> I plan to tag the working prototype (as seen in the demos published in the
> [tek channel at basspistol's peertube](https://v.basspistol.org/c/tek/videos) as `0.1.0`
> once I've identified the appropriate commit!
>
> I reached the limit of how much of the UI I can write imperatively,
> and started refactoring it in a more declarative style. I'm quite
> excited about how the interface logic is turning out!
> I've been dreaming of this project for a decade, and finally had the experience and peace of mind
> to start building it in late May 2024. I quickly reached the limit of how much of the UI I can
> write imperatively, so I started refactoring it in a more declarative style. The new interface
> logic is holding out pretty well, though it's not presently without its warts.
>
> Your moral support means a lot to me.
> Feel free to [contact me on Mastodon](https://mastodon.social/@unspeaker)!
> Your moral support means a lot to me. Feel free to [contact me on Mastodon](https://mastodon.social/@unspeaker)!
> (Especially if you know how to host LV2 plugin UIs in `winit`; or how to relink abandoned Win32
> VST2s into LV2 or CLAP monoliths 😁)
>
> (Especially if you know how to host LV2 plugin UIs in `winit` 😁)
> Love,
>
> - the author
> the author
# tek