It won't be binary compatable for sure, but it'll be mostly source compatable. Many applications written for GTK 1.2 have just worked (or required minimal changes) when ported to 2.0. That being said, if you want to use the cooler new features (new text and tree widgets) you need to change the code a little.
The GNOME port of gmc is in a separate directory, and is fairly innobtrusive in the mc sources. I imagine they will go away eventually, but they don't really get in the way of mc.
GMC has multiple panes available, you just need to bring up a second window. The code is the same inside. If you notice, when you do an action (like copy) in mc, your default target is the opposite pane. Likewise, in gmc, your default target is the last window you were in, or the desktop.
GMC has a lot of the same features that the original mc had, but in retrospect was missing an important one -- that of keyboard navigability. Too many actions required too much mousing.
While the details are still being worked out, the general consensus is that anyone who considers themselves part of the gnome community can join the
GNOME Foundation (or rather, the GNOME community _is_ the GNOME foundation). This is similar to the way that the IETF does membership. You will not need to pay money or be a member of a company in order to join.
Most of the work in GNOME-libs nowadays consists of removing unnecessary features, and trimming it down to size. Expect the next release of GNOME to have smaller core libraries, with the stuff people really needs in them.
I fear that the control-center, one way or another, will not be able to avoid this. In order for there to be any chance of either maintaining the capplets, or installing new ones, they need t o be separate modules.
I use a kinesis here, and hit the curly braces with my ring finger. I don't notice it at all when I program, and will say that it has saved my wrists. If you don't like the location, get the configurable one and remap it -- I've switched many keys to more useful locations.
GTK+ and the rest of the GNOME libraries are currently API frozen. Now is a great time to start using them.
It takes a little time for all the mirrors to pick it up. It's there though, and a few mirrors seem to have it already.
It won't be binary compatable for sure, but it'll be mostly source compatable. Many applications written for GTK 1.2 have just worked (or required minimal changes) when ported to 2.0. That being said, if you want to use the cooler new features (new text and tree widgets) you need to change the code a little.
Alex just posted another screenshot to gtk-devel-list. This one is of dia, and is a little more interesting then the ones above.
http://www.lysator.liu.se/~alla/files/diafb.png
The GNOME port of gmc is in a separate directory, and is fairly innobtrusive in the mc sources. I imagine they will go away eventually, but they don't really get in the way of mc.
GMC has multiple panes available, you just need to bring up a second window. The code is the same inside. If you notice, when you do an action (like copy) in mc, your default target is the opposite pane. Likewise, in gmc, your default target is the last window you were in, or the desktop.
GMC has a lot of the same features that the original mc had, but in retrospect was missing an important one -- that of keyboard navigability. Too many actions required too much mousing.
While the details are still being worked out, the general consensus is that anyone who considers themselves part of the gnome community can join the
GNOME Foundation (or rather, the GNOME community _is_ the GNOME foundation). This is similar to the way that the IETF does membership. You will not need to pay money or be a member of a company in order to join.
Hey, what's wrong with Solitaire in GNOME???
It was intended to be both a user conference as well as a developer conference. In practice, it was more of a developer's conference, though.
It's pronounced Guh-Nome. Like Guh-Nu.
Most of the work in GNOME-libs nowadays consists of removing unnecessary features, and trimming it down to size. Expect the next release of GNOME to have smaller core libraries, with the stuff people really needs in them.
I fear that the control-center, one way or another, will not be able to avoid this. In order for there to be any chance of either maintaining the capplets, or installing new ones, they need t o be separate modules.
I use a kinesis here, and hit the curly braces with my ring finger. I don't notice it at all when I program, and will say that it has saved my wrists. If you don't like the location, get the configurable one and remap it -- I've switched many keys to more useful locations.