Hans wrote:Sounds not completely straightforward to use that theme element as a progress bar (what about other themes?), but Marco would know better how feasible it is.

The actual functionality of showing a progress bar on the task shouldn't be too hard to implement since it already exists for the Icon-Only task manager.

yeah, it would need quite heavy modification for the taskbar
(on the design side, then i'm not sure how much would be clear the distinction between active tasks without a progressbar and those who do)

about feasability in general, the old icontasks plasmoid had done a kind of protocol for doing that so perhaps in the future we can put tiny progressbars in task entries (would be limited to applications that support it tough)

Awesome Fabian! You're back! I thought you had disappeared.

Ehm where to put them is a good question, Marco and Andrew know that better than me right now.

Hey can we have a "Where we are" post about here with links to the work done so far and all relevant bits so we can see what to do and what should be focused on? (Fabian I suspect I would love it if you helped Andrew with the practical bits of the theme work, but lets see what he says when he wakes up (considering he lives in Seattle it will be a few hours))

plusfabi wrote:After this very.. well lets say.. exiting carnival weekend i'm back again:
So far there is now:

• amarok
• audio
• apport
• device
• klipper
• korgac
• nepomuk (do we need this!?)
• preferences -> randr, notofication, bluetooth(inactive, normal, activated)
• printer
• quassel
• synaptiks
• wallet

so how do i git this up in the repository

Welcome back Fabian. Hope you enjoyed carnival! Wow, lots of icons done!

I'm putting together a separate reply with status, git repo links and the like.

When you get a chance can you post a pic with some of them here so we can take a quick look at them here on the thread?

Welcome back!

So where are we?

Status
========
See the tracker for our current progress. Ignoring the files likely to be deprecated, we're about half way through.

I'm thinking the highest visibility tasks remaining are: clock, configuration icons, containment controls, glowbar, pager, shutdowndialog and the remaining icons, plus the opacity and theme contrast settings for plasma2. Marco or Ivan feel free to provide correction to that list.

If anyone chooses to work on any of the remaining files just post a reply here saying what you're working on so we don't duplicate effort too much. My advice: figure out the visual design first, then we can figure out how the technical parts will or will not work to support it (svg color scheme, theme prefixes, applet functionality, etc.).

Git
====
* Marco's git repo hosting the plasma theme development is here: http://quickgit.kde.org/?p=scratch%2Fma ... -theme.git
* Resources for using KDE's git repos are kind of all over the place but the best one I can find is http://community.kde.org/Sysadmin/GitKdeOrgManual
* If you already have read/write access to KDE's git repos, clone Marco's repo with

Code: Select all

git clone git@git.kde.org:scratch/mart/plasma-next-theme.git

* If you don't already have read/write access to KDE git repos, you'll need to request it via KDE Identity. You'll also need to add your SSH key to your KDE Identity account. You can generate a new SSH key on your machine if you don't already have one.
* If you're not quite ready to deal with any of this git stuff, just send me the files and I'll get them into the repo.

I'll be tackling another batch of files over the next day or two.

Hope this helps!

Awesome! Also lets see if our other stray cats come home after carneval

Also: damnit the clock! I forgot about it will get on it in school tomorrow hopefully.

Thirdly: I found this rather neat idea that wen't well with the mockup of the launcher in the public forums. What do you guys think? viewtopic.php?f=285&t=120006

jensreuterberg wrote:I found this rather neat idea that wen't well with the mockup of the launcher in the public forums. What do you guys think? viewtopic.php?f=285&t=120006

Your launcher mockup was the first thing I thought of when I saw that post. Looks pretty neat.

What it brings to mind for me is the potential value of identifying the UI patterns where monochrome icons can be used to support the overall visual design goals. Right now the UI patterns that it seems might use it are the status and notifications, maybe application toolbars? In both your launcher mockup and that public forum post, it looks like a kind of category selection pattern.

Sunday night update:

Updated more files this weekend. Now about 60% of the way through (see tracker). I updated
configuration icons - You see these icons when you mouse over an applet on the desktop and the bar of controls to resize, configure, etc. the applet pops out. I just flattened the existing ones since I thought they looked just fine as is. Of course, if anyone has ideas for new ones feel free to share.
action button - used in a variety of places including the background for the radio button
containment controls - These are handles for aligning and resizing the panel. All new.
pager - For the pager applet. All new.
action overlays - Little icons that appear on icons Folder applet to select, unselect, etc.. All new.
toolbox - little area in the screen corner or on panel where cashew sits. I only updated the screen corner and panel toolboxes. I haven't done the screen edge toolbox yet (that one's kinda weird the way it handles the center vs borders of the frame elements).
panel and dialog shadows - I used the much improved shadows from Marco's shadow experiment with a very minor opacity adjustment.

