summary refs log tree commit diff
path: root/src/lib.rs
Commit message (Collapse)AuthorAgeFilesLines
* Gettextize and add Russian translationVika2024-09-041-10/+11
| | | | | | This is a very shitty translation, but it can be improved later. I added it mostly as a test for translations working correctly, since I know Russian and might as well translate the app into the language.
* Proper main menu iconVika2024-08-251-0/+1
|
* Add licenseVika2024-08-251-0/+2
|
* Signing out of the app and the About dialogVika2024-08-251-4/+60
|
* Fix stuck buttonsVika2024-08-251-1/+3
|
* Use a provided SoupSession for MicropubVika2024-08-251-3/+7
|
* Simplify the main component a lotVika2024-08-251-130/+93
| | | | | Uses the macro again, tries to store only the relevant parts in enums (i.e. the Micropub client, which requires a token).
* Don't use an extraneous Box for the spinnerVika2024-08-251-8/+2
|
* Properly mount loading widgetsVika2024-08-251-0/+5
| | | | Whoops
* "Better" error handling from libsecretVika2024-08-251-33/+78
| | | | | | | | I had to commit a minor safety crime (but not an unsoundness crime) to get libsecret's `glib::Error` to be compatible with `glib::Error` from the newer GLib version. This could be dropped later when libsecret updates.
* Bring child components onto the top-level and use a single SoupSessionVika2024-08-251-36/+36
| | | | | | | This helps unify HTTP-related settings in one place. In Relm4 Matrix chatroom, it was said that deconstructing child components makes little sense in terms of optimizations.
* Prototype for signing in with IndieAuthVika2024-08-251-36/+118
| | | | | | 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.
* Very crude mock-up for an authentication screenVika2024-08-241-62/+146
| | | | | | 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.
* Tags in postsVika2024-08-231-1/+4
|
* Comply with GNOME HIG by ensuring our window can scale to a small sizeVika2024-08-231-1/+1
|
* Factor out the post editor UI into a separate componentVika2024-08-221-367/+46
| | | | | 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).
* Use a nice icon for the post buttonVika2024-08-221-1/+3
|
* SmartSummaryButton: un-asyncify and move summarization to a commandVika2024-08-221-10/+20
| | | | | | | 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-7/+25
| | | | | 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-71/+36
| | | | | | 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-201-6/+65
|
* Make the post composer asynchronousVika2024-08-201-10/+21
| | | | | This makes it able to execute unsendable futures, and unlocks ability for us to do asynchronous initialization and updates.
* Post composer UI prototypeVika2024-08-191-0/+302
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.