Skip to content

Commit

Permalink
blog tweaks
Browse files Browse the repository at this point in the history
  • Loading branch information
willmcgugan committed Sep 8, 2024
1 parent 5318167 commit ef0442f
Show file tree
Hide file tree
Showing 2 changed files with 12 additions and 4 deletions.
4 changes: 4 additions & 0 deletions docs/blog/posts/anatomy-of-a-textual-user-interface.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,6 +9,10 @@ authors:

# Anatomy of a Textual User Interface

!!! note "My bad 🤦"

The date is wrong on this post—it was actually published on the 2nd of September 2024.
I don't want to fix it, as that would break the URL.

I recently wrote a [TUI](https://en.wikipedia.org/wiki/Text-based_user_interface) to chat to an AI agent in the terminal.
I'm not the first to do this (shout out to [Elia](https://github.com/darrenburns/elia) and [Paita](https://github.com/villekr/paita)), but I *may* be the first to have it reply as if it were the AI from the Aliens movies?
Expand Down
12 changes: 8 additions & 4 deletions docs/blog/posts/textual-serve-files.md
Original file line number Diff line number Diff line change
@@ -1,14 +1,14 @@
---
draft: false
date: 2024-08-30
date: 2024-09-08
categories:
- DevLog
authors:
- darrenburns
title: "Improving Textual apps running in the browser"
title: "Towards Textual Web Applications"
---

In this post we'll look at some new functionality available in Textual apps which are being accessed via a browser and how it helps provide a more equal experience across platforms.
In this post we'll look at some new functionality available in Textual apps accessed via a browser and how it helps provide a more equal experience across platforms.

<!-- more -->

Expand Down Expand Up @@ -51,7 +51,7 @@ When running a Textual app in the terminal, getting a file into the hands of the

Run that same app in the browser however, and we have a problem. If you simply write the file to disk, the end-user would need to be able to access the machine the app is running on and navigate the file system in order to retrieve it. This may not be possible: they may not be permitted to access the machine, or they simply may not know how!

The new [`App.deliver_text`](https://textual.textualize.io/api/app/#textual.app.App.deliver_text) and [`App.deliver_binary`](https://textual.textualize.io/api/app/#textual.app.App.deliver_binary) methods are designed to let developers get files into the hands of end users, regardless of whether the app is being accessed via the browser or a terminal.
The new [`App.deliver_text`][textual.app.App.deliver_text] and [`App.deliver_binary`][textual.app.App.deliver_binary] methods are designed to let developers get files into the hands of end users, regardless of whether the app is being accessed via the browser or a terminal.

When accessing a Textual app using a terminal, these methods will write a file to disk, and notify the `App` when the write is complete.

Expand Down Expand Up @@ -80,3 +80,7 @@ This streaming process involves continuous delivery of encoded chunks of the fil
## The result

These new APIs close an important feature gap and give developers the option to build apps that can accessed via terminals or browsers without worrying that those on the web might miss out on important functionality!

## Found this interesting?

Join our [Discord server](https://discord.gg/Enf6Z3qhVr) to chat to myself and other Textual developers.

0 comments on commit ef0442f

Please sign in to comment.