The startling conclusion of the paper is that in a worse case scenario--you break a CFL in a closed, unventilated room; you vacuum the carpet, throwing mercury into the air; you set the vacuum in a corner; and then sit in the room breathing for eight hours--the amount of mercury exposure is about equivalent to the exposure you'd get from eating a can of Albacore tuna.
Shawn Wilsher is working on making it asynchronous, so at least it won't stall everything else. He's got his preliminary work packaged as an addon. (Use at your own risk, obviously.)
That's mostly because people's approval (or lack thereof) of Congress is mainly based on their opinions of the people they didn't vote for. It's why I cringe every time I hear a complaint about people in Congress criticizing Bush when their approval rating is even lower. Apples and oranges, people!
(That's not to say that Congress is all sunshine and ponies, either, just that that particular argument is thoroughly flawed.)
Nope, when you call your own number to get to your voicemail, all that happens is that the call gets forwarded to the "real" voicemail number, kicking you out of mobile-to-mobile land.
And you'd be wrong. It doesn't crash because deleting an open file in Unix only unlinks it from the filesystem tree, leaving the contents alone. Only when all programs release the file does the deletion complete.
For Windows, it's theoretically possible to write a dispatch program to associate with.py files that looks for a version-specific shebang, and tries to find the appropriate version of Python on the system. In the case of Apache, I think you're stuck with whichever version your copy of mod_python was compiled against.
The first Android phone, the HTC Dream, will be out "soon". Beware the curse of the early adopter however; while the Dream may (or may not) live up to its name, later offerings will surely be better.
I believe the current implementation just creates a new tab, copies the history of the dragged tab, loads the URL in the new tab, and closes the old one. Try it with a Gmail tab or something, and watch the whole thing reload. This probably also means the current drag-and-drop doesn't work on pages with submitted POST data. I would guess the new feature is true "reparenting" of tabs, which would avoid both these problems.
Basically, the Oxygen artists insisted that having the default window decoration obey the user's color settings for the window frame (which solve the problem of active/inactive distinction) was just too ugly to bear. Never mind that the first question everybody else had when looking at a KDE4 desktop was "how do I tell which window is on top?" The first response was "you're supposed to have composite support, then the shadows will tell you." That didn't go over too well. They also claimed they were working on a bunch of alternate ways to show the focus, and that supporting colored title bars in the meantime was completely unacceptable.
Eventually, the KWin maintainer stepped in and said they didn't have a choice, and that the default window decoration had to conform to certain expectations. There was a bunch more whining, however, so finally he just forked the "Ozone" decoration where the only difference is that window frame color works (but you still have the option to do it the blended way).
Anyway, long story short, having active/inactive window frame colors is supposed to be the default in 4.1.
The EPL is already in Trolltech's license exceptions, so such a thing would have been possible before. Well, since August, as a quick Googling suggests that's when it was added.
There are no separate versions. There is only one codebase for any given version of Qt, with the only difference being the license headers, and the few features that are only available in the commercial version (the website mentions "commercial database drivers and the Visual Studio Integration on Windows.") The Open Source edition is a single package containing all the applicable licenses.
The thing that Trolltech did here that I find really cool is that they changed their license to basically say "GPL 2, 3, or any subsequent version we announce approval of." This way they don't hand over control to the FSF (I agree, the thought of doing that makes me uncomfortable as well) but next time there's a GPL update, adding the new license will be much less of a hassle.
How would that "trap" those people? I don't know the all the legalities of code licensing when you don't release anything, but on a practical level, how would anybody know?
Ugh. You're right. It's inherited from Debian, too, which seems to be the case with everything I don't like about Ubuntu. I was planning on trying another switch from openSUSE once Gutsy's out, but now I'm reconsidering. Do you know if they've made any kind of statement about this (a WONTFIXED bug, for example) -- searching in Launchpad appears to be crap. It's bad enough that Debian uses three different naming conventions for 32bit packages, even though they're supposed to be the paragon of consistent naming.
You'd think that with all the package splitting they do, making architecture-independent -data packages and whatnot, providing 32bit compat packages would be as simple as providing an alias to the actual i386 package. Of course, in order to do that, they'd have to deviate from Debian's (completely stupid) lib -> lib64 convention.
Thank you! While SixApart completely fucked up the initial process, suspending users based on interests and such, some users have gone overboard with the crazy in response. In response to the quote you gave, the user apparently just said "I don't believe you, so nyah." Well then why ask, if you've already judged what you feel the "correct" answer to be?
SixApart is never going to take a laundry list of "hypothetical" situations and give a response that "1, 2, and 5 are child porn, but 3 and 4 are absolutely ok, because Snape is only thinking of raping Harry while Dumbledore watches, not actually doing it. Have a nice day!" Just because some poor employee got tired with answering the same questions over and over again does not make you right.
They're also stuck between a rock and a hard place because obscenity laws are arbitrary and open to wildly different interpretations, and they can't do a damn thing about it.
In short, please, go ahead and boycott, since I couldn't give any less of a damn about fanfic (of any sort).
As I recall, you can also set an arbitrary extension to be run through PHP in Apache, and just name all your php files that way. Hell, you can even tell it that.html files go through PHP, which might slow down regular HTML (which you can get around further by using.htm for one and.html for the other), but shouldn't cause any other problems.
Another advantage of nspluginwrapper I've noticed is that when the flash plugin crashes, it stops Firefox from crashing with it.
(And before anyone asks, I'm sure it's not nspluginwrapper itself causing the crashes, because I can reproduce them on a pure 32-bit setup, and the whole browser goes down.)
Plasma is indeed there. They haven't replaced kicker with a Plasma-based panel yet, but that part's being worked on; getting the API and libs more or less in shape was the first priority. You can see Plasma in action as it currently stands in the new Run dialog, as well as a small sample of widgets like the dictionary applet. You can also see demos of some of the upcoming stuff in Aaron Seigo's blog.
They fixed dolphin so it uses the more standard.directory (or whatever) files instead of.dolphin, and there is a pref to use the same view settings for all folders, after which it won't make any new files.
Slashdot Mirror
FWIW, I got the impression that the to-be-published paper has more detailed figures.
http://www.kqed.org/quest/blog/2009/06/12/how-toxic-is-a-busted-compact-florescent-bulb/
Shawn Wilsher is working on making it asynchronous, so at least it won't stall everything else. He's got his preliminary work packaged as an addon. (Use at your own risk, obviously.)
Most (if not all) KDE libs are LGPL, while most KDE apps are GPL. This has been the case for quite a while, possibly since the beginning.
Except that all of the results so far in those races have been from the first count. Nice try, though!
That's mostly because people's approval (or lack thereof) of Congress is mainly based on their opinions of the people they didn't vote for. It's why I cringe every time I hear a complaint about people in Congress criticizing Bush when their approval rating is even lower. Apples and oranges, people!
(That's not to say that Congress is all sunshine and ponies, either, just that that particular argument is thoroughly flawed.)
Nope, when you call your own number to get to your voicemail, all that happens is that the call gets forwarded to the "real" voicemail number, kicking you out of mobile-to-mobile land.
I doubt Unix would either.
And you'd be wrong. It doesn't crash because deleting an open file in Unix only unlinks it from the filesystem tree, leaving the contents alone. Only when all programs release the file does the deletion complete.
Close all the tabs that have loaded Flash content in them, then nspluginwrapper will work again without restarting the whole browser.
For Windows, it's theoretically possible to write a dispatch program to associate with .py files that looks for a version-specific shebang, and tries to find the appropriate version of Python on the system. In the case of Apache, I think you're stuck with whichever version your copy of mod_python was compiled against.
The first Android phone, the HTC Dream, will be out "soon". Beware the curse of the early adopter however; while the Dream may (or may not) live up to its name, later offerings will surely be better.
I believe the current implementation just creates a new tab, copies the history of the dragged tab, loads the URL in the new tab, and closes the old one. Try it with a Gmail tab or something, and watch the whole thing reload. This probably also means the current drag-and-drop doesn't work on pages with submitted POST data. I would guess the new feature is true "reparenting" of tabs, which would avoid both these problems.
http://bugs.kde.org/show_bug.cgi?id=152030
Warning: lots of developer whining in that bug.
Basically, the Oxygen artists insisted that having the default window decoration obey the user's color settings for the window frame (which solve the problem of active/inactive distinction) was just too ugly to bear. Never mind that the first question everybody else had when looking at a KDE4 desktop was "how do I tell which window is on top?" The first response was "you're supposed to have composite support, then the shadows will tell you." That didn't go over too well. They also claimed they were working on a bunch of alternate ways to show the focus, and that supporting colored title bars in the meantime was completely unacceptable.
Eventually, the KWin maintainer stepped in and said they didn't have a choice, and that the default window decoration had to conform to certain expectations. There was a bunch more whining, however, so finally he just forked the "Ozone" decoration where the only difference is that window frame color works (but you still have the option to do it the blended way).
Anyway, long story short, having active/inactive window frame colors is supposed to be the default in 4.1.
View -> Zoom -> Zoom Text Only
I don't remember if it made it in before Beta 3, but it'll be in B4.
The EPL is already in Trolltech's license exceptions, so such a thing would have been possible before. Well, since August, as a quick Googling suggests that's when it was added.
There are no separate versions. There is only one codebase for any given version of Qt, with the only difference being the license headers, and the few features that are only available in the commercial version (the website mentions "commercial database drivers and the Visual Studio Integration on Windows.") The Open Source edition is a single package containing all the applicable licenses.
(Or, for the short answer, "they will be.")
The thing that Trolltech did here that I find really cool is that they changed their license to basically say "GPL 2, 3, or any subsequent version we announce approval of." This way they don't hand over control to the FSF (I agree, the thought of doing that makes me uncomfortable as well) but next time there's a GPL update, adding the new license will be much less of a hassle.
How would that "trap" those people? I don't know the all the legalities of code licensing when you don't release anything, but on a practical level, how would anybody know?
Ugh. You're right. It's inherited from Debian, too, which seems to be the case with everything I don't like about Ubuntu. I was planning on trying another switch from openSUSE once Gutsy's out, but now I'm reconsidering. Do you know if they've made any kind of statement about this (a WONTFIXED bug, for example) -- searching in Launchpad appears to be crap. It's bad enough that Debian uses three different naming conventions for 32bit packages, even though they're supposed to be the paragon of consistent naming.
You'd think that with all the package splitting they do, making architecture-independent -data packages and whatnot, providing 32bit compat packages would be as simple as providing an alias to the actual i386 package. Of course, in order to do that, they'd have to deviate from Debian's (completely stupid) lib -> lib64 convention.
Thank you! While SixApart completely fucked up the initial process, suspending users based on interests and such, some users have gone overboard with the crazy in response. In response to the quote you gave, the user apparently just said "I don't believe you, so nyah." Well then why ask, if you've already judged what you feel the "correct" answer to be?
SixApart is never going to take a laundry list of "hypothetical" situations and give a response that "1, 2, and 5 are child porn, but 3 and 4 are absolutely ok, because Snape is only thinking of raping Harry while Dumbledore watches, not actually doing it. Have a nice day!" Just because some poor employee got tired with answering the same questions over and over again does not make you right.
They're also stuck between a rock and a hard place because obscenity laws are arbitrary and open to wildly different interpretations, and they can't do a damn thing about it.
In short, please, go ahead and boycott, since I couldn't give any less of a damn about fanfic (of any sort).
As I recall, you can also set an arbitrary extension to be run through PHP in Apache, and just name all your php files that way. Hell, you can even tell it that .html files go through PHP, which might slow down regular HTML (which you can get around further by using .htm for one and .html for the other), but shouldn't cause any other problems.
Yes, that's exactly what happens. I meant to make that clearer.
Another advantage of nspluginwrapper I've noticed is that when the flash plugin crashes, it stops Firefox from crashing with it.
(And before anyone asks, I'm sure it's not nspluginwrapper itself causing the crashes, because I can reproduce them on a pure 32-bit setup, and the whole browser goes down.)
Plasma is indeed there. They haven't replaced kicker with a Plasma-based panel yet, but that part's being worked on; getting the API and libs more or less in shape was the first priority. You can see Plasma in action as it currently stands in the new Run dialog, as well as a small sample of widgets like the dictionary applet. You can also see demos of some of the upcoming stuff in Aaron Seigo's blog.
They fixed dolphin so it uses the more standard .directory (or whatever) files instead of .dolphin, and there is a pref to use the same view settings for all folders, after which it won't make any new files.