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