leyoda/softbuffer
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Updated rest of the code to use softbuffer name instead of swbuf

Browse source
This commit is contained in:
David Johnson 2022-12-22 18:43:54 -06:00
parent ddb1b9bfeb
commit 9023b096d7
6 changed files with 11 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

12
README.md
View file

@ -10,15 +10,15 @@ example, it occasionally segfaults on some platforms and is missing key features
icon. While it would be possible to add these features to minifb, it makes more sense to instead use the standard
window handling systems.
swbuf integrates with the [raw-window-handle](https://crates.io/crates/raw-window-handle) crate
Softbuffer integrates with the [raw-window-handle](https://crates.io/crates/raw-window-handle) crate
to allow writing to a window in a cross-platform way while using the very high quality dedicated window management
libraries that are available in the Rust ecosystem.
What about [pixels](https://crates.io/crates/pixels)? Pixels accomplishes a very similar goal to swbuf,
What about [pixels](https://crates.io/crates/pixels)? Pixels accomplishes a very similar goal to Softbuffer,
however there are two key differences. Pixels provides some capacity for GPU-accelerated post-processing of what is
displayed, while swbuf does not. Due to not having this post-processing, swbuf does not rely on the GPU or
displayed, while Softbuffer does not. Due to not having this post-processing, Softbuffer does not rely on the GPU or
hardware accelerated graphics stack in any way, and is thus more portable to installations that do not have access to
hardware acceleration (e.g. VMs, older computers, computers with misconfigured drivers). swbuf should be used over
hardware acceleration (e.g. VMs, older computers, computers with misconfigured drivers). Softbuffer should be used over
pixels when its GPU-accelerated post-processing effects are not needed.
@ -31,7 +31,7 @@ from the minifb library to do platform-specific work.
Platform support:
==
Some, but not all, platforms supported in [raw-window-handle](https://crates.io/crates/raw-window-handle) are supported
by swbuf. Pull requests are welcome to add new platforms! **Nonetheless, all major desktop platforms that winit uses
by Softbuffer. Pull requests are welcome to add new platforms! **Nonetheless, all major desktop platforms that winit uses
on desktop are supported.**
For now, the priority for new platforms is:
@ -55,7 +55,7 @@ For now, the priority for new platforms is:
Example
==
```rust,no_run
use swbuf::GraphicsContext;
use Softbuffer::GraphicsContext;
use winit::event::{Event, WindowEvent};
use winit::event_loop::{ControlFlow, EventLoop};
use winit::window::WindowBuilder;

2
examples/animation.rs
View file

@ -2,7 +2,7 @@ use instant::Instant;
#[cfg(not(target_arch = "wasm32"))]
use rayon::prelude::*;
use std::f64::consts::PI;
use swbuf::GraphicsContext;
use softbuffer::GraphicsContext;
use winit::event::{Event, WindowEvent};
use winit::event_loop::{ControlFlow, EventLoop};
use winit::window::WindowBuilder;

2
examples/fruit.rs
View file

@ -1,5 +1,5 @@
use image::GenericImageView;
use swbuf::GraphicsContext;
use softbuffer::GraphicsContext;
use winit::event::{Event, WindowEvent};
use winit::event_loop::{ControlFlow, EventLoop};
use winit::window::WindowBuilder;

2
examples/winit.rs
View file

@ -1,4 +1,4 @@
use swbuf::GraphicsContext;
use softbuffer::GraphicsContext;
use winit::event::{Event, WindowEvent};
use winit::event_loop::{ControlFlow, EventLoop};
use winit::window::WindowBuilder;

2
examples/winit_wrong_sized_buffer.rs
View file

@ -1,4 +1,4 @@
use swbuf::GraphicsContext;
use softbuffer::GraphicsContext;
use winit::event::{Event, WindowEvent};
use winit::event_loop::{ControlFlow, EventLoop};
use winit::window::WindowBuilder;

2
src/wayland/buffer.rs
View file

@ -28,7 +28,7 @@ pub(super) struct WaylandBuffer {
impl WaylandBuffer {
pub fn new(shm: &wl_shm::WlShm, width: i32, height: i32, qh: &QueueHandle<State>) -> Self {
let name = unsafe { CStr::from_bytes_with_nul_unchecked("swbuf\0".as_bytes()) };
let name = unsafe { CStr::from_bytes_with_nul_unchecked("softbuffer\0".as_bytes()) };
let tempfile_fd = memfd_create(name, MemFdCreateFlag::MFD_CLOEXEC)
.expect("Failed to create memfd to store buffer.");
let tempfile = unsafe { File::from_raw_fd(tempfile_fd) };