Slashdot Mirror


Gnome 2.0 Beta 2 Released

plastercast writes: "Following the release of GTK2, the second beta of gnome 2.0 is available. There are also release notes here. From Gnotices: 'The GNOME 2.0 Desktop is a greatly improved user environment for existing GNOME applications. Enhancements include anti-aliased text and first class internationalisation support, new accessibility features for disabled users, and many improvements throughout GNOME's highly regarded user interface.'"

3 of 237 comments (clear)

  1. GNOME 2.0 by nzkoz · · Score: 4, Informative

    For those of you who aren't too keen on manually downloading all the individual packages and their dependencies, you may wish to try garnome (http://www.gnome.org/~jdub/garnome/).

    It behaves a bit like the BSD ports tree as it'll download and install all the necessary packages. Even better, it'll install them in an out-of-the-way place so you can keep running gnome1.2!

    --
    Cheers Koz
  2. release codename by bob@dB.org · · Score: 5, Informative

    I bastun bor vi allihopa = we all live in the sauna (it's swedish)

    --
    Acts@core.mailboks.com Acrux@core.mailboks.com Adam@core.mailboks.com Adar@core.mailboks.com Ada@core.mailboks.com
  3. Re:It's all so windowesque ... by WasterDave · · Score: 4, Informative

    kcalc has the biggest footprint I've ever seen for a calculator

    I have a suspicion this is to do with the C++ linker problem. In a nutshell, GCC"s handling of relocating libraries when they address collide sucks. It's slow. Really slow. The KDE team have been attempting to get over this by creating one process that loads most of the libraries - kdeinit, then forking the process to be the individual applications. The long and the short of this is the libraries remain loaded at the same address, don't have to reload and relocate, and all the processes can share the same code pages since they're copy on write.

    Don't worry, they know it's a hack too.

    There's a lot of work going into making it such that the GCC linker can build libraries to different default virtual memory addresses, hence stopping the loader from having to relocate libraries. When this happens the individual distros can be built with non colliding libraries, the kdeinit hack can go away and all will be at peace in KDE land. Personally, I'd delay 3.0 until the situation is sorted, but it's not my project.

    Dave

    --
    I write a blog now, you should be afraid.