If you don't understand them, it means you don't have the problem they are solving - a lot of UI components open all at once.
But whenever you're overloaded with multitude of items, grouping may help you. And sometimes you can distinguish some non-overlapping groups of GUI components. These are activities.
Like: For staying up to date with life (my eMail client, my facebook page), for the project I am currently working on (my IDE, some folders of the project I am currently editing, GIThub page, various googling sessions I am doing in research), for the entertainment (my favorite offtopic sites, etc.).
Yeah, but this would just be tagging:) In RDF, since you can relate any resource (i.e. concept) to any other, you can also relate "tags" (e.g. rdf:type properties) to each other. RDF features some simple inference-enabling vocabulary for creating taxonomies out of these, OWL offers even more and this is not the limit. Then you can easily discover similar "tags" by analysing the number of common instances and semantic distance between them both in the taxonomy created by RDF/OWL vocabulary as well as any other.
Why are the icons all ridiculously huge and ridiculously tiny? Why are the sides of the taskbar chopped off?>
Duh! But what? What's that window titled Configure Battery Monitor that has a 'Size of the battery' field?
You wouldn't think they were going to hard code the size of scalable (SVG!) items just not to 'confuse' the easily confusable grammas.
"
The fact that you had to hunt around and make changes to make the desktop simple and sane enough to use means that KDE failed to get it right in the first place. How is [hard coding functionalities/stripping configuration] helping to achieve sane defaults? KDE has also been working on usability with OpenUsability. However there are always different ways of doing stuff that no study will prove any of them better, and this is where configuration is cruicial.
But if that's the case you're an outlier (no offence - rejoice in your point of difference!) and you probably shouldn't be making broad judgements about the usability of desktop environments for anyone other than yourself. Interface Nazi;P
Here's Pat's view on the issue:
From the ChangeLog.txt from Fri Jul 14 18:31:20 CDT 2006
"I'm probably going to leave the bare.i 2.4.32 kernel as the default kernel (or perhaps sata.i?) as it has very good performance and probably better security due to the simpler and longer-tested design."
Slashdot Mirror
If you don't understand them, it means you don't have the problem they are solving - a lot of UI components open all at once.
But whenever you're overloaded with multitude of items, grouping may help you. And sometimes you can distinguish some non-overlapping groups of GUI components. These are activities.
Like: For staying up to date with life (my eMail client, my facebook page), for the project I am currently working on (my IDE, some folders of the project I am currently editing, GIThub page, various googling sessions I am doing in research), for the entertainment (my favorite offtopic sites, etc.).
Great. I bet the haxxorz just can't wait to revamp their dictionaries using brute force scanning of the password choice form.
Early adopters! Come on!
Wondering how pop resistant it is :>
Speaking about popping, this is THE INTERFACE for:
http://www.cocagames.com/games/files/bubblewrap.swf
That's probably because they don't know about
sudo -i
Yeah, but this would just be tagging :)
In RDF, since you can relate any resource (i.e. concept) to any other, you can also relate "tags" (e.g. rdf:type properties) to each other. RDF features some simple inference-enabling vocabulary for creating taxonomies out of these, OWL offers even more and this is not the limit.
Then you can easily discover similar "tags" by analysing the number of common instances and semantic distance between them both in the taxonomy created by RDF/OWL vocabulary as well as any other.
Duh! But what? What's that window titled Configure Battery Monitor that has a 'Size of the battery' field?
You wouldn't think they were going to hard code the size of scalable (SVG!) items just not to 'confuse' the easily confusable grammas.
Remember. It's KDE... not Gnome
How is [hard coding functionalities/stripping configuration] helping to achieve sane defaults? KDE has also been working on usability with OpenUsability. However there are always different ways of doing stuff that no study will prove any of them better, and this is where configuration is cruicial. But if that's the case you're an outlier (no offence - rejoice in your point of difference!) and you probably shouldn't be making broad judgements about the usability of desktop environments for anyone other than yourself. Interface Nazi
Duuh... Anybody remembers what OLPC stood for? One Lapdance Per Child or something...
Here's Pat's view on the issue:
From the ChangeLog.txt from Fri Jul 14 18:31:20 CDT 2006
"I'm probably going to leave the bare.i 2.4.32 kernel as the default kernel (or perhaps sata.i?) as it has very good performance and probably better security due to the simpler and longer-tested design."
Are the kernel source files permissions part of a new security policy? rwxrwxrwx!