#winapi #window-manager #windows

dgews

Easy multithreaded toy windowing system for learning purposes only

17 releases

0.1.5 Nov 9, 2022
0.1.4 Oct 29, 2022
0.0.15 Oct 18, 2022
0.0.14 Sep 22, 2022

#434 in GUI

Download history 1/week @ 2024-03-09 83/week @ 2024-03-30 22/week @ 2024-04-06

60 downloads per month

MIT/Apache

110KB
2K SLoC

DGEWS

DGEWS DGEWS

DGEWS is a simple multithreaded toy windowing system for only learning purposes.

[dependencies]
dgews="0.1.4"

DGEWS is an ordinary window manager for only Windows users. It is pretty simple and straightforward so that anyone can understand and sometimes learn something from it. Indead, my goal is actually to learn the cycle of programming a practical crates and the developement of them.


Usage

DGEWS usues the c++ win32 api library wrapper winapi to build its windows. Therefore, anyone else except for Windows OS users cannot use this crate. Currently, this crate is not stable and crashes sometimes, that is why it is better not to use it in production (though I think nobody will use it while winit crate is ready to use). But, if someone wants to use some of its features in their own projects, just take it as I have stated that it is only for educational purposes.


Example

Manager is a central point of this crate: it processes everything and users retrieve the event messages from it. Moreover, window or windows are created with that. The run() method accepts a closure that must be called in each event and users will be given events, the manager itself as well as the control flow of that main events loop

extern crate dgews;
use dgews::prelude::*; // prelude module contains everything

fn main() {
    let mut manager = Manager::new(WindowBuilder::default()
            .with_title("DGEWS Window")
            .with_dimensions(800, 640)
            .with_theme(Theme::Dark)
            .with_resizable(true))
        .add_window("Hooray", WindowBuilder::new()
            .with_title("Finally")
            .with_dimensions(400, 300)
            .with_theme(Theme::Dark)
            .with_pos(700, 700));

    manager.run(|events, control_flow, manager| {
        match events {
            Events::WindowEvents { id, event } => match event {
                WindowEvents::Create => println!("[INFO]: a new window with id: {} has been created", id),

                WindowEvents::Close => {
                    println!("[INFO]: a window with id: {} has been closed", id);
                    *control_flow = ControlFlow::Exit; // to exit with panicing, use ControlFlow::ExitWithCode(<your number>) instead.
                },

                WindowEvents::SetFocus => println!("[INFO]: window with id: {} gained the focus", id),

                WindowEvents::LostFocus => println!("[INFO]: window with id: {} Lost the focus", id),

                _=> {}
            },

            Events::MouseEvents { id: _, event } => match event {
                MouseEvents::MouseMove { x, y, last_x, last_y, dx, dy } => {
                    println!("[INFO]: mouse moved in the window with id {}: x={}, y={}, last_x={}, last_y={} dx={} dy={};", manager.window().unwrap().get_id(), x, y, last_x, last_y, dx, dy);
                },
                
                _=> {}
            }

            _=> *control_flow = ControlFlow::Continue,
        }

        if manager.get_key(Key::ESCAPE) == Action::Release {
            println!("[INFO]: program is exiting");
            *control_flow = ControlFlow::Exit;
        }
    });
}

Features

current features

  • Multithreaded: windows have their own threads and they send messages from there so that when the user is interacting, windows will be still refreshing without waiting for the user to finish their event;
  • Winit stylish style: when I saw the winit crate first time, I really liked it for its structure. Thus, I decided to make something that resembles it;
  • Icons: users can use their own icons;
  • Themes: there is now only light and dark themes;
  • Ready events processing: it actually needs some work there so do not hestitate if you have any suggestions or ideas;
  • Easy: a glance of attention to the documentation is enough to get the hang of everything;
  • HasRawWindowHandle and HasRawDisplayHandle traits are implemeneted so that you can use them with other crates such as wgpu-rs;

Not implemented yet (in other words features)

  • Not ready yet: it is only in beta mode;
  • System keys error: I don't know why but some system keys such as Alt key are not working properly. In order to get Action::Press you have to press it twice!;
  • Not cross-platform: I have used the Windows api crate, so no cross-platform support 😔;

plans

  • Better documentation: I think it has 'pretty nice' documentation. But still there is more to make it even better and more user-friendly.
  • Fix the bugs: I am working on the issues like with the system keys or the window not opening,

Contributions

Everyone is welcome who are willing to contribute even to the documentation. Thanks in advance. Contact me via:


I am a student of a lyceum that is why I think you won't get the response immediately, however, I will try my best to reply back as soon as possible.


Licenses

  1. The MIT License
  2. The APACHE 2.0 License

Dependencies

~71–295KB