What's the best way to get progress updates from rust into my frontend

[thejawker]

I'm am working on an idea where I'd like to share progress for a few situations:

• file processing, eg: file compression, bundling, moving etc
• file uploads
• audio playback (from within rust, reason is I need to support a large set of filetypes and compressing to mp3 is not an option)

It's important that the the progress is entity scoped, eg there might be a list of uploads/audio files and they should individually update.

What is the preferred way to get this type of progress data back to the client?

My first thought is the following:

1. client calls rust which returns a unique progress event name
2. client subscribes to this event name
3. rust keeps updating this periodically
4. client responds to the event and updates progress bar (or whatever it needs to update)
5. when done both do some cleanup

I'm thinking this should work, but I feel that there might be a better/cleaner/easier/more tauri type of approach, hence this question.

So far really digging tauri, thanks!

[abisar]

It's in the docs and its called Events. Here is another simple example of it:

In your JavaScript:

import {listen} from '@tauri-apps/api/event';
import {invoke} from '@tauri-apps/api/tauri';

// Set it to a variable if you want to unlisten later
listen('stuff-happened', (event) => {
  console.log(event);
});
invoke('do_stuff');

And then emit the event as much as you want in rust:

// Don't forget the required includes/definitions

#[tauri::command(async)]
fn do_stuff(window: Window) {
    let mut progress: u8 = 0;

    loop {
        window.emit("stuff-happened", Payload {message: progress.to_string()}).unwrap();
        if progress > 20 {break;};
        progress += 1;
    }
}

invoke is optional. As long as you have access to window, you can emit events to js. The above example emits all 21 events almost at the same time, but the idea remains the same in whatever async progress you're gonna do.

It's important that the the progress is entity scoped

You can separate them by id, event name and even window.

[thejawker]

Thank you so much @abisar for this example! This is kind of where my head was at as well. I think this should solve it.

It might be a useful package if abstracted right.