@csepp Bemenu/dmenu is slow and solutions have been discussed. A couple of solutions have been proposed including adding a server/client architecture to bemenu.
The "just write a new widget gui" is a new one. It should not be hard to add your own custom dmenu/bemenu gtk implementation - just implement all the command line args sxmo requires and edit `sxmo_dmenu.sh` to use it systemwide.
The "just write a new widget gui" is a new one. It should not be hard to add your own custom dmenu/bemenu gtk implementation - just implement all the command line args sxmo requires and edit `sxmo_dmenu.sh` to use it systemwide.
@csepp I just tested nmtui on my pinephone. It only works if you have the screen rotated. The script should probably do this for you before launching nmtui. Like the bemenu/dmenu issue, no one has sent a patch =/. nmtui was selected over nm-applet cause it's easy to code in and has minimal dependancies. Most people just prefer bemenu/dmenu. If they have an enterprise setup, they just use networkmanager's command line. A sxmo-userscript for configuring enterprise would be cool.
@csepp By the way, Sxmo is not a suckless project. We like some of suckless's ideas/programs but when someone has coded something that is a complex solution because the problem is complex, we have adopted if it has clear advantages. Ie sway support. Moreover we got better touch support into sway and bemenu thanks to @stacyharper
The reason for these issues is no one has gotten around to coding it not cause we have some philosophy we cling to.
The reason for these issues is no one has gotten around to coding it not cause we have some philosophy we cling to.
@csepp @stacyharper
We have listened to criticism of using posix shell as the language. Posix shell isn't my favorite language but any suggestions of "this is a bad language for this" should have a patch attached that shows the problem being solved better in a different language.
For context, our power management used to be written in C. I thought our problems would be solved in rewriting with shell script and I attached code that you see today.
We have listened to criticism of using posix shell as the language. Posix shell isn't my favorite language but any suggestions of "this is a bad language for this" should have a patch attached that shows the problem being solved better in a different language.
For context, our power management used to be written in C. I thought our problems would be solved in rewriting with shell script and I attached code that you see today.
@csepp @stacyharper I dont know about accessibility but I do think it's important and I think that's a fair critique. What is the link to the gtk dmenu you mentioned? Like I said, it should not be too hard to use it system-wide and implementing the required flags shouldnt be too hard.
@csepp @stacyharper We have been looking to split up sxmo-utils for a while now and if you think "I want to rewrite this part" - I would start with splitting up sxmo-utils. Multiple people have talked about it but no one has written a plan. We are open to making sxmo-utils more modular so it's easier to rewrite and replace parts of it in your favorite language. As it exists now, we are very prone to feature creep.
@csepp @stacyharper https://todo.sr.ht/~mil/sxmo-tickets/470
I opened an issue. Feel free to ask for help in #sxmo irc channel on OFTC or post in that issue.
I opened an issue. Feel free to ask for help in #sxmo irc channel on OFTC or post in that issue.
@csepp @stacyharper Power management should be discussed in pmaports as they can detail how it's done in phosh. I havent used phosh in forever.
Please open an issue on the tracker here:
https://gitlab.com/postmarketOS/pmaports
Feel free to tag me @anjandev on gitlab and we can discuss how to solve this issue.
Please open an issue on the tracker here:
https://gitlab.com/postmarketOS/pmaports
Feel free to tag me @anjandev on gitlab and we can discuss how to solve this issue.
- replies
- 0
- announces
- 0
- likes
- 0