| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
The code is really janky and unpolished, the error handling is
TERRIBLE, and I think I can't publish it like this. This'll need a
refactor, but it'll come tomorrow.
|
| |
|
|
|
|
| |
This saves memory by dropping unneeded components. Once the app
changes state, it can simply drop the unnecessary component, such as
the login screen, to save memory.
|
| | |
|
| | |
|
| |
|
|
|
| |
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).
|
| | |
|
| |
|
|
|
|
|
| |
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.
|
| |
|
|
|
| |
On receving `smart_summary::Output::Start`, one must reply with
`smart_summary::Input::Text(text)` to start the actual summarization.
|
| |
|
|
|
|
| |
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.
|
| |
|
|
|
| |
Success toasts also display a button to open the post in your browser
of choice.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
This makes it able to execute unsendable futures, and unlocks ability
for us to do asynchronous initialization and updates.
|
|
|
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.
|
