Originally posted by anda_skoa
View Post
That is not a bad idea.
Could be suggested as a feature for KWin on the appropriate channels.
Could be suggested as a feature for KWin on the appropriate channels.
You're the first person in four or five years that's said that. Every other time I've mentioned that it got shot down.
Transferring a session between processes is unfortunately not that trivial, e.g. handing over open file descriptors.
Easier for programs that can just serialize a state and deserialize it in the other instance.
Doable but more complicated so even programs that support moving sub windows between main windows can often do this just in one process.
For example you can drag Firefox tabs between windows of the same Firefox instance but can't between different ones, e.g. between windows of two Firefox profiles.
Probably also very OS dependent.
One options could be for all applications to be nested Wayland compositors and each component to be a Wayland client.
Then de-embed and/or re-embed would be disconnecting from the current compositor and connecting to the new one.
Easier for programs that can just serialize a state and deserialize it in the other instance.
Doable but more complicated so even programs that support moving sub windows between main windows can often do this just in one process.
For example you can drag Firefox tabs between windows of the same Firefox instance but can't between different ones, e.g. between windows of two Firefox profiles.
Probably also very OS dependent.
One options could be for all applications to be nested Wayland compositors and each component to be a Wayland client.
Then de-embed and/or re-embed would be disconnecting from the current compositor and connecting to the new one.

From your point of view they are all the most advanced of them with plugins disabled or not loaded.
It might be more complicated internally than you've considered.
It might be more complicated internally than you've considered.
Kate and KWrite are the same things. KWrite is basically Kate without the Plugins menu. Every advanced feature where someone goes "Well Kate has project support, git support, a terminal, yada yada" are all Plugins. Disable a few of those and Kate IS KWrite. They'll have the same interface, abilities, and features aside from advanced users having access to the Plugin menu for more features.
They should replace KWrite with Nota and disable a few Kate plugins to simplify it for first-time users. Nota looks like a GNOME program due to it being a Maui program, but it is minimal and fulfills the simple, easy-to-use function KWrite is supposed to accomplish while not being Kate Minus Minus . . . That's a Notepad++ joke.
Leave a comment: