summary refs log tree commit diff
path: root/src/components
Commit message (Collapse)AuthorAgeFilesLines
* Comply with GNOME HIG by ensuring our window can scale to a small sizeVika2024-08-231-126/+148
|
* Factor out the post editor UI into a separate componentVika2024-08-221-0/+489
| | | | | Now it's easy to use the same UI for sending a new post or editing an existing one (by loading it with `?q=source` and then comparing).
* SmartSummaryButton: un-asyncify and move summarization to a commandVika2024-08-221-21/+44
| | | | | | | What this command should do is construct a summarization request and return a future which would return chunks from the LLM. Perhaps this component will be asyncified in the future.
* SmartSummaryButton: ask parent component for textVika2024-08-221-31/+42
| | | | | 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-221-0/+84
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.