I'd post some screenshots, but it's better to just install it yourself (see below) and play with it live.

The latest changes are available from Marco's repo here. You can download the theme in a compressed file by clicking on "snapshot" on the latest commit at the repo link. After it downloads, just extract it into your ~/.kde/share/apps/desktoptheme folder. Then select the "Next" theme in System Settings.

While I did mention 60% of the files are done, most of the visible areas are now themed. So, in use, it is much more complete than the raw file count suggests. The remaining high-visibility areas are the plasma2 opacity and contrast settings, the clock and the shutdown dialog. Ideas to replace the moon graphic of the shutdown dialog are certainly welcome. I think we can afford something a little more on the illustrative side here (not my forte) - doesn't have to be specifically related to shutdown either - could be something that represents Plasma or KDE as well. The other files are lower priority for the moment. If there's a particular file you think needs my attention please let me know.

As an aside, I updated the Aurorae windec as well. It's in my shared folder with other next config files (colors, qt curve settings, plasma theme snapshot) here.

alake wrote:Sunday night update:

terrific
i also made now more translucent the parts under translucent/ folder (so htose will be used only when all the needed effects are enabled)

a couple of thing i noticed, consistency wise, is
* shadows: the panel now uses a new one (better, i think) other elements still have another version, it should be used the same everywhere i think.
* white border in frames vs no border: in some places the white border is used(dialog,panel) in some it's not(tooltip, widgets/background). A decision should be made and always the same way used (i'm fine with either, i just think should be paid attention of the edges not looking blurry if no white border is used)

Meaningless sidedetail but I did a simple theme for Chrome and Chromium to use with the Plasma Next Light colors

https://drive.google.com/file/d/0B36nDb ... sp=sharing

notmart wrote:i also made now more translucent the parts under translucent/ folder (so htose will be used only when all the needed effects are enabled)

Thanks Marco. Hopefully it'll look better on plasma2 now. If you get a chance to share how it looks on your plasma2 install that'd be awesome.

notmart wrote:a couple of thing i noticed, consistency wise, is
* shadows: the panel now uses a new one (better, i think) other elements still have another version, it should be used the same everywhere i think.

I'll be sure to take a look. I had hoped I caught most of the shadows, but I may have missed some. Feel free to point out where the old shadows are when you encounter them.

notmart wrote:* white border in frames vs no border: in some places the white border is used(dialog,panel) in some it's not(tooltip, widgets/background). A decision should be made and always the same way used (i'm fine with either, i just think should be paid attention of the edges not looking blurry if no white border is used)

'
Thanks much for paying attention to the details like this Marco. I'll be sure to take a look and get those updated. Also, those edges will probably need to be tuned based on the actual translucency on plasma2. It should be just bright enough to sharpen the edge (keep it from being blurry like you mention). If we notice the white outline at a casual glance then it's probably too bright.

As always, thanks for your help and feedback Marco!

Trying to figure out some things here but this is my laptop right now. Just out of curiosity the top-of-screen menu's how do you change they "glow" effect?



Should I start drawing on a dark theme btw? Thought I should give myself time to do that tonight while packing for the trip

EDIT: sry, THIS glow effect.

> Should I start drawing on a dark theme btw?

IMO, it can wait until 90% of the light one is done - if something needs to be redesigned, to minimize the work.

I'll be helping on that one - the dark themes are my only choice

jensreuterberg wrote:Trying to figure out some things here but this is my laptop right now. Just out of curiosity the top-of-screen menu's how do you change they "glow" effect?
...
EDIT: sry, THIS glow effect.

I think that glow effect in is glowbar.svgz - haven't gotten to that one yet. (Although I wonder why its' showing when the panel is already visible?)

> Although I wonder why its' showing when the panel is already visible?

Guessing it is KRunner glowing... for some reason.

ivan wrote:

jensreuterberg wrote: Should I start drawing on a dark theme btw?

IMO, it can wait until 90% of the light one is done - if something needs to be redesigned, to minimize the work.

I'll be helping on that one - the dark themes are my only choice

Well, I was kinda sorta trying to imply we're at that point when I suggested that most of the visuals you see in day to day use is done.

Much of the remaining files represent visuals that are either corner conditions or likely won't change in any drastic way when they're complete. So I'm thinking the visual design of the theme is reaching some stability at this point. Therefore, if anyone wants to get started on the dark theme I say go for it! The risk of rework should be pretty low. The upside is that we might benefit from the design work done on the dark theme feeding back into the design for the light theme.

For clarity, all ^^^that^^^ talk about design stability doesn't mean we're no longer welcoming design feedback on the theme. Just that I think we've received enough feedback so far that I think it is representative of our collective efforts. I hope I'm not wrong!