KDE Plasma 6.3 Bringing A More Consistent Close Button, Other Last Minute Changes

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • skeevy420
    replied
    Originally posted by anda_skoa View Post
    I am not sure that is actually true.
    KWrite could be a different host application without any plugin support. I find that actually very likely as it reduces complexity over having all the plugin infrastructure and just not loading any.
    I just mean with how they look. Kate and KWrite are damn near identical. Everywhere. KWrite is just missing the plugins feature and the settings that it can add. I don't use KWrite due to it missing a single Kate plugin.

    That is not a bad idea.
    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.
    I just think it'd be neat if instead of everything having a per-app widget it would open up an embedded Widget attached to its Widget daemon. Terminals would have a Konsole daemon, KDE text editors could have a KText daemon . . . all because saving and opening in another program is too hard . . . but I also don't disagree with you regarding the difficulties different ones could have. Sending a text window, essentially an immutable datastream the second the tab is clicked to drag and drop, can't necessarily be treated the same as sending a terminal doing an rsync transfer that's logged in as a secondary user.

    ​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.
    You need to open up the different audio players and text editors to see what I mean. All their audio players have different interfaces, options, features. They're all distinct and different from one another. It's like comparing XMMS to Amarok. They're not the same things other than they happen to play music.

    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:


  • skeevy420
    replied
    Originally posted by QwertyChouskie View Post

    That sounds like a bug/unintended behavior that should be reported. Releasing the scrollbar should never do anything besides release the scrollbar.
    I've only noticed it happening on Firefox. Nothing else that I use has that much of a scroll bar to close button slippage zone or is a program where I'll use the scroll wheel or Page Up/Down to navigate. I've tried to replicate it with other programs but only happens with Firefox.

    AFAICT, it's an issue with the Firefox header bar design and why I run it with a title bar now. Accidental slippage closing hasn't happened a single time since I made that post which prompted me to switch to the system title bar to see what happens.

    Leave a comment:


  • QwertyChouskie
    replied
    Originally posted by skeevy420 View Post
    When scrolling windows up by clicking the scroll bar I have a bad habit of not unclicking until I'm over the close button and I've lost a lot of shit because of it.
    That sounds like a bug/unintended behavior that should be reported. Releasing the scrollbar should never do anything besides release the scrollbar.

    Leave a comment:


  • anda_skoa
    replied
    Originally posted by skeevy420 View Post
    With the text editors it's unnecessary since they're all Kate with less and less plugins enabled.
    I am not sure that is actually true.
    KWrite could be a different host application without any plugin support. I find that actually very likely as it reduces complexity over having all the plugin infrastructure and just not loading any.

    Originally posted by skeevy420 View Post
    I wish that drop-down, or rather slide in to cover all directions, was a function of KWin or Plasma or whatever. We could then pin a window to the screen's border and then hit a shortcut to pop it in or out so we can treat any program like Yakuake.
    That is not a bad idea.
    Could be suggested as a feature for KWin on the appropriate channels.


    Originally posted by skeevy420 View Post
    It would be nice if there was a way to move the terminal widget from program to program to program instead of it being a fixed widget per program.
    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.

    Originally posted by skeevy420 View Post
    A way to embed and debed a widgets. I suppose that could cover more than just terminal widgets.
    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.

    Originally posted by skeevy420 View Post
    The overlap with audio players is a different story since some have databases and libraries, some are bare bones, they have different interfaces, and they do things differently.
    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.

    Leave a comment:


  • bug77
    replied
    skeevy420 Reusability is at KDE Frameworks level. At an app level, everything goes.

    Leave a comment:


  • skeevy420
    replied
    Originally posted by mrg666 View Post

    Overlap is good in my opinion ... and it is unavoidable as this is an open project. The overlapping parts can be new grounds for growing new ideas. Either the ideas are transferred or the whole app is replaced. That happened so many times in the past. Plus, every person has different preferences, it is good to have options.
    For me it depends on the context. With the text editors it's unnecessary since they're all Kate with less and less plugins enabled. If they were a video game they'd be Easy/Medium/Hard modes. Terminals like Konsole and Yakuake have the same settings and abilities but their windows are drawn differently (floating vs dropdown). IMHO, how windows are drawn should be part of Wayland, KWin, Plasma, etc.

    I wish that drop-down, or rather slide in to cover all directions, was a function of KWin or Plasma or whatever. We could then pin a window to the screen's border and then hit a shortcut to pop it in or out so we can treat any program like Yakuake. Instead of Yakuake existing people could pin Konsole to the top. Less app overlap for more system functionality.

    Since I'm on the subject, there's also having the same terminal widget in a lot of KDE programs. It would be nice if there was a way to move the terminal widget from program to program to program instead of it being a fixed widget per program. Like, if Kate closes it'd offer the option to transfer its active terminal widget to a drop-down or Konsole window or if we open up Kate or KDevelop we can drag and drop our current terminal into their terminal widget area. A way to embed and debed a widgets. I suppose that could cover more than just terminal widgets.

    The overlap with audio players is a different story since some have databases and libraries, some are bare bones, they have different interfaces, and they do things differently. Having tangible differences applies to image and video players, too. They're not the same things being drawn differently or with the same things with different difficulty settings.

    Leave a comment:


  • Topolino
    replied
    Originally posted by Landway12 View Post
    It seems that the Ubuntu team really need to "kill their darlings" and jump on the KDE train.
    Predictability on quality and schedule is king. You probably underestimate how well the current setup works.

    Leave a comment:


  • Nth_man
    replied
    Originally posted by bug77 View Post

    Out of curiosity, I'm on Nvidia. You?
    Using Intel.

    Leave a comment:


  • sophisticles
    replied
    Originally posted by DumbFsck View Post
    Congrats on your top tier reading comprehension. If the guy said "I changed from Ubuntu to Kubuntu [...]" Would you have gotten it?

    Or do you think everyone that wants to share their experiences must take a few classes to fully understand what a display manager is, a compositor, layouting engine, widget framework, shell, desktop and finally desktop enviroent are all before making their first post?


    Or is it just that you can't see that other people are able to understand what you can't?

    As time passes you're becoming a worse and worse troll. Weak baits, etc.
    Reread what he said and pay note that he felt the need to change his comment to reflect that he was talking about Gnome vs KDE.

    His phrasing was atrocious as is you trying to stand up for him.

    Leave a comment:


  • ResponseWriter
    replied
    Originally posted by mrg666 View Post

    I have seen no Plasma crashes in a long time either.
    I hadn't for a long time, then today tried to add the audio widget to my desktop (wanted an easy way to switch outputs) and it crashed. The widget management stuff in general needs some improvement as it seems to freeze Plasma and the "Get New Widgets" window freezes a lot.

    Leave a comment:

Working...
X