In both 10.2 and 10.3, the first TAB gives you the most recently used. In 10.2, the second TAB gives you the next one after the most recently used in Dock order. In 10.3, the second TAB gives you the second most recently used. Try switching among 3 applications in 10.2. It's not easy.
That is the whole reason that the extra UI is needed. You want to preserve that ordering, but there's no way to indicate it in the Dock.
There's actually a difference in functionality, not just appearance. In the new version the order of the applications is preserved. Press TAB n times and you get the nth most recently used application. In previous versions it just cycled through the applications in Dock order after the first one, which was a lot less useful.
You completely misunderstood how Tinderbox works (the thing with the red and green columns). Red means that the build was failing at that point in time. It has nothing to do with the number of bugs outstanding, it just means that someone checked in something (it could be a single line) that wouldn't compile on that particular platform.
The Chinese block-printing technique is supposed to have originated around the 6th century A.D. Hand-copied books written on papyrus rolls or clay tablets date back to 3000 B.C. See the Britannica entry on books.
Even the earliest form of copyright law didn't exist until the 15th century A.D., so it's not exactly surprising that any book published before then would be freely distributable.
The way things are set up now, with a potentially infinite number of levels of meta-moderation (what if the meta-moderation isn't fair? do we need meta-meta-moderation?), is too complicated. I propose a simpler system.
Set up a directed graph, with the nodes being the slashdot users, and the weighted connection between user A and user B being A's average opinion of B's posts. (Maybe put in an "uncertainty" factor, as well-- only having rated one post means the rating has a high uncertainty, while having rated dozens means the rating is quite accurate.) Now, use paths through the graph to determine whether a post should be seen. If I like B's posts, and B likes C, then I should be likely to see C's posts. This way, there is no one universal standard for a "good" post. If I happen to think that it's really funny when people flame each other and post a bunch of offtopic stuff, I should be able to adjust my ratings so that is mostly what I see. On the other hand, if I want to see well-balanced, reasoned posts, I can do that, too.
This kind of system would mimic the kinds of trust systems you see in real life-- you trust the opinions of your closest friends, those of friends of your close friends a little less, and those of random people off the street not very much at all.
You could also set it up so if there is no path between yourself and a given user, you just look at the overall average of paths coming into that user and use that to build a reputation score. You go back more than one level deep, though, so if 10 people rate user A highly, but each of these 10 people has received a poor rating from 10 other people, A's rating should not be that high. (In effect, the first extra level deep is your "meta-"moderation and the extra levels are even more exponentially diminishing "meta-" levels.)
Of course this system is based on scoring per individual, not per post, but I think it's safe to assume that the overall quality of a given user's posts is going to be fairly consistent.
I'll admit that this may be more expensive in terms of implementation complexity and resource usage, but I think it's a conceptually clearer system than what exists now.
I tried that too. The wxGTK-devel-2.1.0-9 RPM was missing an include file (wx/gtk/setup.h), so I built wxGTK from scratch, which worked. It still didn't copy that include file when I did 'make install', so I copied it by hand.
Then I build hewx and, while it did build successfully, it was messed up enough to render it unplayable. On the normal game screen I couldn't see any of the text output. If I went to 'show scrollback window', I could see the game output, but then I couldn't type.
I installed wxGTK-2.1.0-9.i386.rpm, downloaded hugov25_wxwin_linux.tar.gz, ran./hewx, and got:
./hewx: Symbol `__vt_14wxImageHandler' has different size in shared object, consider re-linking ./hewx: Symbol `__vt_13wxJPEGHandler' has different size in shared object, consider re-linking Segmentation fault (core dumped)
You can't go at the speed of light. As you approach the speed of light your mass increases and it takes more and more energy to accelerate. You can't actually hit 'c' unless you're massless (like a photon), in which case you're always going at 'c'.
If you're at.999c or whatever and you turn the lights on, the light from the headlights will still appear to be going at 'c' relative to you to observers (_not_.001c).
If that is how it really works, it makes a lot more sense. However, some of the statements on the web page then seem to be basically blatant lies: e.g., "it [the tiny IPic TCP/IP stack] is compliant with all applicable requirements of RFC-1122". Well, yeah, but only if you count all of the code running on the router machine as part of the "tiny IPic TCP/IP stack".
It's based on the normal frequency distribution of letters in English words. "ETAOIN", the six most common letters, are on the corners and the sides where they only take one stroke out to enter. The next few most common, "SHRDLU", take two "short" strokes, and the least common ones, like "Z", "Q", etc., take one short plus one long stroke.
So the current layout is prejudiced toward English, but it could be changed easily enough to accommodate any alphabet with a relatively small number of letters.
Slashdot Mirror
In both 10.2 and 10.3, the first TAB gives you the most recently used. In 10.2, the second TAB gives you the next one after the most recently used in Dock order. In 10.3, the second TAB gives you the second most recently used. Try switching among 3 applications in 10.2. It's not easy.
That is the whole reason that the extra UI is needed. You want to preserve that ordering, but there's no way to indicate it in the Dock.
There's actually a difference in functionality, not just appearance. In the new version the order of the applications is preserved. Press TAB n times and you get the nth most recently used application. In previous versions it just cycled through the applications in Dock order after the first one, which was a lot less useful.
You completely misunderstood how Tinderbox works (the thing with the red and green columns). Red means that the build was failing at that point in time. It has nothing to do with the number of bugs outstanding, it just means that someone checked in something (it could be a single line) that wouldn't compile on that particular platform.
.org/showbuilds.cgi?tree=SeaMonkey.
You can still view the current Tinderbox status for Mozilla at http://tinderbox.mozilla
I closed the anchor tag properly in the HTML I submitted, but somehow it was removed.
Virtually all physics papers are published online before they appear in printed journals. Physicists invented the web, remember?
The Chinese block-printing technique is supposed to have originated around the 6th century A.D. Hand-copied books written on papyrus rolls or clay tablets date back to 3000 B.C. See the Britannica entry on books.
Even the earliest form of copyright law didn't exist until the 15th century A.D., so it's not exactly surprising that any book published before then would be freely distributable.
The way things are set up now, with a potentially infinite number of levels of meta-moderation (what if the meta-moderation isn't fair? do we need meta-meta-moderation?), is too complicated. I propose a simpler system.
Set up a directed graph, with the nodes being the slashdot users, and the weighted connection between user A and user B being A's average opinion of B's posts. (Maybe put in an "uncertainty" factor, as well-- only having rated one post means the rating has a high uncertainty, while having rated dozens means the rating is quite accurate.) Now, use paths through the graph to determine whether a post should be seen. If I like B's posts, and B likes C, then I should be likely to see C's posts. This way, there is no one universal standard for a "good" post. If I happen to think that it's really funny when people flame each other and post a bunch of offtopic stuff, I should be able to adjust my ratings so that is mostly what I see. On the other hand, if I want to see well-balanced, reasoned posts, I can do that, too.
This kind of system would mimic the kinds of trust systems you see in real life-- you trust the opinions of your closest friends, those of friends of your close friends a little less, and those of random people off the street not very much at all.
You could also set it up so if there is no path between yourself and a given user, you just look at the overall average of paths coming into that user and use that to build a reputation score. You go back more than one level deep, though, so if 10 people rate user A highly, but each of these 10 people has received a poor rating from 10 other people, A's rating should not be that high. (In effect, the first extra level deep is your "meta-"moderation and the extra levels are even more exponentially diminishing "meta-" levels.)
Of course this system is based on scoring per individual, not per post, but I think it's safe to assume that the overall quality of a given user's posts is going to be fairly consistent.
I'll admit that this may be more expensive in terms of implementation complexity and resource usage, but I think it's a conceptually clearer system than what exists now.
I tried that too. The wxGTK-devel-2.1.0-9 RPM was missing an include file (wx/gtk/setup.h), so I built wxGTK from scratch, which worked. It still didn't copy that include file when I did 'make install', so I copied it by hand.
Then I build hewx and, while it did build successfully, it was messed up enough to render it unplayable. On the normal game screen I couldn't see any of the text output. If I went to 'show scrollback window', I could see the game output, but then I couldn't type.
Oh well.
I installed wxGTK-2.1.0-9.i386.rpm, downloaded hugov25_wxwin_linux.tar.gz, ran ./hewx, and got:
./hewx: Symbol `__vt_14wxImageHandler' has different size in shared object, consider re-linking
./hewx: Symbol `__vt_13wxJPEGHandler' has different size in shared object, consider re-linking
Segmentation fault (core dumped)
You can't go at the speed of light. As you approach the speed of light your mass increases and it takes more and more energy to accelerate. You can't actually hit 'c' unless you're massless (like a photon), in which case you're always going at 'c'.
.999c or whatever and you turn the lights on, the light from the headlights will still appear to be going at 'c' relative to you to observers (_not_ .001c).
If you're at
If that is how it really works, it makes a lot more sense. However, some of the statements on the web page then seem to be basically blatant lies: e.g., "it [the tiny IPic TCP/IP stack] is compliant with all applicable requirements of RFC-1122". Well, yeah, but only if you count all of the code running on the router machine as part of the "tiny IPic TCP/IP stack".
It's based on the normal frequency distribution of letters in English words. "ETAOIN", the six most common letters, are on the corners and the sides where they only take one stroke out to enter. The next few most common, "SHRDLU", take two "short" strokes, and the least common ones, like "Z", "Q", etc., take one short plus one long stroke.
So the current layout is prejudiced toward English, but it could be changed easily enough to accommodate any alphabet with a relatively small number of letters.
"Credit card carrying waste of flesh"?
I guess that refers to every American
above the age of, say, 16?
Bleh.