https://bugs.kde.org/show_bug.cgi?id=522302
--- Comment #2 from tarik <[email protected]> --- (In reply to Nate Graham from comment #1) > In fact we used to do exactly what you suggested. The result: people > complained that plasmashell took a long time to load. > > There's no winning here, unfortunately. The only real solution is to make > everything faster and use fewer resources. Which is a great idea! And it's > always happening as a baseline level. No single change will be a magic > bullet for that; it's just a slow drip of enhancements over time. > > As such, I don't think there's anything actionable for this Bugzilla ticket, > unfortunately. I understand, I didn't know that you had tried this in the past and received this kind of feedback. But what if this feature didn't come enabled by default, but was added as an optional choice under the "Effects" or "Appearance" section in System Settings? Users who want a fast boot could continue with the current system, but those who prioritize visuals like me could enable this option themselves. However, considering the issues of code complexity and technical maintenance burden that I mentioned, it seems much more logical to focus directly on just the Splash Screen logic instead of messing with the code of the panels. Because in the current working logic (ksplash), the system closes the splash screen the exact moment it starts the plasmashell process. However, the fact that plasmashell has started does not mean that panels, heavy widgets, applets, and desktop icons are completely rendered and ready. Since the splash screen closes early, we are left looking at just a blank wallpaper; it still takes 2-3 seconds for the panels to load up. That's why it feels like the splash screen doesn't fully serve its purpose. If the splash screen continued to stay on the screen until the panels, widgets, and desktop components were completely loaded and rendered in the background (or if there were such an option in the settings), the user wouldn't even see that rough loading phase at all. The moment the screen closed, the desktop would be 100% ready and in place. This "advanced splash screen synchronization" or "optional effect" option that I mentioned could make the desktop's initial boot quality feel much more premium. But on the other hand, it is true that the desktop loading really takes a long time. There are a lot of things I complain about regarding KDE, but let me not sidetrack the topic by bringing them up here. By the way, thank you for your response. -- You are receiving this mail because: You are watching all bug changes.
