6 ms·

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 p

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.

vog 12y ago
Is it really helpful to have different components of the same project in separate repositories? Are they really that independent? Four independent components for a single window manager seems a bit high to me. Regarding modularization, I tend to prefer Fowler's criterium that a component should contain code which is usually changed together. So, if you have one component where 95% change slowly and 5% change often, you should split it. However, if you have two components that you almost always have to change at the same time, you should merge them.
- codingbinary 12y ago
  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.
  - TheHydroImpulse 12y ago
    You could take advantage of having a single git repo for multiple cargo packages. This has worked extremely well for me. It was a lot easier having a single git repo to manage and control but still have separate packages for each of the different pieces. You could have the main package become the executable and have the core and various other packages in there, too.
    - tpaksoy 12y ago
      I've seen this done in many Rust repositories on Git. I would also suggest to look into this (single repo, multiple Cargo crates in seperate folders).
      - codingbinary 12y ago
        Thanks, I will look into it. But tomorrow at the earliest. Today I'm out to celebrate the last ever exam I just passed.
        rudolf0 12y ago
        Congratulations!
      - codingbinary 12y ago
        And done
Symmetry 12y ago
Wayland support Wow, nice to see a tiling window manager working on that.
- codingbinary 12y ago
  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.
- kragniz 12y ago
  loliwm is another one. https://github.com/Cloudef/loliwm https://github.com/Cloudef/loliwm

vog 12y ago

Is it really helpful to have different components of the same project in separate repositories? Are they really that independent? Four independent components for a single window manager seems a bit high to me. Regarding modularization, I tend to prefer Fowler's criterium that a component should contain code which is usually changed together. So, if you have one component where 95% change slowly and 5% change often, you should split it. However, if you have two components that you almost always have to change at the same time, you should merge them.

codingbinary 12y ago
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.
- TheHydroImpulse 12y ago
  You could take advantage of having a single git repo for multiple cargo packages. This has worked extremely well for me. It was a lot easier having a single git repo to manage and control but still have separate packages for each of the different pieces. You could have the main package become the executable and have the core and various other packages in there, too.
  - tpaksoy 12y ago
    I've seen this done in many Rust repositories on Git. I would also suggest to look into this (single repo, multiple Cargo crates in seperate folders).
    - codingbinary 12y ago
      Thanks, I will look into it. But tomorrow at the earliest. Today I'm out to celebrate the last ever exam I just passed.
      - rudolf0 12y ago
        Congratulations!
    - codingbinary 12y ago
      And done

Symmetry 12y ago

Wayland support Wow, nice to see a tiling window manager working on that.

codingbinary 12y ago
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.
kragniz 12y ago
loliwm is another one. https://github.com/Cloudef/loliwm https://github.com/Cloudef/loliwm