dhorse2 / clipmdplus Goto Github PK

I decided it would, overall, be of higher value to select a widely used clipboard crate.
Connection and monitoring the OS clipboard has always been a separate concern from keeping the history and UI.

Here are the crates that were reviewed:

rust crates - clipboard
https://crates.io/search?q=clipboard

Rust Clipboard (short(ish) list)

Note: I'm not clear if the Linux OS Wayland/X11 tweaks used by ArBoard (and a few others) are needed or not.
If not, the regular clipboard-rs will is the best choice.

These all have the Wayland/Linux tweak.

https://crates.io/crates/arboard
The Wayland issue includes retaining clipboard contents on program exit.
GNU/Linux
The GNU/Linux implementation uses the X protocol by default for managing the clipboard but fear not because Wayland works with the X11 protocol just as well. Furthermore this implementation uses the Clipboard selection (as opposed to the primary selection) and it sends the data to the clipboard manager when the application exits so that the data placed onto the clipboard with your application remains to be available after exiting.

There's also an optional wayland data control backend through the wl-clipboard-rs crate. This can be enabled using the wayland-data-control feature. When enabled this will be prioritized over the X11 backend, but if the initialization fails, the implementation falls back to using the X11 protocol automatically. Note that in my tests the wayland backend did not keep the clipboard contents after the process exited. (Although neither did the X11 backend on my Wayland setup).

https://github.com/1Password/arboard
https://github.com/alacritty/copypasta
https://crates.io/crates/cli-clipboard
https://gitlab.com/timvisee/rust-clipboard-ext

Standard RUST Clipboard crates.

clipboard-rs
https://crates.io/crates/clipboard-rs
Dependencies
^5.2.0 clipboard-win 1 extra feature
Provides simple way to interact with Windows clipboard.
^0.25.0 cocoa
Bindings to Cocoa for macOS
^0.25 image
Imaging library. Provides basic image processing and encoders/decoders for common image formats.
^0.13.0 x11rb 1 extra feature
Rust bindings to X11

clipboard
https://crates.io/crates/clipboard
Dependencies
^2.1 clipboard-win
Provides simple way to interact with Windows clipboard.
^0.2 objc
Objective-C Runtime bindings and wrapper for Rust.
^0.1 objc-foundation
Rust wrapper for Objective-C's Foundation framework.
^0.1 objc_id
Rust smart pointers for Objective-C reference counting.
^0.3 x11-clipboard
x11 clipboard support for Rust.

rust-clipboard
https://github.com/aweinstock314/rust-clipboard
Dependencies:
^2.1 clipboard-win
Provides simple way to interact with Windows clipboard.
^0.2 objc
Objective-C Runtime bindings and wrapper for Rust.
^0.1 objc-foundation
Rust wrapper for Objective-C's Foundation framework.
^0.1 objc_id
Rust smart pointers for Objective-C reference counting.
^0.3 x11-clipboard
x11 clipboard support for Rust.

https://crates.io/crates/clipboard-ext

clipboard
https://docs.rs/clipboard/0.5.0/clipboard/
https://crates.io/crates/clipboard
https://docs.rs/clipboard/latest/clipboard/trait.ClipboardProvider.html

Rust Clipboard rejected:
https://docs.rs/clippers/latest/clippers/
https://crates.io/crates/clipboard-win
https://docs.rs/clipboard-win/latest/clipboard_win/formats/index.html
https://crates.io/crates/doe
https://github.com/dacap/clip
https://github.com/dacap/clip/wiki/API
https://github.com/dacap/clip/wiki#who-is-using-clip

More LInks:
https://stackoverflow.com/questions/65064854/rust-crossclip-print-type-of-clipboard?rq=3
https://github.com/aweinstock314/rust-clipboard
https://crates.io/crates/clipboard-ext
https://gitlab.com/timvisee/rust-clipboard-ext
https://github.com/aweinstock314/rust-clipboard
https://crates.io/search?q=clipboard
https://stackoverflow.com/questions/55545157/how-to-write-an-image-to-the-windows-clipboard-in-rust
http://www.ece.ualberta.ca/%7Eelliott/ee552/studentAppNotes/2003_w/misc/bmp_file_format/bmp_file_format.htm

Features are: OS (required?), History, Clipboard (no hist), Window, ProcMacros.
At lower detail level WindowTypes (ie egui, web), Specific macros and
crates could all be easily excluded in a clear (to the dev) manner.

It's a discussion topic for later releases.