If it was on gutenberg, it would have been a transcription. This is a full scan of the original pages, including illustrations. It's looking pretty good.
No, it didn't require anything like that, not even from the very beginning. You were always free to choose either opengl desktop effects, xrender desktop effects, and no desktop effects, and if kwin determined your gpu couldn't handle desktop effects from what the gpu advertised, it would disable desktop effects. And you would have a perfectly functional, fast, usable and beautiful desktop environment.
Of course, some gpu's lied about their abilities in unspecified ways. But you can hardly blame kwin for that.
"There is no "Visual Studio" standard. I mean, what are you supposed to use? Vim and Glade? Get real."
Qt Creator. That's a really excellent development environment.
"they basically just dismissed 3.x, said "we ain't doing it no more". That is just not true. We released two more releases of KDE 3.5 after KDE 4.0 was released.
Except, of course, my dear anonymous ignoramus, that your complaint hasn't been true since KDE 2.0. By default, for instance, the chat application is labeled "Instant Messanger" in big letters, and then, smaller, in gray, you get "kopete". You can find the Instant Messenger in "Internet Applications/Chat".
So, you know, if xcfe shows the binaries name in the menus, it's xfce that's about a decade behind the times.
Because that's what used to be the default pretty much everywhere for a long, long time. Also, there's nothing particularly uncomfortable about the combination.
Yeah, because that's, like, the most important feature of any desktop environment! A huge majority of people are using that all the time, I'm sure!
Well, coming back to planet reality: --geometry is a stupid workaround for applications developed by people who are too incompetent to implement proper geometry management, or re-use the proper geometry management provided by a proper toolkit.
I'm sorely tempted to just close that bug as "invalid" -- but I'm note a kde-core developer.
"Get your feedback and testing from a closed group."
Wonderful idea. Except, of course, the KDE is open software and developed in the open... That makes your proposal kind of completely irrelevant.
Working on that. The unstable version actually seems to work well for quite a few people, it was even used to preset Krita at LFNW. Please download it and tell me whether it works or not so I can fix issues and make it stable...
http://www.kogmbh.com/download.html
It has been solved. Krita supports 8, 16 bit integer -- but also 16 and 32 bit floating point per channel.
And heck, if you have a high-end graphics card and a high-end monitor that support more than 8 bits per channel output -- and those do exist -- then Krita supports that, too.
I'm really happy I got the trinity guys to rename their fork of Krita 1.6. There's no way I would like to be associated with that version in 2012:-). Krita 2.4 just is so much better.
Like the steel industry in Pittsburgh had. One week of 10 hour night shifts, 24 hours off, one week of 14 hour day shifts and a 24 hour shift to switch back to the night shift...
See http://www.clpgh.org/exhibit/ptpa.html -- it was so good for productivitiy!
Yes. Settings/Keyboard Settings, then Advanced tab. Check 'Caps Lock key behaviour". "Make Caps Lock an addition Backspace" is on of the options (there are more than 10). If that doesn't work reliably for you, file a bug. It works perfectly here, even with non-KDE applications.
Nothing is taken away from KDE. The trinity people are different people, and they are welcome to do what they want to do: they even do it right inside the KDE svn infrastructure. Their itch, they scratch, it's totally fine.
And when I asked them to rename their fork of Krita (because Krita 2.4 is so much better that we all want to forget Krita 1.6), they did, no complaints. Great people, good cooperation. They only need to start showing up at aKademy or Desktop Summits.
No, he did not. He talked about ctrl-alt-f2, which goes to a text console, not alt-f2, which opens krunner, aka the minicli, right inside the X11 session.
You'd realized that, had you cared to read both his and my post before jumping to reply. Toodle-pip.
No, killing the plasma-desktop process does not kill all your chance to start a terminal: krunner is a separate process, so alt-f2 will give you the minicli and you can start anything you want.
Compile and execute code from within an application? That's exactly what Krita (http://www.krita.org) does with OpenGTL (http://opengtl.org) -- we have code written in special languages for filters and so on which gets compiled by Krita and then executed as native code. It's pretty safe as well.
Slashdot Mirror
At least work is being done to implement the feature -- how much better can it get?
If it was on gutenberg, it would have been a transcription. This is a full scan of the original pages, including illustrations. It's looking pretty good.
Oh gods! Doctors still make housecalls where you live? They sure don't in the Netherlands.
"Cannabis smoke leaves behind a tarry resin but it doesn't cause cancer." It does, and a lot quicker than tobacco smoke, too.
That's actually also true for the united states. The first macadamization was done by bicycle clubs.
No, it didn't require anything like that, not even from the very beginning. You were always free to choose either opengl desktop effects, xrender desktop effects, and no desktop effects, and if kwin determined your gpu couldn't handle desktop effects from what the gpu advertised, it would disable desktop effects. And you would have a perfectly functional, fast, usable and beautiful desktop environment. Of course, some gpu's lied about their abilities in unspecified ways. But you can hardly blame kwin for that.
It was one, good, reason for moving to Linux. The perfect excuse to decline helping people with their Windows problems.
"There is no "Visual Studio" standard. I mean, what are you supposed to use? Vim and Glade? Get real." Qt Creator. That's a really excellent development environment.
The review suggests it is... Maybe get a copy for yourself to make sure?
"they basically just dismissed 3.x, said "we ain't doing it no more". That is just not true. We released two more releases of KDE 3.5 after KDE 4.0 was released.
And, of course, KOffice, Calligra these days, is older than LibreOffice or OpenOffice. It predates the opening of StarOffice.
Except, of course, my dear anonymous ignoramus, that your complaint hasn't been true since KDE 2.0. By default, for instance, the chat application is labeled "Instant Messanger" in big letters, and then, smaller, in gray, you get "kopete". You can find the Instant Messenger in "Internet Applications/Chat". So, you know, if xcfe shows the binaries name in the menus, it's xfce that's about a decade behind the times.
Because that's what used to be the default pretty much everywhere for a long, long time. Also, there's nothing particularly uncomfortable about the combination.
Yeah, because that's, like, the most important feature of any desktop environment! A huge majority of people are using that all the time, I'm sure! Well, coming back to planet reality: --geometry is a stupid workaround for applications developed by people who are too incompetent to implement proper geometry management, or re-use the proper geometry management provided by a proper toolkit. I'm sorely tempted to just close that bug as "invalid" -- but I'm note a kde-core developer.
"Get your feedback and testing from a closed group." Wonderful idea. Except, of course, the KDE is open software and developed in the open... That makes your proposal kind of completely irrelevant.
Working on that. The unstable version actually seems to work well for quite a few people, it was even used to preset Krita at LFNW. Please download it and tell me whether it works or not so I can fix issues and make it stable... http://www.kogmbh.com/download.html
It has been solved. Krita supports 8, 16 bit integer -- but also 16 and 32 bit floating point per channel. And heck, if you have a high-end graphics card and a high-end monitor that support more than 8 bits per channel output -- and those do exist -- then Krita supports that, too.
I'm really happy I got the trinity guys to rename their fork of Krita 1.6. There's no way I would like to be associated with that version in 2012 :-). Krita 2.4 just is so much better.
Like the steel industry in Pittsburgh had. One week of 10 hour night shifts, 24 hours off, one week of 14 hour day shifts and a 24 hour shift to switch back to the night shift... See http://www.clpgh.org/exhibit/ptpa.html -- it was so good for productivitiy!
Yes. Settings/Keyboard Settings, then Advanced tab. Check 'Caps Lock key behaviour". "Make Caps Lock an addition Backspace" is on of the options (there are more than 10). If that doesn't work reliably for you, file a bug. It works perfectly here, even with non-KDE applications.
You do know Suse is no longer owned by Novell, right? That it's been spun off as a separate company again by Attachmate?
Nothing is taken away from KDE. The trinity people are different people, and they are welcome to do what they want to do: they even do it right inside the KDE svn infrastructure. Their itch, they scratch, it's totally fine. And when I asked them to rename their fork of Krita (because Krita 2.4 is so much better that we all want to forget Krita 1.6), they did, no complaints. Great people, good cooperation. They only need to start showing up at aKademy or Desktop Summits.
No, he did not. He talked about ctrl-alt-f2, which goes to a text console, not alt-f2, which opens krunner, aka the minicli, right inside the X11 session. You'd realized that, had you cared to read both his and my post before jumping to reply. Toodle-pip.
No, killing the plasma-desktop process does not kill all your chance to start a terminal: krunner is a separate process, so alt-f2 will give you the minicli and you can start anything you want.
Compile and execute code from within an application? That's exactly what Krita (http://www.krita.org) does with OpenGTL (http://opengtl.org) -- we have code written in special languages for filters and so on which gets compiled by Krita and then executed as native code. It's pretty safe as well.