Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggestion to have xmonad/dwm configuration #2

Open
Raj2032 opened this issue Aug 21, 2023 · 14 comments
Open

Suggestion to have xmonad/dwm configuration #2

Raj2032 opened this issue Aug 21, 2023 · 14 comments
Labels
help wanted Extra attention is needed

Comments

@Raj2032
Copy link

Raj2032 commented Aug 21, 2023

Would be kinda cool to have an easy way to config your entire project by modifying the source code, similarly to how xmonad and dwm does it. This gives the user much more control.

@Walker-00
Copy link
Owner

Yea I've plan for that to implement in v0.0.5 or something, when I've completely rewritten sswm's x window manager in x11rb. Thanks for your suggestion.

@Walker-00 Walker-00 added the help wanted Extra attention is needed label Aug 21, 2023
@mustardfrog
Copy link
Contributor

I always had a mix feeling about the suckless philosophy. (i.e modifying the source code, patching third party source code just to have some basic functionalities).

I mean you can still edit this source code technically, since you have to compile the project to install and use it.

And think about it again. Rust is famous for slow compilation. Do you really want to re-compile in RUST every time you made a change??

@Walker-00
Copy link
Owner

I always had a mix feeling about the suckless philosophy. (i.e modifying the source code, patching third party source code just to have some basic functionalities).

I mean you can still edit this source code technically, since you have to compile the project to install and use it.

And think about it again. Rust is famous for slow compilation. Do you really want to re-compile in RUST every time you made a change??

That also right, I think I might have to write an interpreted language to config it when I have free times.

@Walker-00
Copy link
Owner

I always had a mix feeling about the suckless philosophy. (i.e modifying the source code, patching third party source code just to have some basic functionalities).
I mean you can still edit this source code technically, since you have to compile the project to install and use it.
And think about it again. Rust is famous for slow compilation. Do you really want to re-compile in RUST every time you made a change??

That also right, I think I might have to write an interpreted language to config it when I have free times.

Or maybe should I use two method two config, One is by changing extra source code file and One is the Yaml file.

@mustardfrog
Copy link
Contributor

Sticking with just one method is good enough. Consistency is key.

And i was also a bit skeptical about the project vision, which is to make wm for both X and Wayland, which is not very consistent imo.

README states that "Wayland version is buggy", but X version still has huge amount of bugs and lacks a lot of core features of a wm.

I suggest to focus on just one and make it good. I recommend to separate X and Wayland like i3 and sway (you don't have to do it btw)

@mustardfrog
Copy link
Contributor

If you don't want to separate them, you should remove the word "minimal" from the project.

I don't mean to be rude, but let just say i do care about minimalism and want to try sswm, I have to install both X server and wayland related utilities.

so there is just one useless windows manager sitting on my computer doing nothing.

@Walker-00
Copy link
Owner

If you don't want to separate them, you should remove the word "minimal" from the project.

I don't mean to be rude, but let just say i do care about minimalism and want to try sswm, I have to install both X server and wayland related utilities.

so there is just one useless windows manager sitting on my computer doing nothing.

Yea I'll in about version 0.0.3 or 0.0.4

@mustardfrog
Copy link
Contributor

Ok. very cool.

Quick question. is the spelling in the config.rs, normal_bordar and focused_bordar intentional??

Does it just mean border and you don't want naming conflict?

@Walker-00
Copy link
Owner

Ok. very cool.

Quick question. is the spelling in the config.rs, normal_bordar and focused_bordar intentional??

Does it just mean border and you don't want naming conflict?

normal_border is the border for window when it's not focused and yea like that, yea I miss spelled those :3

@Walker-00
Copy link
Owner

And You should ask those in other issue or in some social media, Cuz asking in not related issue is maybe some kinda weird, not being rude BTW.

@mustardfrog
Copy link
Contributor

my bad

@Walker-00
Copy link
Owner

nah man just a suggestion

@Raj2032
Copy link
Author

Raj2032 commented Aug 27, 2023

@Walker-00 No worries mate and thank you mate for taking my suggestion :), sorry for the late response, I completely missed out on the notifications for some odd reason.

Regarding this suggested feature, would it support both wayland and x11?

I can see another Rust created projects does this as well:

https://github.com/mahkoh/jay
https://github.com/sminez/penrose

@Raj2032
Copy link
Author

Raj2032 commented Aug 27, 2023

@Walker-00 Hey man, regarding my suggested feature, I was thinking like I would want to suggest possibly the user codiing their config file in the main.rs (like a regular cargo project) and the user just imports the library as with a regular cargo project, rather than how dwm does it by getting the user to code in the config.h file afaik?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

3 participants