GTK has to work in an environment without a file manager, so it needs a baby one built in as a fallback. What people are looking at here is the fallback GTK file selector.
The API supports pluggable file managers, so if Nautilus/whatever is selected as the default file manager, a nautilus window could pop up when you click on "Open file...".
GTK has signals and slots, it has single inheritance, it has multiple inheritance of interfaces, it has run time introspection, it has about Java's level of static typechecking (very slightly less).
People get hung up on the implementation language. It doesn't really matter (except in extreme cases). Writing in C beings many benefits (portability, ease of foreign language bindings, simplicity).
GTK2 is mostly slower because all text layout is now done with pango. Pango does a huge range of language typesetting, and AFAIK, Qt is still behind in this area.
All lenses are limited by diffraction. You can only get so much detail through a piece of glass. A typical large-format lens will have the equivalent of about 15,000 by 15,000 pixels in the centre of the field of view, falling to about 7,000 by 7,000 at the edges. So 10k x 10k pixels (100 MP) is about the best resolution there is.
You can get away with much less than this. This article compares a 10MP digital versus medium format film on a drum scanner.
What you're asking X to do is exactly what GDK does. It's not a toolkit, it's a layer over Xlib which hides the complexity of the colour model. It's very quick: you can use it for video windows, for example.
Here's a link to the docs. As a side benefit, your code becomes portable to win32 too.
Some systems really do need the visual/colormap stuff. If your hardware is a 4 bit deep framebuffer plus a colormap, you're going to need exact control over it. Other systems let you have different bit depths in different windows (!), and you need to be able to control that too.
Xlib is rather low level and somewhat of a pain to use (to say the least). If you want something more abstract, use a higher level toolkit. In GTK/GDK, for example, everything is RGBA and the library maps this to the X visual nonsense for you.
The visual stuff is there for (eg.) = 8 bit displays where apps really do need to have exact control over colormaps. No longer useful on the desktop, but very handy for embeded or PDA developers.
It only does rotate/scale/translate (all I need), but it can do any size image on a 32 bit machine. The screendump shows a 43000 by 30000 pixel image. Linux, win32 and mac.
A friend mailed me this earlier today, might help you:
I've just applied the 5 windows patches released today to 160 boxes in under 2 hours. Takes a little bit of getting used to how it works but I highly recommend it. It does service packs now too.
On the 2nd problem, what has happened is that some application has grabbed the mouse pointer and forgotten to ungrab it.
You can break the grab by switching to another desktop and back again. So if you're on desktop 1, press CTRL-F2 to jump to desktop 2, then CTRL-F1 to jump back to where you started. Voila! You mouse will work again.
If the app grabbed the keyboard as well, you're in trouble:) but it's usually just the mouse they take.
For good colour, your filters should be a linear combination of the CIE XYZ curves. RGB, CMY, whatever, as long as you can make XYZ out of them, you're OK.
Nikon use CYMG because the filters are much brighter, so you get less noise in the RGB image you make at the end.
Slashdot Mirror
Here's a shot of 1.3.23 (I think), the final is pretty similar.
GTK has to work in an environment without a file manager, so it needs a baby one built in as a fallback. What people are looking at here is the fallback GTK file selector.
The API supports pluggable file managers, so if Nautilus/whatever is selected as the default file manager, a nautilus window could pop up when you click on "Open file ...".
Brian Millar's excellent Executive summary of Hamlet in Powerpoint. It includes a handy SWOT analysis of the Danish royal family.
He's also got a PDF version.
People get hung up on the implementation language. It doesn't really matter (except in extreme cases). Writing in C beings many benefits (portability, ease of foreign language bindings, simplicity).
No, GTK+ is LGPL. You can do closed-source development with GTK on any platform without getting a licence. Check the page.
The last moon/mars thing that Bush Sr started (and was rejected by congress) in '92 was budgeted at $400 bn.
GTK2 is mostly slower because all text layout is now done with pango. Pango does a huge range of language typesetting, and AFAIK, Qt is still behind in this area.
You can get away with much less than this. This article compares a 10MP digital versus medium format film on a drum scanner.
Here's a link to the docs. As a side benefit, your code becomes portable to win32 too.
Some systems really do need the visual/colormap stuff. If your hardware is a 4 bit deep framebuffer plus a colormap, you're going to need exact control over it. Other systems let you have different bit depths in different windows (!), and you need to be able to control that too.
The visual stuff is there for (eg.) = 8 bit displays where apps really do need to have exact control over colormaps. No longer useful on the desktop, but very handy for embeded or PDA developers.
Yes. It's the same code, they're just trying to open up the development process a bit to get new features in faster.
At least GTK is planning to switch to it, I guess QT as well.
You want SDL:
http://www.libsdl.org/
I think it's earlier than that. I remember a maglev test track outside Cambridge (UK) in the 1970s.
http://www.vips.ecs.soton.ac.uk/
It only does rotate/scale/translate (all I need), but it can do any size image on a 32 bit machine. The screendump shows a 43000 by 30000 pixel image. Linux, win32 and mac.
A friend mailed me this earlier today, might help you:
I've just applied the 5 windows patches released today to 160 boxes in under 2 hours. Takes a little bit of getting used to how it works but I highly recommend it. It does service packs now too.
http://sourceforge.net/projects/mbsafu/
There are various test windows builds, check out the gimpwin-users list:
s ag e/10439
http://groups.yahoo.com/group/gimpwin-users/mes
Reported to fail horribly on win9x.
I'm too late and no one will see this post, but here's a link to my favorite strange paper: REAL TIME ELEPHANT DETECTION USING INFRASOUND CALLS.
On the 2nd problem, what has happened is that some application has grabbed the mouse pointer and forgotten to ungrab it.
:) but it's usually just the mouse they take.
You can break the grab by switching to another desktop and back again. So if you're on desktop 1, press CTRL-F2 to jump to desktop 2, then CTRL-F1 to jump back to where you started. Voila! You mouse will work again.
If the app grabbed the keyboard as well, you're in trouble
For good colour, your filters should be a linear combination of the CIE XYZ curves. RGB, CMY, whatever, as long as you can make XYZ out of them, you're OK.
Nikon use CYMG because the filters are much brighter, so you get less noise in the RGB image you make at the end.
Wow, did you get a photo?
Acutally, water boatmen are (usually) diving beetles, a different family. The common UK name for the Water Strider is the Pond Skater.
abiword is nice, but it's still missing a lot of quite basic features (eg. tables). OOo is much closer to a drop-in word replacement.
GIMP only rellly does 8 bit RGB, that's the real problem with colour output :-(
GIMP2 is supposed to do CMYK, LAB, 16 bit, etc. which should take it closer to the pro- level. But that's a year or two away still (AFAIK).
The Ardour people have a long page discussing exactly this issue.