codingbinary

And done

Thanks, I will look into it. But tomorrow at the earliest. Today I'm out to celebrate the last ever exam I just passed.

Except for 2 exceptions, only for interfacing with xlib, as the calls to rust-xlib involve raw pointers (because rust-xlib is just a plain c-binding wrapper around xlib).

The 2 exceptions are: loading of the config library. The config file is compiled to a dynamic lib at startup, and I need to read the symbol out of that library to access the configure function. The DynamicLibrary module is unfortunately unsafe. The second exception is in one of the default handler methods, managing the on-the-fly restart of the WM (akin to xmonad). This involves a call to execvp in the libc:: module, and therefore also unfortunately requiring an unsafe block (split into 2 unsafe block, for pointer handling and calling).

Xephyr is just for testing. You can run wtftw completely standalone when you use it in your .xinitrc for example.

It's still a bit buggy though. Works perfectly fine here. Been using it as my default WM for 2 weeks straight now. But some bugs do seem to creep up on other machines.

As soon as I figure out how to do that. But I need only minimal functionality, so I don't expect it to be _too_ difficult. I figured I should start with the Weston shell and figure it out from there.

As for the xlib stuff, I can't really write tests for that. But I will write a more extensive test suite for the core components, especially the ones in src/core.rs

For the methods in window_manager.rs, they often depend on the window system, but that shouldn't be a problem as I could simply insert a dummy interface.

Tests will follow. Last weeks were just filled with thesis and preparations for my last exam. So I used the coding for relaxation and kinda omitted the tests. I know, I know...behaviour.

Ok, for the dragging part I would have to come up with something, but theoretically, your desired features are possible. I just need some spare time to implement the layout plugins and come up with a good way to handle keyboard shortcuts in nested splits.

That's why I split it. The window system interface is pretty much done. The main module won't change by much.

95% of the work is done in the core module. The main module is merely for the executable and rarely changes.

I've split it up because the xlib (and future wayland) modules need to refer to the core as a library, so the main module has nothing to do there.

Though I admit that part of the reason is earlier attempts with dynamic libraries, but that was more hassle than it needed to be.

I could merge the core back into the main module, but I'll wait a bit until I do that, just to be sure.

Author here. I am sorry about the confusion. It happened later in the project when I split it into 3 components (4 as soon as I add Wayland support). I should probably mention that in the Readme.

Thank you.

The first part is merely a rough setup. Tutorial is unfinished. At the moment I am writing my thesis, but I'll try to do a few parts over the holidays.

Well, $100 million of apprenticeship grants isn't gonna cut it. The money would be better spent in developing the needed infrastructure to adopt the system. Skip state wide systems and adopt a nation wide system.

As for the "cost factor" for the companies...even if still at apprenticeship level, the people are working, even if it's just minor tasks in the first few months, so give them a damn salary. Here in Germany the average is about 700$/month on average, with salary increasing by about 50$ each year. Plus a decent chance to get a full time job at the same company after your apprenticeship is done.

The firms won't need to establish programs. The states will have to establish schools for that, not the firms.

Shouldn't the pay be good at Google? Or what are the rents over there? (Sorry, German here)

Exactly my thought.

Exactly. Most Germans accept nearly everything, except if it comes to their privacy. And I'd strongly support such a move.