COUNTDOWN TILL THE NEXT CUBE FLIP SOFTWARE
COUNTDOWN TILL THE NEXT CUBE FLIP CODE

You shouldn't start from what you want to make, but what it needs to be to achieve its purpose. Good design begins with purpose - identifying the required function - and that produces a specification the design needs to fulfil. We all set to work drawing things we thought we could make which would do the job, until one boy asked the teacher 'How big is a slice of bread?' The teacher congratulated him on his inside. In my first-year woodworking class at school the teacher gave us the assignment of designing a toast rack.

COUNTDOWN TILL THE NEXT CUBE FLIP CODE

If users came first, wouldn't the correct approach be to rewrite or replace functionality first so it were ready for the new streamlined code when that comes along? The approach of break it first and then see whether we can provide something similar later might be OK as a development approach, but not in released production versions. that's always a good thing to aim for, but I would question whether that should be done in a way which deprives users of features they need, at least if it doesn't provide something of equivalent utility.

The question is what is the purpose of a desktop? Is it to be a vehicle for its authors to write elegant code or to provide functionality to users? I can quite understand the desire to streamline code. I do think arguing about resources misses the point. It appear to be, but since most of the discussion has happened here I'm not sure which is the best way to merge them without risking these comments being lost from sight.

It's not the resources that are the problem it's the attitude. Again, I've read the email exchange that you linked to, and it's not a matter of 'we don't have the resources', but of 'let's just drop it, because hardly anybody's using it anyway.' Don't hide behind the excuse of not having the resources and/or the manpower. If you break something, then you're also taking the responsibility upon you to fix it again. There's an old saying that goes 'If it ain't broke, don't fix it', just as there is another saying that goes 'Whatever you're going to do, if you're going to do it, then you should do it well.' Plasma 4 springs to mind, as well as that it took you guys until 5.10 before the global menu ─ a feature that had already more or less been present (even if only for Qt applications only at the time) in KDE 1.x, 2.x and 3.x ─ was reintroduced, in spite of the very popular demand throughout the entire life cycle of Plasma 4 and up until 5.10. If the new 'scene' ─ as you guys call it ─ requires the rewriting of those effects, then perhaps you are pushing out this new 'scene' prematurely at the cost of breaking existing features, and ─ forgive me for saying this ─ you guys unfortunately have a history of doing that.

COUNTDOWN TILL THE NEXT CUBE FLIP SOFTWARE

Therefore, you are also in control of which aspects of the software you wish to advance to the next level first. You are all in control of how Plasma works and how it evolves. It will be great if the community helpsįorgive me for sounding hostile, and I fully appreciate that the effect(s) would need to be rewritten in order to ensure compatibility with the evolution of the Plasma desktop, but from the email exchange you've linked to here-above, it appears to rather be a matter of not having any motivation to do so instead of a matter of not having the manpower or the resources, as well as a matter of not being in touch with your user base. > the effect reimplemented in qml (like the overview effect), but we don't As discussed in the mailing list thread, we would like to have > I'm afraid that we can't bring the effect back because rendering (In reply to Vlad Zahorodnii from comment #3) Without that, I fear KDE will lose favour with its supporters and something else will take its place in due course, but I'd rather not have the upheaval. All that is needed is a little good will and understanding. The rest of the template is about technical details and is unnecessary in this case, as those who have taken this vital component out will know precisely what they have done and what needs to be done to put it back. Without it I, and I'm sure many others, will be much impoverished. Now I hear it is to be removed in the next release and I must implore you to think again.īeing able to hit a simple key combination and swivel to a fresh workspace is a boon to productivity and makes Plasma such a joy to use, being able to distance and rotate the desktop enables a quick and intuitive overview of layouts and locations in organising work. It marks it out from all the other DEs and makes it more useful and user-friendly than the alternatives.

The desktop cube is for many the distinguishing feature of KDE Plasma.

Countdown till the next cube flip