summary refs log tree commit diff
path: root/src
Commit message (Collapse)AuthorAgeFilesLines
* SmartSummaryButton: ask parent component for textVika2024-08-222-38/+67
| | | | | On receving `smart_summary::Output::Start`, one must reply with `smart_summary::Input::Text(text)` to start the actual summarization.
* Factor out the smart summary buttonVika2024-08-222-71/+120
| | | | | | This is a little bit janky in my opinion, because it takes a reference to the buffer which contents its gonna be summarizing. In a perfect world, it would ask the parent component for the text.
* Display toasts on submitted posts and errorsVika2024-08-221-157/+178
| | | | | Success toasts also display a button to open the post in your browser of choice.
* Don't submit empty postsVika2024-08-201-0/+4
|
* Visibility selectorVika2024-08-201-21/+84
|
* Make the TextView scrollableVika2024-08-201-12/+19
|
* Send posts made in the post composerVika2024-08-203-6/+173
|
* Make the post composer asynchronousVika2024-08-202-12/+28
| | | | | This makes it able to execute unsendable futures, and unlocks ability for us to do asynchronous initialization and updates.
* Post composer UI prototypeVika2024-08-194-0/+351
Currently the UI does precisely nothing, but the ✨ Smart Summary button prints a message stating what it's supposed to do. The Post button currently just logs to the console, although ultimately it should send a message to a parent component or something. Perhaps even the composer UI itself should be a separate part that can provide an MF2-JSON document on a command.