Add tauri-plugin-prism to the Prism documentation #129
Replies: 3 comments
|
Hi there, This is not a bug, so I have converted it to a discussion. (We use issues for genuine bugs, not questions or general discussions.) Not a warning or anything, just a note. As for it, whichever you believe is more appropriate. Given it is not necessarily a language binding, I think integrations may be more appropriate, but if it turns into both, language bindings may be more preferable. This is a bit confusing since we've never had an integration like this before. I know someone was proposing Node.JS bindings (see #44) but understandably that has yet to be done. I am open to either at this point, given the novelty here. |
|
Appreciate you converting the issue into a discussion, this system is quite underused and so I tend to forget about it. Since the primary interface is typescript, I think adding it to the bindings section makes the most sense for now. If NodeJS bindings end up getting created and/or other integrations are maintained, we can reconsider. For what it's worth, once I have gotten the chance to test this out on iOS and Android, I plan to add it to the Tauri community plugins list. Prism seems like the most reliable way to do spoken output these days and the more people we can get to use it, the better. I will open a PR tomorrow. |
|
Sounds good, I look forward to it! |
Uh oh!
There was an error while loading. Please reload this page.
I built tauri-plugin-prism, a Tauri 2 plugin that exposes Prism speech and screen reader output to desktop and mobile applications with web frontends.
Thanks to the work you've done on this library, we are one step closer to making cross-platform audio based games that seemlessly run on every platform.
The plugin uses
prismerfor its native integration and provides a TypeScript API for speaking text, stopping speech, inspecting the selected backend, enumerating voices, and changing supported voice settings.Packages are available from:
Would you be open to listing this project in the Prism README? Since it is a Tauri integration called from Typescript and not a language binding alone, it could either appear in the existing Bindings table or in a small Integrations section.
If so, I am happy to submit the documentation PR once you confirm the preferred location and wording.
Thanks!
All reactions