Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.

KDE4: Mockup Sources

Skip to first unread message

Leen Shonerd

Dec 7, 2023, 10:12:15 PM12/7/23
Mockups can be used to design the visual layout of each screen of an application, without writing code. The mockup toolkit is provided as an Inkscape SVG with each Building Block UI element and sample mocked applications.

KDE4: Mockup sources
Download File

Most VDG discussions start out informally in the real-time chatroom mentioned earlier. Once there is general agreement in the real-time chat, the discussion moves to a GitLab task. Our goal is to open the discussion to include developers, and make the proposal more concrete using images and mockups.

Our default "Breeze" visual style is undergoing many changes as part of the "Breeze Evolution" project. If you would like to submit mockups for our consideration, use the new New Figma-based Breeze SVG Kit have the most updated graphics for your mockups. This helps our developers visualize your design ideas better.

Raptor will load the Plasma DataEngines through an Interface to gain access to the DataSources. By specifying these interface for Raptor, and a plugin handler, others can write their own plugins with datasources and -engines and add it in Raptors configuration. Raptor then tells the plugins to deliver data via the interface (updateData or sthg) and the plugin sends these data in the form that it fits through the interface into it.

Setting the latter to "none" will remove any desktop integration. However, it will remove native KDE open/save dialogs, too! "kde" will bring back an old KDE3 style and "kde4" is the default setting on openSUSE and is the one which loads the oxygen mockup and native open/save dialog.

Long press will work there as well, but we wanted to make the multi-selection discoverable for everyone, so we decided to include checkboxes as an alternative for those who are not used to long press. This is just an early mockup, though, so the final result may or may not include the checkboxes.

We will use the KDE brand and the other sub-brands actively in our communications, making sure to distinguish between them in a natural way, and start treating the workspace as "just another product". Over the next months we'll be increasingly transitioning to the new terminology and updating our online resources and marketing material to provide a single, coherent branding structure. Of course, as a member of the KDE community, you can help. First of all by using the new terms in your communication, updating sites, documentation and dialogs; secondly by explaining things to others.

Maybe that was the kardinal problem with the KDE4 release cycle. You develop great toolkits and platforms to be used for (later) potential purposes. But no one has a user scenario in mind to which the technology development is instrumental, the solution. Here one early mockup got it right. It is really about a solution to a problem "Browse the web", "mail mary", not technology and applications per se.

Now you have to look at that set of new icons at the top right, close to the search box, for - the tooltip says Select View Appearance (Theme). Choose Configure, then Appearance tab. There is a list of Content Items, and below that a mockup of column headers. Each one of those column headers needs to be clicked on, and your new Custom font set. At the end of this the message list will display in the same font as the rest of your layout.

In case migration from KMail 1 to KMail 2 fails or you have weird problems after it, you can try to do a clean import of your data, instead of migrating the existing settings. Be warned, that needs more manual setup, so do only if you are confident with setting up again your KMail accounts, and it can generate a large amount of network traffic for IMAP resources.

Thank you for your kind comments and suggestions. Can you show me an example of your suggestion? Also, note that I have a first screen in my design that might address some of that. It is not in this mockup.

anemeth offered an interesting idea in While I'm not sure that's the visual look we're going for, I think it does suggest that when the border actually is serving as a visual border, more contrast rather than less would make it look better (though perhaps not as much as in Alex's mockups). I bet the current border would look better in Kirigami and 3rd party apps if it had a 1px dark gray line separating it from the window content. Warning: very very crude mockup incoming:

CGroups and slices provide several benefits over what we can do currently. Because resources are always relative to within the parent slice, we are able to boost resources as well as limit things. This will allow us to bump kwin and such ever so slightly without needing elevated cap privileges.

Another key part of cgroup usage is the concept of slices. Cgroups are based on a heirachical structure, with slices as logical places to split resource usage. We don't adjust resources globally, we adjust resources within our slice, which then provides information to the scheduler.

The best way to get involved is to comment on the relevant phabricator ticket. Or swing by #plasma on IRC and let people know what you want to work on and we'll help you get started.
Some of the systemsettings modules have mockups from the VDG and we want to keep them in the loop.
0 new messages