that's why its no longer the official kde media player.
Basicly your whole commnet is utter nonsens, reaching a high point by this part of the comment. Amarok have never been the official KDE media player. In KDE2 and 3 the official mediaplayer was Noatun(In later releases you also got the choice of JuK for audio).
For KDE 4 users, JuK is the default media player for audio media. While Dragon Player is the default for video. Both are great applications, preforming their task well. Interrestingly many of the load complainers against Amaroks design, describe the way JuK works. Go figure.
Qt is nice, but its licensing prevents Google from using it in this way. To use Qt, Google would need to either pay for a license,
This would be no problem. Fact is, Google already does exactly this for other products.
but it wouldn't be transferable to others,
??? What are you talking about? Companies sell, eg transfer, software developed with Qt all the time, it's what is made for after all. Obviously the license allow it.
or Chrome would need to be GPLed. Google goes to great effort to license it's code under the Apache/BSD/etc. licenses whenever possible, as it considers this better for it's business (and that's a reasonable position to take).
Good luck writing up that letter to your ISP to complain about their outages then, guess that would be as useful as using their web based fault reporting tool or sending a e-mail to support.
And NI are absolutely writing kernel-level drivers, since they in addition to software for measurement and automation they offers a huge number of different hardware. So to support all their measurement, dataloging and automation hardware, they have to write drivers for PXI (PCI eXtensions for Instrumentation), VXI, PXI- and PCI-based modular instruments and GPIB bus controllers. Their Linux offering have been rapidly growing for years, so obviously their userbase already have a strong interest in Linux.
Even if I disagree in that NI's hardware are considerably less complex than the hardware of NVidia and AT. For some I think actually the opposite are true, but it does not matter. What makes it hard for NI are simply the huge amount of different hardware they have to support, most likely many more than any other hardware vendor doing Linux support. Combined with the fact that their userbase expect support for far longer time than you can expect from the likes of nVidia or ATI. And very few, if any, of the regular kernel developers have or use any of their rather specialized hardware, makes it rather inconvenient and expensive when the kernel API changes. IMHO, the only strong reason for a stable kernel API are vendors like NI making specailzed, non-mainstream hardware.
Simply drop the toolkit fanboi-ism and use the application that already provides what you ask for, Kopete. Being a KDE application is not relevant, it runs very well under Gnome too.
Ubuntu LTS had to include a beta web browser (Firefox 3) because the old version would not have been supported by Mozilla for the three years that Canonical has to support the OS.
This statement has two major flaws. The first one since other distributions manage to support packages after upstream abandoned them, there should be no problem for Canonical to do the same.
The second flaw is the notion that it's impossible to upgrade applications to later major versions in a distribution. Libraries can be tricky, and best avoided, but for applications there are no real compelling reason not to do it. Even if most distributions has the policy not to do this. It usually makes the burden of maintainace less, so it's a natural choice. But it's only policy, and making exceptions when needed poses no problems. So rather than including a unstable application, they should have included the old stable version, and pushed a upgrade to the new version in due time.
The pricing difference is quite natural as the Greenphone basicly are a development board, while the Neo is supposed to be a consumer device. Hopfully soon after the release we will see a port of the Greenphone suite to it. Giving the best of both worlds. Giving access to cool stuff like this: http://blogs.qtdeveloper.net/archives/2007/01/19/w ebkit-on-embedded/
don't believe any claims nade about vaporware until you see it for yourself in the shipping product.
But this is not about vaporware, since you already can run pre releases of KDE 4 and see for your self. And even more important, the reason for the expected reduction of memory usage. Is based on improvement clearly seen in the underlying library used by KDE, Qt. And Qt 4.0 was released 29 June 2005, so you can hardly call that vaporware.
Simply with BSD-licensed code you don't have to give your changes back, but with GPL v2 you have to Tivio or not. And that's the whole difference, simply getting the code back.
The reviewer was right, back then(for a time) it was by far the best desktop linux. Strange you did not hear about it, it was all over the news and generally Linux sites.
Both the install and desktop was far slicker, and better put together then anything else at the time. Unfortunately it had a few not so good points too, like not having a collection good gui administrative tools. Making others like Mandrake a better choice for beginners. And the worst problem was from it's Debian heritage, it was based on the Debian stable at the time which was even more out of date than now. A old version of glibc made compiling lots of the new development taking place at that time problematic or impossible.
Hopefully Slashdot will. But until it get fixed, you can apply a workaround by disabling javascript for shlasdot. Just add.slashdot.org Reject as a domain-Specific setting for JavaScript in Konqueror.
Sounds like you don't tell it the correct way. Controll Center->KDE Components->Component Chooser->Web Browser and set it to Firefox.
When other applications get launched it's not mysteriously, but based on MIME types. Left click on a file of the type that "missbehaves" select properties. Click on the little wrench and edit the Application preference order to show your preferred application at the top of the list.
>Kevin J. Anderson & Timothy Zahn could write a story.
Agree 50%, but not with the Kevin J. Anderson bit. I would rather have Michael A. Stackpole work with Timothy Zahn, he is better than Anderson. They are the best writers that has worked on the Star Wars novels, their respective works are in a class above all the others. And they already have experience working thogether in the Star Wars universe. The 'Side Trip' story from Tales From the Empire, are one of the best short stories in the series.
Re:Link KDE/GNOME applications w/ Motif library?
on
A Look at GNOME 2.14
·
· Score: 2, Insightful
I think you just won the award for the craziest question ever asked on Slashdot. Motif widgets are NOT interchangeable with Qt/Gtk.
Not as crazy as you think. If you need to migrate a large Xt and Motif application to a modern toolkit, that's the most sensible solution. And the exact reason why the TT has developed the Qt Motif Extension. The Qt Motif Extension provides a complete and working solution for incremental migration. http://doc.trolltech.com/3.3/motif-walkthrough.htm l
But still beats starting from scratch, I'd say.
(especially in package management) are *sorely* behind.
And the package manager are probably the most uninteresting part of YaST anyway, it's the myriad of other tools in YaST that's interresting. Putting a nice GUI on top of URMPI or APT solves the package management part nicely, and several such already exist.
>KDE makes me want to log out of Linux, but that's just my opinion.
Could you please clearify this statement?
I think it's because he likes the KDE logout dialog so much....
Re:Great way of starting a flamewar
on
KDE 4 Screenshots
·
· Score: 1
bad window title bar button layout
The default button layout can vary between window decoration styles, but since every last one of them are configurable(Except the OpenLook decoration actually, that would have been kind of useless) making it rather easy to use the layout that fits your personal preferences best.
It does have a few (very simple and easy to use) tools to enhance contrast/color etc., but it's purpose is nothing like Photoshop/Gimp/PaintShopPro/etc.
And that is what makes Picasa the right applications for the majority of users, since it does fill their limited needs when it comes to photo editing. The average user simply do not need all the functionality you find in the likes of Photoshop/Gimp/PaintShopPro/etc. Using Photoshop/Gimp/PaintShopPro/etc when you only do basic tasks like cropping and redeye removal etc. is just plain stupid. Those users are better of with simpler tools, and if it's included in their photo organizer application it's just a added bonus, like Picasa or DigiKam.
Windows 95/98/Me operating systems are more secure than Windows 2000/XP.
The funny thing is, the statement is not as ridiculous as it sounds. They are of course not more secure, but they are actually less likely to get compromised by an attack. Since most of the current malware and virus uses newer functionality which do not exist or function slightly different on the older systems. Resulting in the malware simply not working on those old systems. I guess the mallware writers are not too concerned about backwards compability.
They use the same:
* Processors (Intel x86)
Ok, a nobrainer.
* Internal peripherals busses (PCI and AGP)
* External peripherals interfaces (USB and BlueTooth)
* Hard drive interface (SATA)
And all of those require drivers for the different chipsets used, with all their different quirks and differences. Take a look at the list of different SATA chipset supported by Linux, and the list of those not yet or fully supported. MacOS X for x86 will naturally only have support for a very limited range of chips, the one Apple uses themselves. To make it work with others, you first have to reverse engineer the driver interface used in OS X and then write the drivers from scratch(I don't think it's very likely Apple will release documentation for it). Or as I already said, you may carefully select components using the same chipsets as Apple uses. Basically making it impossible to just slap OS X on any random PC.
Just about the only thing non-commodity is the Apple Display Connector (ADC)
And perhaps the little thing which on IBM compatible PCs are called BIOS, which the MacIntels don't have since they use something different for that task. And eventually all the additional hooks Apple may have placed in the hardware and software to prevent just this scenario. And any experience people have had with the earlier developer pre-release does not really matter, as they can have added those later.
That the new Mac's use Intel processors does not make them commodity system. And in the same way non Apple PPC machines like the Pegasos machines from Genesi don't run MacOS X, commodity PCs will not either.
if I wish to install one of my licensing of Mac OS on an extra PC, and I cannot, then I am likley to an become an irate customer.
Then you are going to become irate, using a Intel processor does not mean it magically will run on a standard IBM architecture PC. The fact is, the move to Intel may make it possible to run MacOS X on a non Apple box. And only if it's built with carefully select components, in combination with some carefully crafted patches made by reveresengenering/hacking parts of OS X.
the significance of whitespace was a major barrier for them to overcome.
If they are new to programming that is an absolute non-issue. Don't talk about whitespaces at all, it's totally unnecessary, just tell them to follow the block indenting. AKA everything having the same left margin belongs to the same code block. Use how lots of books displays their table of contents, with chapters and subchapters differently indented as an example.
Slashdot Mirror
that's why its no longer the official kde media player.
Basicly your whole commnet is utter nonsens, reaching a high point by this part of the comment. Amarok have never been the official KDE media player. In KDE2 and 3 the official mediaplayer was Noatun(In later releases you also got the choice of JuK for audio).
For KDE 4 users, JuK is the default media player for audio media. While Dragon Player is the default for video. Both are great applications, preforming their task well. Interrestingly many of the load complainers against Amaroks design, describe the way JuK works. Go figure.
Qt is nice, but its licensing prevents Google from using it in this way. To use Qt, Google would need to either pay for a license,
This would be no problem. Fact is, Google already does exactly this for other products.
but it wouldn't be transferable to others,
??? What are you talking about? Companies sell, eg transfer, software developed with Qt all the time, it's what is made for after all. Obviously the license allow it.
or Chrome would need to be GPLed. Google goes to great effort to license it's code under the Apache/BSD/etc. licenses whenever possible, as it considers this better for it's business (and that's a reasonable position to take).
No need for GPL, you can freely use Qt with a wide range of open source licenses like Apache/BSD/etc. Please check your facts. http://doc.trolltech.com/4.4/license-gpl-exceptions.html
Good luck writing up that letter to your ISP to complain about their outages then, guess that would be as useful as using their web based fault reporting tool or sending a e-mail to support.
Native KOffice for Windows and Mac are already exist, they are in beta just as the native X11 variant.
And NI are absolutely writing kernel-level drivers, since they in addition to software for measurement and automation they offers a huge number of different hardware. So to support all their measurement, dataloging and automation hardware, they have to write drivers for PXI (PCI eXtensions for Instrumentation), VXI, PXI- and PCI-based modular instruments and GPIB bus controllers. Their Linux offering have been rapidly growing for years, so obviously their userbase already have a strong interest in Linux.
Even if I disagree in that NI's hardware are considerably less complex than the hardware of NVidia and AT. For some I think actually the opposite are true, but it does not matter. What makes it hard for NI are simply the huge amount of different hardware they have to support, most likely many more than any other hardware vendor doing Linux support. Combined with the fact that their userbase expect support for far longer time than you can expect from the likes of nVidia or ATI. And very few, if any, of the regular kernel developers have or use any of their rather specialized hardware, makes it rather inconvenient and expensive when the kernel API changes. IMHO, the only strong reason for a stable kernel API are vendors like NI making specailzed, non-mainstream hardware.
Simply drop the toolkit fanboi-ism and use the application that already provides what you ask for, Kopete. Being a KDE application is not relevant, it runs very well under Gnome too.
The second flaw is the notion that it's impossible to upgrade applications to later major versions in a distribution. Libraries can be tricky, and best avoided, but for applications there are no real compelling reason not to do it. Even if most distributions has the policy not to do this. It usually makes the burden of maintainace less, so it's a natural choice. But it's only policy, and making exceptions when needed poses no problems. So rather than including a unstable application, they should have included the old stable version, and pushed a upgrade to the new version in due time.
The pricing difference is quite natural as the Greenphone basicly are a development board, while the Neo is supposed to be a consumer device. Hopfully soon after the release we will see a port of the Greenphone suite to it. Giving the best of both worlds. Giving access to cool stuff like this: http://blogs.qtdeveloper.net/archives/2007/01/19/w ebkit-on-embedded/
don't believe any claims nade about vaporware until you see it for yourself in the shipping product.
But this is not about vaporware, since you already can run pre releases of KDE 4 and see for your self. And even more important, the reason for the expected reduction of memory usage. Is based on improvement clearly seen in the underlying library used by KDE, Qt. And Qt 4.0 was released 29 June 2005, so you can hardly call that vaporware.
The most common form of hero is the person that actually goes about to get the hard parts done, not the one preaching about doing it.
Simply with BSD-licensed code you don't have to give your changes back, but with GPL v2 you have to Tivio or not. And that's the whole difference, simply getting the code back.
The reviewer was right, back then(for a time) it was by far the best desktop linux. Strange you did not hear about it, it was all over the news and generally Linux sites.
Both the install and desktop was far slicker, and better put together then anything else at the time. Unfortunately it had a few not so good points too, like not having a collection good gui administrative tools. Making others like Mandrake a better choice for beginners. And the worst problem was from it's Debian heritage, it was based on the Debian stable at the time which was even more out of date than now. A old version of glibc made compiling lots of the new development taking place at that time problematic or impossible.
Hopefully Slashdot will. But until it get fixed, you can apply a workaround by disabling javascript for shlasdot. Just add .slashdot.org Reject as a domain-Specific setting for JavaScript in Konqueror.
I want to know what X86 cpu they are using that only uses one watt!
o ductInformation/0,,50_2330_9863_13022,00.html
I would guess one of those AMD Geode processors:
http://www.amd.com/us-en/ConnectivitySolutions/Pr
Sounds like you don't tell it the correct way. Controll Center->KDE Components->Component Chooser->Web Browser and set it to Firefox.
When other applications get launched it's not mysteriously, but based on MIME types. Left click on a file of the type that "missbehaves" select properties. Click on the little wrench and edit the Application preference order to show your preferred application at the top of the list.
>Kevin J. Anderson & Timothy Zahn could write a story. Agree 50%, but not with the Kevin J. Anderson bit. I would rather have Michael A. Stackpole work with Timothy Zahn, he is better than Anderson. They are the best writers that has worked on the Star Wars novels, their respective works are in a class above all the others. And they already have experience working thogether in the Star Wars universe. The 'Side Trip' story from Tales From the Empire, are one of the best short stories in the series.
I think you just won the award for the craziest question ever asked on Slashdot. Motif widgets are NOT interchangeable with Qt/Gtk.
m l
Not as crazy as you think. If you need to migrate a large Xt and Motif application to a modern toolkit, that's the most sensible solution. And the exact reason why the TT has developed the Qt Motif Extension. The Qt Motif Extension provides a complete and working solution for incremental migration. http://doc.trolltech.com/3.3/motif-walkthrough.ht
Actually the YaST code is still full of SUSE-isms
But still beats starting from scratch, I'd say. (especially in package management) are *sorely* behind.
And the package manager are probably the most uninteresting part of YaST anyway, it's the myriad of other tools in YaST that's interresting. Putting a nice GUI on top of URMPI or APT solves the package management part nicely, and several such already exist.
>KDE makes me want to log out of Linux, but that's just my opinion.
Could you please clearify this statement?
I think it's because he likes the KDE logout dialog so much....
bad window title bar button layout
The default button layout can vary between window decoration styles, but since every last one of them are configurable(Except the OpenLook decoration actually, that would have been kind of useless) making it rather easy to use the layout that fits your personal preferences best.
It does have a few (very simple and easy to use) tools to enhance contrast/color etc., but it's purpose is nothing like Photoshop/Gimp/PaintShopPro/etc.
And that is what makes Picasa the right applications for the majority of users, since it does fill their limited needs when it comes to photo editing. The average user simply do not need all the functionality you find in the likes of Photoshop/Gimp/PaintShopPro/etc. Using Photoshop/Gimp/PaintShopPro/etc when you only do basic tasks like cropping and redeye removal etc. is just plain stupid. Those users are better of with simpler tools, and if it's included in their photo organizer application it's just a added bonus, like Picasa or DigiKam.
Windows 95/98/Me operating systems are more secure than Windows 2000/XP.
The funny thing is, the statement is not as ridiculous as it sounds. They are of course not more secure, but they are actually less likely to get compromised by an attack. Since most of the current malware and virus uses newer functionality which do not exist or function slightly different on the older systems. Resulting in the malware simply not working on those old systems. I guess the mallware writers are not too concerned about backwards compability.
They use the same:
* Processors (Intel x86)
Ok, a nobrainer.
* Internal peripherals busses (PCI and AGP)
* External peripherals interfaces (USB and BlueTooth)
* Hard drive interface (SATA)
And all of those require drivers for the different chipsets used, with all their different quirks and differences. Take a look at the list of different SATA chipset supported by Linux, and the list of those not yet or fully supported. MacOS X for x86 will naturally only have support for a very limited range of chips, the one Apple uses themselves. To make it work with others, you first have to reverse engineer the driver interface used in OS X and then write the drivers from scratch(I don't think it's very likely Apple will release documentation for it). Or as I already said, you may carefully select components using the same chipsets as Apple uses. Basically making it impossible to just slap OS X on any random PC.
Just about the only thing non-commodity is the Apple Display Connector (ADC)
And perhaps the little thing which on IBM compatible PCs are called BIOS, which the MacIntels don't have since they use something different for that task. And eventually all the additional hooks Apple may have placed in the hardware and software to prevent just this scenario. And any experience people have had with the earlier developer pre-release does not really matter, as they can have added those later.
One problem with using a full commidity system
That the new Mac's use Intel processors does not make them commodity system. And in the same way non Apple PPC machines like the Pegasos machines from Genesi don't run MacOS X, commodity PCs will not either.
if I wish to install one of my licensing of Mac OS on an extra PC, and I cannot, then I am likley to an become an irate customer.
Then you are going to become irate, using a Intel processor does not mean it magically will run on a standard IBM architecture PC. The fact is, the move to Intel may make it possible to run MacOS X on a non Apple box. And only if it's built with carefully select components, in combination with some carefully crafted patches made by reveresengenering/hacking parts of OS X.
the significance of whitespace was a major barrier for them to overcome.
If they are new to programming that is an absolute non-issue. Don't talk about whitespaces at all, it's totally unnecessary, just tell them to follow the block indenting. AKA everything having the same left margin belongs to the same code block. Use how lots of books displays their table of contents, with chapters and subchapters differently indented as an example.