Good list, I put some time in on it today. Most of it landed in v0.7.0, which is live now on Copr and PyPI:
Multi-select, fully fleshed out. You were right that End/Kill alone was half a feature. A multi-selection now also does Suspend / Resume, Set priority, and Copy PIDs / paths / command lines and the copy puts one value per line on the clipboard, just as you expected. Signalling and renice still skip processes you don’t own; copy works across the whole selection since it’s read-only.
The grouping problem. This was your sharpest point: with everything split into User and System groups, you could never sort the whole list by CPU and see the heaviest tasks at the top. There’s now a View menu, grouped (as before), Flat (all), User only, and System only. Flat collapses everything into one list, so sorting by CPU finally floats the hottest process from any user straight to the top. Your choice is remembered between runs.
Compact density: Compact now tightens the row padding only and leaves the text at full size.
Search highlight. Also fixed: the highlighted match was drawn slightly high and nudged the row out of line. It’s now vertically centered like every other cell, in both densities.
The one thing I held back on is Properties / Open file location for a whole multi-selection.
“always have the advanced user in mind” I did my best!
Search filter / highlighted entries still are NOT aligned correctly and the name of a process is not positioned to the far left of the column (it never was iirc).
Buttons at the top are “destroyed” if window is rather small. There already is a menu “View”, why not put the “Compact” button in there as well. The “Compact” button also does not toggle state, only text (not optimal UI design).
The “View” dropdown should be renamed “Grouping” it is confusing with the “View” menu which exists at the same time. Maybe also move the “Grouping” into the menu
Offer an Option in “View” if these two buttons should be shown on the UI, I don’t need them there, I won’t switch “Compact”, “Grouping” and “Columns” around, once the GUI is configured as required.
I think we also need an option / toggle to “collapse” the navigation bar on the left, as the Win11 task manager has. It makes no sense to save so much space on the right to get a decent and “dense” layout / design, when the left part of the windows is wasting space at the same time (it’s using a non-standard font size as well, much too big if you ask me). Maybe collapse down to some icons at least or make the nav bar resizable. I could live with only “Pro”, “Per” and “Sta” being visible.
This screenshot is showing some of the issues from above (indentation, destroyed buttons, space allocation, process name alignment etc.)
Why is no other person suggestion features here? o)
I have another one..
The XFCE task manager has a “second” graph for the memory display, it shows the virtual memory / swap usage (the area below the mouse pointer). That would be nice to have in LPM as well!
Hello, please also keep up industry standards.. o) The two buttons in the top left are everything else but any kind of proven UI standard. I would also print full path for “source” and “destination” folders. In serious scenarios, you have multiple folders with the same name (in testing, stage, production e.g.), relying on the name only to summarize / monitor a copy operating is not enough. If you have a dedicated thread about this software, let us know.
Regarding your Win10 style graphs, yes.. there might be things to steal from elsewhere. o) I’m am not entirely happy yet with the LPM graphs. The Win10 graphs are thinner, they have a higher resolution if the line in the graph is not that bold and “neon” style. The XFCE task manager with that blue and green graph also uses a thin line for the graph, you can see spikes much better that way.
This is a Win10 task manager graph, also thin lines.. just saying! o))
Thanks again, tbone genuinely for all the feedback and for taking the time to share it. It’s helped polish things a lot.
On the UI-standards point: I don’t disagree that there’s a whole design language worth respecting. Some of it is also taste — the graph “glow” and the nav rail are deliberate calls I happen to like — and reasonable people land in different places on that. Where we differ, I’m comfortable with.
Realistically, though, I’m out of runway on this for a while. Between time constraints and everything else on my plate, I’m going to leave Lindoze as-is for now and let it breathe. It’s totally open license and all the source is in git — so if anyone else wants to redo the UX, the door’s wide open and I’d be genuinely curious to see it.
Eventually v1.0 but I have some personal life stuff at the moment. I should be able to get back to it in a few weeks though, maybe a month. I enjoy working on it, so I’ll pick it up when I can for sure.
