Slashdot Mirror
Gnome 2.4 Release (d)
chendo writes "Gnome 2.4 will be released today. Here is the link to the article on Ars Technica. GNOME 2.4 is the result of quite a bit of work toward complying with the GNOME Human Interface Guidelines (HIG), which mainly focus on user interface consistency and predictability. This release has also undergone some general polish, and it can finally be said that the GNOME 2 platform has achieved maturity with this release. The Epiphany web browser, a major new component of GNOME, also makes its debut with this release. (From Footnotes)"
All KDE and Gnome Zealots please board this thread, forsaking all other threads within this topic.
;)
To make this new guideline more comfortable for the really and truly devoted:
- KDE had all of the new features three releases ago. Please get Gnome development out of the way of The One Real GUI(tm)
- KDE whiners: eat our dust! (Gnome, The True Gui for Real People)
A Console/Lynx user... (Yeah, right...
Karma? What's that again?
When is _is_ out, you'll have all sorts of release notes and screenshots to look at. Slashdot is announcing non-existant releases again :)
Well, GNOME has already won awards for its accessibility work, and it has a mature framework for dealing with this (disclaimer: I've never tried it, just heard people praising it).
The article itself points this out in two places.
From the (f*******) article:
Gnome 2.4 ships with GOK, an award-winning dynamic onscreen keyboard. It supports Direct Selection, Dwell Selection, Automatic Scanning and Inverse Scanning, and includes word completion. A detailed overview can be found on the GOK website.
Gnopernicus, the second accessibility application to ship with GNOME, provides a number of assistive technologies for people suffering from visual impairment. Most notably, it includes a screen reader, a screen magnifier and a Braille writer.
One of the big concessions that I've heard about Windows is that it has a lot of accessibility features that weren't present in other previous GUIs.
That's actually not true. The X-Windowing-System has come with xmag virtually for ever. High contrast themes are not hard to create. You can make icons and fonts whatever size you want. We've even got sticky keys. The only thing X is missing as far as accessibility is keyboard control of the mouse cursor. Then again, you can always run ratpoison and be rid of the rodent forever.
You've been lied to my friend.
Disclaimer: Haven't used pure Gnome in quite a while, perhaps some of the points below have been handled by now.
I hate the fact that the Windows taskbar reflects the order in which the apps are launched and then cannot be changed. If you're going to have a taskbar interface, then fair enough chronological order seems a sensible default. However once launched, I really want to be able to drag that indication to whatever position I want in the taskbar.
For example, at work on my NT4 box I have a standard set of apps open most times. They are Notes (ugh), two Firebird windows, Putty and a Remote desktop connection. Apps after that can come and go, but I want those apps always in the same place so I don't have to hunt for them later.
I'm also an OS X user, and although I'm aware of criticism of the dock there's certainly one thing to be said for it - your most frequenctly used applications always appear in the same place, both for launching and for bringing to the front.
As a quick aside - anyone else remember the Apple Human Interface Guidlines circa System 7-era, incorporating the Principle of Muscular Remembrance? The idea is that important stuff is always in the same place, every time, so that the user doesn't even have to conciously think about where to find things. It's the reason Macs have a single menu bar, at the top of the screen. It seems to me to also be a key thought behind the dock.
Cheers,
Ian
The GNOME section icon is out of date: GNOME changed their logo about a year ago. I've done a new topic icon with the new logo if one of the slashdot editors is interested in putting it in.
were you expecting to see a sig here? perhaps you'd rather see the inside of an ambulance!
Try Shift-Numlock, it worked for me for ages
The Gnome-panel bug is a new one for me; filing a bug report would likely be very appreciated by the devels.
Sawfish: Just run it. There are some people hacking on it, I believe, so it should be maintained. And tell the sawfish devels if there is something you miss.
The terminal: They are all the same application with multiple windows; cuts down on resource use. Of course, if it dies, so do they all - that's the downside. You can, however, start a new terminal, explicitly stating that it should not be another instance in an existing gnome-terminal application:
gnome-terminal --disable-factory
That will give you an independent terminal instance that will not be affected. Of course, you pay by a bit higher total resource use, but that is probably worth it for you.
Trust the Computer. The Computer is your friend.
You gotta love Ars. The first few paragraphs describe in layman's terms why Windows and the Mac have consistent GUIs and why Linux does not. I hope the main drivers of Linux desktop adoption (the Gnomes, KDEs & Red Hats of the world) pay very close attention to the implications of this message. It's been said many times, but warrants repeating again: Linux desktop adoption is suffering from a lack of consistency across applications.
5 is a button click and and you change what button it is by clicking / for left, * for both, and - for right. + is a double-click. 0 is button hold, . is release.
-N
I've nothing to say here...
Actually, Mandrake is compiled for i686 but only using the i586 instruction set, while Red Hat is compiled for i686 utilising the i486 instruction set for compatibility. Why it's still called 'i386' is anyone's guess.
Michel
Fedora Project Contribut
As much as I like gentoo, it doesn't release packages immideatelly after they are released.
/etc/make.conf
nano -w
Advanced Masking
# ================
#
# Gentoo is using a new masking system to allow for easier stability testing
# on packages. KEYWORDS are used in ebuilds to mask and unmask packages based
# on the platform they are set for. A special form has been added that
# indicates packages and revisions that are expected to work, but have not yet
# been approved for the stable set. '~arch' is a superset of 'arch' which
# includes the unstable, in testing, packages. Users of the 'x86' architecture
# would add '~x86' to ACCEPT_KEYWORDS to enable unstable/testing packages.
# '~ppc', '~sparc', '~sparc64' are the unstable KEYWORDS for their respective
# platforms. DO NOT PUT ANYTHING BUT YOUR SPECIFIC ~ARCHITECTURE IN THE LIST.
# IF YOU ARE UNSURE OF YOUR ARCH, OR THE IMPLICATIONS, DO NOT MODIFY THIS.
#
ACCEPT_KEYWORDS="~x86"
You'll get stuff a LOT faster. I've been using that "unstable branch" (if you will) for a year and a half or so with zero show-stopper problems on 5 or so machines. OK, OK, there's a bad realease from some developer from time to time, but Portage will down-grade it next emerge -u world if there's something really bonked with a package or ebuild.
I'm not a prophet or a stone-age man,
I'm just a mortal with potential of a super man.
256mb of RAM should be fine. The difference in memory usage between a bare windowmaker desktop and a KDE one is about 60meg (~34meg -> ~90meg). That's worth about what, $20? Considering the vast amount of functionality that gives me, I think that's a worthwhile trade off.
Back in the day, I was a major lightweight system zealot. I used Ratpoison or Ion at work (if you though fvwm was lightweight, you ain't seen nothing yet). Then I realised that saving 0.5 seconds on launching a terminal window didn't make me any more productive, but having excellent integrated apps like kmail and konqueror did.