https://bugs.kde.org/show_bug.cgi?id=15329
--- Comment #137 from Bob English <[email protected]> --- (In reply to Nate Graham from comment #135) > It's fundamentally infeasible for the window manager to track windows across > openings/closings without some metadata to help it. Apps will need to do > their part to provide this information. > > All of the existing approaches for doing this automatically rely on > unreliable heuristics such as the window title, which isn't guaranteed to be > the same when a window is opened again. Something tells me they could, and should though, as well as all making apps for all DE's, and as a superpower user with no developing skills but most basic HTML, CSS, and of course just enough Bash command language to use the terminal with notes and stuff open to help me not mess up. I am allthough very understanding of it all on a more conceptual level, an electronics engineer who made science grade Wave tech for R&D, like spectroscopy... and logic circuitry, and so in using computers since 1979, and what many of us understood what computers were capable of, and should do, how best to do it... and watched it go sideways anyhow, often mostly not for the better with big tech, and so I do have a good idea I'm sure others have thought of too, in order to fix a lot of stuff similar as to interoperability and so, more of a Linux standard procedure, than a specific module, with some and the idea based on some Star Trek tech, but also what already is done in ways within programs, I will for now call: "universal translator files". Just comma, line, glyph type lists and yes small programs and what not, but in basic a go between to translate stuff that differ in programing languages, but do essentially the same thing, but differing based on the differing methods those languages and modules do them: Example: All KDE apps can go through it to pass it's commands... to the translator, and it translates it to gnome, and all DEs to one and it to all compositors... that way without unifying Linux by using only one compositor and DE, like a monolith, still behave like one no matter what DE, compositor, apps are in use with fewer issues. The how I cannot help with much other than in concept, but if, and then once it is more like a project in development, I can help, at least with some pretty good critical and rational thinking skills. I know it doesn't quite help here and now, but it came to mind, and I think may be worthy for consideration, and if so should be addressed on a more general entity level, so maybe The FSF, Kernel developer space or wherever most appropriate, and I can hit them up on it once I know the best place to start, and who to run it by Some of it actually already exists; I'm sure, but it just needs to be in more of a standards and compliance (hated but helps) way, so any tips and feedback on that would be appreciated. And once in swing Ill get on trying to tackle my love hate relationship with most if not all spell checkers. ;>) -- You are receiving this mail because: You are watching all bug changes.
