Can someone please explain HDTV to me? While I was in the states this summer, I saw HDTV on a ~60 inch television. It was amazing. What exactly is this technology, and more importantly, what's the status in Europe?:-)
Not in Denmark (and I suspect, many other countries). We are moving to chip-based cards instead. Actually, Denmark is almost fully converted away from magnetic cards.
Now here is a good example of using big words in titles that are not at all covering for the real thing.
"iTunes Europe goes Live". I didn't know that Europe was only UK, France and Germany.
This is the same thing as to say that USA is California and Florida.
Why is this important to prove? Even though downloading music doesn't hurt CD sales, does it make it more right?
If downloading music becomes legal, *then* it will hurt CD sales. Without doubt.
With the upcoming release of Mozilla 1.0, Netscape 7 will be based on that. I really hope reviewers, developers and users will take a new view on Netscape so Netscape can gain some of the lost market share. I'm tired of seeing websites which simply don't care about Netscape/Mozilla support...
And don't start saying "hey, I don't need Netscape, I want plain Mozilla!". You're right, but Netscape is for (l)users. If Netscape 7 has success, you'll also have more luck surfing the internet with your Mozilla browser.
By the way, MozillaZine is also a great source of information for Mozilla-fans.
I have been programming gtkmm for about a year now, and I really love the APIs. If you know the STL, you'll also feel at home with the gtkmm API.
As an example, the Gtk::Notebook widget provides push_back() for pushing back your widgets, and you can iterate through the list using rows().begin() and rows().end().
Another thing is that you won't have to fiddle with MOC. And no reason to add 'Q_OBJECT' to all of your classes.
I'm looking forward for the Windows support, then we'll have a *great*, 100% free widget set for Windows.
You are wrong. Look at std::vector, it has both a [] operator and a at() member - the at() member throws an exception while [] does not, you have a choice.
To sum up the different comments - the only real downside is the implementations on the different platforms. First of all, not all compilers have STL implemented fully (I think g++ 3.1pre has it all). Second, older systems and embedded systems totally lack an STL implementation.
The rumours about the STL having a lot of overhead because of virtual functions etc. is not true - one of the goals with the STL was speed and therefor it was implemented without virtual functions, but just concrete templated classes.
Sure, a std::vector has overhead compared to a built-in array, but development is usually faster using vector because it dynamically resizes and it throws exceptions when trying to reach an element which is out of range.
Slashdot Mirror
Can someone please explain HDTV to me? While I was in the states this summer, I saw HDTV on a ~60 inch television. It was amazing. What exactly is this technology, and more importantly, what's the status in Europe? :-)
I live in Denmark myself.
Not in Denmark (and I suspect, many other countries). We are moving to chip-based cards instead. Actually, Denmark is almost fully converted away from magnetic cards.
Now here is a good example of using big words in titles that are not at all covering for the real thing. "iTunes Europe goes Live". I didn't know that Europe was only UK, France and Germany. This is the same thing as to say that USA is California and Florida.
Why is this important to prove? Even though downloading music doesn't hurt CD sales, does it make it more right? If downloading music becomes legal, *then* it will hurt CD sales. Without doubt.
TuxTime has been up for a long, long time, it even has more participating computers than the "New Uptimes Project".
I read half-way through the article and the site gets slashdotted.
With the upcoming release of Mozilla 1.0, Netscape 7 will be based on that. I really hope reviewers, developers and users will take a new view on Netscape so Netscape can gain some of the lost market share. I'm tired of seeing websites which simply don't care about Netscape/Mozilla support...
And don't start saying "hey, I don't need Netscape, I want plain Mozilla!". You're right, but Netscape is for (l)users. If Netscape 7 has success, you'll also have more luck surfing the internet with your Mozilla browser.
By the way, MozillaZine is also a great source of information for Mozilla-fans.
Go see the gtkmm FAQ: Why use gtkmm instead of GTK+?.
Working with STL-style interfaces, and having the chance to use std::string and std::vector to input data to your widgets is just *great*.
Of course, all the other advantages of C++ can be used as an argument on why to use the C++ interface.
You never mentioned why you don't want to use the C++ interface, maybe you should mention what you consider the disadvantages.
In one one his slides, they are compared pretty nicely:
3 /s lides/html/img6.htm
http://www.murrayc.com/murray/talks/2002/GUADEC
I have been programming gtkmm for about a year now, and I really love the APIs. If you know the STL, you'll also feel at home with the gtkmm API.
As an example, the Gtk::Notebook widget provides push_back() for pushing back your widgets, and you can iterate through the list using rows().begin() and rows().end().
Another thing is that you won't have to fiddle with MOC. And no reason to add 'Q_OBJECT' to all of your classes.
I'm looking forward for the Windows support, then we'll have a *great*, 100% free widget set for Windows.
You are wrong. Look at std::vector, it has both a [] operator and a at() member - the at() member throws an exception while [] does not, you have a choice.
To sum up the different comments - the only real downside is the implementations on the different platforms. First of all, not all compilers have STL implemented fully (I think g++ 3.1pre has it all). Second, older systems and embedded systems totally lack an STL implementation. The rumours about the STL having a lot of overhead because of virtual functions etc. is not true - one of the goals with the STL was speed and therefor it was implemented without virtual functions, but just concrete templated classes. Sure, a std::vector has overhead compared to a built-in array, but development is usually faster using vector because it dynamically resizes and it throws exceptions when trying to reach an element which is out of range.