Language Selection

English French German Italian Portuguese Spanish

Where’s the KDE4 Desktop?

Filed under
KDE

Before I come to the content please bear in mind: This is just my personal impressions from the 10/15 minutes I played with the current KDE4 desktop yesterday. I’m completely aware that there’s still 2 months of work happening and that KDE 4.0 is not primarily targeted at the broad user base that KDE4 is. Also I only have kdebase,kdesdk and kdevelop checked out, so I can’t say how the other modules are..

Still I think the Desktop is not in the shape I would’ve liked to see it for the 4.0 release. We do have a desktop with a wallpaper and this desktop-widget-thingie. First thing I noticed after trying the analog clock example is that the drop-down box is not xinerama aware. That is the widget itself is on the second screen (have them side by side) in the top-left corner, but the content of the box appears on the first in the top-left corner (2nd is left of 1st). Another thing is that the clock is somehow cropped when I switch from Desktop to one of the panel-types, it seems as if there’s some leftover from the round shape of the analog clock thats covering the left parts of the digital display.

Then tried to run some kde4 apps...

MOre Here




Aaron J. Seigo: xinerama and plasma

so andreas pakulat notes that plasma doesn't work with xinerama very well at the moment. perhaps that's because none of the developers are using it on such a system at the moment. "humorously" i still don't have such a system to play with either. it is "cute" that andreas picked on a UI element that isn't even going to be in the final release; it is cool that he's using testing features (the form factor drop down) to find issues, though, since that's what they are there for. =)

and so, andreas concludes, that with some other apps crashing for him he's not going to "eat the dogfood" until 4.1. that's unfortunate. why? because that's precisely how we can ensure that things don't get better. so what to do?

here are my thoughts:

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

More in Tux Machines

Security Leftovers

10 hot Android smartphones that got price cuts recently

With numerous smartphone getting launched each month, brands always adjust prices to give slightly competitive edge to older smartphone models and also to clear inventories. Here are 10 smartphones that got price cuts recently. Read more

Debian and Ubuntu News

  • Debian Project News - July 29th, 2016
    Welcome to this year's third issue of DPN, the newsletter for the Debian community.
  • SteamOS Brewmaster 2.87 Released With NVIDIA Pascal Support
  • Snap interfaces for sandboxed applications
    Last week, we took a look at the initial release of the "portal" framework developed for Flatpak, the application-packaging format currently being developed in GNOME. For comparison, we will also explore the corresponding resource-control framework available in the Snap format developed in Ubuntu. The two packaging projects have broadly similar end goals, as many have observed, but they tend to vary quite a bit in the implementation details. Naturally, those differences are of particular importance to the intended audience: application developers. There is some common ground between the projects. Both use some combination of techniques (namespaces, control groups, seccomp filters, etc.) to restrict what a packaged application can do. Moreover, both implement a "deny by default" sandbox, then provide a supplemental means for applications to access certain useful system resources on a restricted or mediated basis. As we will see, there is also some overlap in what interfaces are offered, although the implementations differ. Snap has been available since 2014, so its sandboxing and resource-control implementations have already seen real-world usage. That said, the design of Snap originated in the Ubuntu Touch project aimed at smartphones, so some of its assumptions are undergoing revision as Snap comes to desktop systems. In the Snap framework, the interfaces that are defined to provide access to system resources are called, simply, "interfaces." As we will see, they cover similar territory to the recently unveiled "portals" for Flatpak, but there are some key distinctions. Two classes of Snap interfaces are defined: one for the standard resources expected to be of use to end-user applications, and one designed for use by system utilities. Snap packages using the standard interfaces can be installed with the snap command-line tool (which is the equivalent of apt for .deb packages). Packages using the advanced interfaces require a separate management tool.
  • Ubuntu 15.10 (Wily Werewolf) Reaches End Of Life Today (July 28)
  • Ubuntu MATE 16.10 Yakkety Yak Gets A Unity HUD-Like Searchable Menu
    MATE HUD, a Unity HUD-like tool that allows searching through an application's menu, was recently uploaded to the official Yakkety Yak repositories, and is available (but not enabled) by default in Ubuntu MATE 16.10.

Tablet review: BQ Aquaris M10 Ubuntu Edition

As employees have become more and more flexible in recent years thanks to the power and performance of mobile devices, the way we work has changed dramatically. We frequently chop and change between smartphones, tablets and laptops for different tasks, which has led to the growth of the hybrid market – devices such as Microsoft’s Surface Pro 3 and Apple’s iPad Pro – that provide the power and functionality of a laptop with the mobility and convenience of a tablet. Read more