A Look at the Upcoming GNOME 2.6 428
A user writes "GNOME 2.6 is just around the corner, and I figured out that many GNOME users would like to know what's in store. So I installed GNOME 2.5 (development version for 2.6) in my box, and came up with a list of the new stuff that are coming up. (and just in case, copies of the article are also available here and here)."
Almost as interesting... (Score:5, Interesting)
Re:Almost as interesting... (Score:4, Informative)
My response (Score:3, Insightful)
I'll take your post point-by-point.
1. Just because something is 20+ years old, it doesn't mean it should be thrown away.
If you had bothered to RTFP (read the fucking paper) I linked to, you'd see *exactly* why usin
Re:My response (Score:3, Informative)
Actually, X used to be shipped with a basic widget set called the "X Toolkit", and also with a somewhat more advanced library called "X View" (which implemented more advanced concepts like callbacks ("notifiers"), etc).
I remember using these libraries when I wrote a font editor (around 1986 or so).
I found them easy to use, and bereft of much of the cruft that seems to have accumulated around more modern libraries (such as GTK+, etc.).
However, I don't think that XFree
Gnome 2.6 beta 1 release (Score:5, Informative)
More details here [osnews.com]
Don't forget to report the bugs!
Re:Gnome 2.6 beta 1 release (Score:3, Insightful)
I've been trying to install gnome off and on for the past month and a half. Problem is that it's a major bitch to install, even with neat little shell scripts like CVSGNOME I run into at least a dozen quirky dependencies. Each dependency is hell and a half to get working, and requires at least an hour googling and tweaking to get running.
The first time I tried to install I got up to the point where I needed some XML library, which needed a font library, whi
Re:Gnome 2.6 beta 1 release (Score:5, Informative)
As far the core GNOME libraries go, though, here's an excerpt from the dependencies section of my top-level makefile. If you start from the bottom of this list and work your way up, installing the dependencies before you install each library/package, you should be OK.
(you may already have some, like xrender, if you have recent XFree86)
GConf: popt glib ORBit2 libxml2 gtk+
libgnomeui: gtk+ libxml2 libgnome libgnomecanvas libbonoboui libbonobo
libgnome: glib gnome-vfs libbonobo GConf
gnome-vfs: glib libxml2 libbonobo ORBit2 GConf gnome-mime-data
libbonoboui: gtk+ libbonobo libgnomecanvas libxml2 GConf
libgnomecanvas: gtk+ libart_lgpl pango
libbonobo: glib libxml2 ORBit2
libgsf: glib libxml2
libglade: libxml2 gtk+ atk
gtk+: glib atk pango
pango: glib freetype fontconfig xft
ORBit2: popt glib libIDL
xft: fontconfig freetype xrender
fonts: fontconfig
fontconfig: freetype expat
atk: glib
xrender: render
render: pkgconfig
glib: pkgconfig
New File Selector - WOO HOO (Score:5, Informative)
But they have decided to remove the text entry box??? Eeep. I guess having the Ctrl-l shortcut to get one is OK (after all, it will most likely be geeks that want direct text on a file open) but thats one they need to document WELL.
On the whole though, it might be a good thing. I guess we'll have to wait and see. But text box or not, it can hardly be worse than the old one.
Re:New File Selector - WOO HOO (Score:4, Interesting)
Then again, I think that the Amiga did a lot of things right for the desktop part of the OS, and in many underlying areas. Not bad for such an old, quickly written system.
Re:New File Selector - WOO HOO (Score:5, Interesting)
Hyperbole is fun (Score:5, Funny)
Isn't this just a tad bit harsh? Imagine someone opening his TiVo box:
Re:New File Selector - WOO HOO (Score:2, Insightful)
It's important to remember that some users are much more skilled at using some aspects of the computer than are developers, and that "easy to learn" is not the same as "ease of use."
New File Selector with type ahead (Score:5, Informative)
It is certainly not just geeks who will want or need to type in file names. Skilled typists will not want to move their hands from the home row to open a file. Making them use the mouse to open a file is a bad idea.
So ... type in the name of the filename, anywhere in the window. This file selector has type-ahead support so it will search through the files looking for the next file that matches the string you have typed so far. If you've been using this feature extensively in Mozilla, it'll be second nature already.
Cheers,
Toby Haynes
Re:New File Selector with type ahead (Score:3, Interesting)
Re:New File Selector - WOO HOO (Score:3, Interesting)
Re:New File Selector - WOO HOO (Score:5, Insightful)
Isn't Evolution a mail reader and not a file browser ? Or did you mean Nautilus ?
Or you could leave both options open and let people use whichever they want. Like it's done now.
Besides, if I have both mplayer and xine installed, how does the One File Browser know which one to launch ? Or Emacs and Vi ? Or whatever ?
And yes, I realize you can set this in preferences; but suppose you want to use different tools for different tasks, despite the file format being the same ? Or if I just want to try out a new program ?
Because that would mean resizing application windows to fit them besides the directory windows, and be a lot more hassle than simply using a selector window ?
No, it's a useability feature. Lacking a separate file selector would give users unneccessary grief.
The more features you bundle into a single program, the less likely it performs any of them well, simply because different features (such as useability and low learning curve) conflict with one another.
Re:New File Selector - WOO HOO (Score:3, Informative)
File -> Open -> Select File
With a file browser system, it would be:
Un-maximize word processor -> open browser app -> find folder -> position windows for drag & drop -> drag & drop
There are additional problems. From my experience with Windows users:
1) They don't understand drag & drop
2) They don't understand hierarchical filesystems
They think in terms of applications, not files. They want to open a Wor
Re:New File Selector - WOO HOO (Score:4, Insightful)
EVERY TIME there's talk about file selectors, someone pops up and seriously suggests an option that not only encourages the need to use mouse, but actually requires it.
Especially for saving... instead of hitting ctrl-s (and quickly typing a name if it's the first time), I'm supposed to a) resize application window, b) locate file manager from open windows, or open one if it isn't running, c) drag icon somewhere? Excuse me, I think I need to puke.
Re:New File Selector - WOO HOO (Score:4, Interesting)
That still has failings: it doesn't guide you to which applications are valid for opening a certain type of file. If your system has many applications (typical result of a "Full" Linux install from commercial cdroms), then it'd be impossible to have an icon for every app without wasting pixels or inducing squinting. (Both of those are points of opinion that would bother some users and not others)
The system in KDE's Konqueror filemanager is better because it recognizes multiple possible associations for each filetype, allowing a user to right-click to select opening something in the non-default handler. (KDE's approach still needs some improvement; the right-click menus need some streamlining, for example)
Focusing on the "dialog vs filemanager" question ignores a more important UI design choice, though: Should each application include its own GUI code to pick files, or reference a centralized GUI system to perform that operation?
Many of the problems you've cited with SaveAs are the result of poor and inconsistent implementations of dialogs, not file-dialogs per se.
Ideally, the application program would be written at a higher conceptual level, where details like dialog boxes and icons are implementation trivia handled by a GUI control process. That way each user could load/save files in exactly the way she prefers, regardless of the biases of any specific application's author.
Re:New File Selector - WOO HOO (Score:4, Insightful)
That's subjective... I could claim that needing to drag an icon from a text editor to a whole other window (which I'd have to find and make visible first) is painfully slow compared to
That points to one big advantage of the dialog box approach: keyboard compatibility. Desktop environments which offer DnD should provide some (optional) way to perform equivalent actions from the keyboard, but I'm not aware of any having done so.
Digressing down that topic:
There have been some small steps made towards keyboard-controlled DnD, but I haven't seen any adequate yet. Of course, some systems let you push a button to steer the mouse from the keypad, but that's too awkward to consider. Some file managers include an abuse of the clipboard metaphor (like a Copy button which makes a "shallow [python.org] copy", instead of a "deep" one like every other Copy command besides Excel) to provide features that could be better solved by enabling DnD via keyboard. There are assorted taskbar-applets which provide a "shelf" to set down an icon in mid-drag; enhancing one of those to be controllable by keyboard would be the most direct implementation of a solution.
Re:New File Selector - WOO HOO (Score:3, Funny)
I hope they remember to send the KDE team a thank you note.
Re:New File Selector - WOO HOO (Score:2)
Re:New File Selector - WOO HOO (Score:3, Insightful)
"Well *my* kettle boils water in twelve different ways!"
-mike
Performance (Score:5, Interesting)
Linux is supposed to get us off the upgrade treadmill, but as far as I can see, GNOME just keeps getting bigger, slower and more complex. I've switched to XFce; it's so much faster. KDE is a hog too, but at least they're concerned about performance and efficiency as the 3.2 release shows.
Really, this is something we should think about. When gconfd is eating up 20 megs (resident), just for a configuration back-end, it's evident that we're getting sloppy. A faster Linux could work wonders in terms of corporate and home adoption, but we just seem to be chasing Moore's Law and copying Microsoft for bloat.
I'll try GNOME 2.6 when it arrives, but to give a better impression to newcomers we need to make things noticably faster, more elegant and more efficient than Windows. Companies have to support all this code into the future, after all...
Re:Performance (Score:5, Insightful)
Let's be clear about this: the vast, VAST majority of machines on the planet, in homes and in businesses, have 32M, 64M (and occasionally 128M) RAM. That's nowhere enough to run GNOME/KDE, OpenOffice.org and Mozill at a realistic and usable speed. When did we become just as bloated as Microsoft?
If the GNME developers don't step back, look at the problem and concentrate on efficiency and clean design (rather than flashy features and bloat), it'll lead to long term damage for Linux on the desktop. They're doing a great job bringing Linux to the masses, but the masses are going to be less enthusiastic about Linux when it keeps requiring hardware upgrades...
Re:Performance (Score:2)
Re:Performance (Score:2)
What are you talking about? Everywhere I look I see people with at least 128 MB RAM computers at home. 256 is not rare these days.
And let's face it: Windows XP won't run quickly with less than 128 MB RAM. I've seen some XP boxes with 128 MB RAM and they are *horribly slow*.
As Windows XP gains more and more market share, which means more and more people are u
Re:Performance (Score:5, Insightful)
Re:Performance (Score:4, Interesting)
IMHO, a window manager/desktop environment should always try to eat up as little space as possible. After all, the applications you run are getting more memory hungry as well.
BTW, nice to know that OS/2 goodies start to show up in GNOME! Now give me "Arbeitsordner" (don't know what the English name is, it's file manager windows which remember the documents opened from it and closing/reopening them when they are themselves closed/opened; sort of session management for single file manager windows), and I'll no longer miss anything from OS/2 Presentation Manager in Linux.
Re:Performance (Score:3, Insightful)
Yes OS/2 Warp did some of that but it also looks bad by today's standards and isn't nearly as advanced or polished.
Re:Performance (Score:2)
Re:Performance (Score:2)
Re:Performance (Score:2)
Of course, there are tradeoffs. It doesn't work like windows. It's different. It's better. It's every thing you ever wanted in a beer
Re:Performance (Score:2)
There are alternative environments for older systems out there. I think Gnome should definitely focus on efficieny but I don't think they should focus so much as to not incorporate new featur
Re:Performance (Score:2, Interesting)
I know that's not a particularly up to date processor, but it's not that uncommon for home users.
Re:Performance (Score:5, Informative)
With GNOME 2.0 and 2.6. Nautilus 2.0 got a huge speed boost compared to 1.x. Nautilus 2.6 is spatial and has because even faster. Windows appear instantly.
"Linux is supposed to get us off the upgrade treadmill, but as far as I can see, GNOME just keeps getting bigger, slower and more complex."
Not true. GNOME (and KDE!) have only gotten faster and faster. The exceptions are KDE 2.0 (which is slower than 1.0; but 3.0 is faster than 2.0 and 3.2 is even faster than 3.0) and GTK (which has become a little slower but also smoother because of extensive double buffering). On this system (Athlon 1.4 Ghz 390 MB RAM) I can definitely say GNOME 2.x is faster than 1.4. And GTK 2 feels smoother than GTK 1.
"When gconfd is eating up 20 megs (resident), just for a configuration back-end, it's evident that we're getting sloppy."
OMG not this again. I will repeat it *again*. Don't trust memory reports! The 20 MB you read includes shared memory! In reality it uses a lot less than 20 MB, somewhere around 6 MB on my system.
People who think software x is bloated by looking at the system monitor's memory report are just deceiving themselves.
And sometimes you need to use more resources in order to make things faster. Low memory usage doesn't always equal fast and high memory usage doesn't always equal slow!
Re:Performance (Score:5, Insightful)
That's the same argument Microsoft used to say that Windows 95 is faster than Windows 3.1. And on a system with plenty of memory, it is. But most people's experience with the hardware available at the time was that Win95 was much much slower, thrashing horribly with less than eight megabytes and still rather uncomfortable with less than sixteen.
Making a program twice as fast in CPU time but at the expense of using twice as much memory may not be a good trade-off. If you start running low on memory then you get a very steep performance drop from paging to disk (or not having enough RAM for disk cache, which is effectively the same thing). The most important benchmark is how it performs on a machine with, say, 64 megabytes of RAM, or whatever minimum level you want to require. Not shaving a few fractions of a second off times on recent hardware.
Re:Performance (Score:2)
No it isn't. I'm talking about 2.x and 1.4 on the same system! GNOME 2.x on an Athlon 1.4 Ghz + 390 MB RAM is faster than GNOME 1.4 on the very same system!
"But most people's experience with the hardware available at the time was that Win95 was much much slower, thrashing horribly with less than eight megabytes and still rather uncomfortable with less than sixteen."
Yet Win95 won and all the critics were beaten d
I disagree (Score:3, Interesting)
``Not true. GNOME (and KDE!) have only gotten faster and faster. The exceptions are KDE 2.0 (which is slower than 1.0; but 3.0 is faster than 2.0 and 3.2 is even faster than 3.0) and GTK (which has become a little slower but also smoother because of extensive double buffering).''
I can't comment on KDE, but when I upgraded from Gnome 2.2 to 2.4, I noticed significant performance hits. The desktop took longer to load, and in general, were noticably slower.
``On this system (Athlon 1.4 Ghz 390 MB RAM) I
In a corporate setting, 90% is shared. (Score:2)
Re:Performance (Score:4, Informative)
There are also several specific performance improvements in particular GTK+ widgets, and the GNOME Help system has had an incredible speed up.
Linux kernel 2.6 also makes a very noticeable difference, with it's pre-emptive schedule that gives priority to things that the user is doing.
Well if you are using XFce 4 (Score:2)
Only thing I miss in XFce is that konsole doesn't seem to want to work well. A tabbed multi terminal app is very very usefull to me :) a
Re:Performance (Score:2)
Of course, neither can touch any of the "lig
Re:Performance (Score:2)
Re:Performance (Score:5, Informative)
As for a low resource using window manager, check out XFCE4 [xfce.org]. It has the look and feel of Gnome but is far more zippy on old hardware. I run it (and occasionally fluxbox) on a P2 300 laptop with 128 MB RAM.
Wow... (Score:5, Funny)
That does it. I am shifting to GNOME.
gpdf (Score:5, Interesting)
Re:gpdf (Score:2)
I personally think that GGV is great, but I'm excited to see what gpdf might bring.
Re:gpdf (Score:2)
Even without that, I'd still use xpdf. Bookmarks are arugably of use, but thumbnails? No way.
File selectors? Why? (Score:5, Interesting)
Re:File selectors? Why? (Score:4, Funny)
Re:File selectors? Why? (Score:4, Insightful)
Spatial Nautilus? (Score:2, Insightful)
The windows take up 1/4 of a 1024x768 screen. I don't want to have a bunch of gigantic nautilus windows filling up my small screen.
Re:Spatial Nautilus? (Score:2)
Can anyone who's used both comment on whether "spatial nautilus" is the same sorta thing as Windows Explorer's "Open each folder in a new window" non-feature? It sure sounds like it from the article, but it's the first thing I turn off in Windows, so I have no idea if Explorer tries to remember size and location for each open folder or not.
Some of those linux paths get kinda deep, you know. I can't imagine trying to inspect something like
Gnome and KDE interoperability (Score:5, Insightful)
I've always thought that the reason having two (main) desktops (KDE and Gnome) is good is not necessarily because of the competition, but because there is a need to interoperate between the two, so sensible 'generic' programming interfaces need to be created. This should create more modular code, and modular code makes successful open source projects.
However, to what extent is this true? Can I, for instance, use just the Gnome file manager in KDE, and vice-versa? Is it an aim of these projects to make this level of interoperability a goal?
Re:Gnome and KDE interoperability (Score:3, Informative)
Yes, you can. Try nautilus --no-desktop (I think that is the switch).
Expect some stuff to break though. Noticeable KDE uses illegal URI syntax so drag and drop of files etc to/from KDE apps won't work so great I suspect.
Standardisation will allow us to reach these giddy levels of interop but it's not there yet, and to be frank most effort is going on stuff that actually matters (like the
Re:Gnome and KDE interoperability (Score:2)
I do think it matters a lot. Yes, I know standardisation of interfaces is very difficult, but we have the development of KDE apps and Gnome apps, for instance Gnumeric and Kspread. The developers of these programmes should not have to worry what desktop it will run on, they should work with generic programming interfaces.
I appreciate this is very difficult but as I said in my original post, it's a good thing to have both KDE and Gnome be
Re:Gnome and KDE interoperability (Score:2)
Re:Gnome and KDE interoperability (Score:5, Informative)
The KDE folks have also worked on some Qt-GTK toolkit inter-operability stuff. See also:
GTK-Qt [kde.org]
Ditto [kde.org]
Glib/Qt main loop integration [kde.org]
amongst others.
Re:Gnome and KDE interoperability (Score:3, Interesting)
However I see no sign of them doing some stuff that should not be hard. Some services should be provided by running a seperate program, so that program could be replaced. An obvious one is to make the file chooser be a seperate program. In my sample programs, statically linked with the fltk toolkit, the file chooser is sometimes 1/2 the entire size of the program! And you cannot change it. And every program runni
OS/2 lives again! (Score:2, Funny)
We only had to wait a decade or so for Moore's Law to make it usable...
Garg
Nice Job (Score:4, Interesting)
Liberal inspiration has, of course, been taken from the Apple way of doing things - the spatial navigation is, as noted in the Ars Technica [arstechnica.com] article, based on the pre-OS X MacOS Finder. And that's no bad thing, certainly if FOSS wants to move towards real usability on the desktop.
The file dialogue boxes are also notably similar to Mac OS X's way of doing things, although the puzzling (at least to me) scrollbars that the Mac uses to browse up and down a directory tree are here replaced with arguably simpler tabs. Very nice touch.
Personally I'll keep Mac OS X on this for the moment, if only to avoid kernel recompiles and incompatibilities arising from that, but hell, if I were a Windows user, I'd be sitting here asking myself why the fuck I am waiting till 2006 for Longhorn when I can have this now...
Zealots were quick [winsupersite.com] to criticise [winsupersite.com] the most prominent competition - Mac OS X 10.3 - in terms of eye candy on the desktop when it came to making comparisons with their darling Longorn (which is, rather pointedly, not available for purchase yet). Now that UNIX is offering two superb alternatives, one of them properly FOSS (and, more importantly, runnable on x86), Windows' days should surely be numbered...?
iqu
Re:Nice Job (Score:4, Insightful)
Yes, and like most holy wars, it's about obsolete ideas. Gnome and KDE are both serviceable desktop environments, but let's not kid ourselves: imitating Windows and MacOS should not be the future of computing.
Personally I'll keep Mac OS X on this for the moment, if only to avoid kernel recompiles and incompatibilities arising from that,
Whatever makes you happy, dear. Personally, I dumped Mac OS X because I got tired of the manual upgrades and install hassles; Debian has been much less effort to maintain and has a lot more software available for it. And kernel upgrades just work, with no recompiles, with Debian.
Re:Nice Job (Score:3, Interesting)
Away from the desktop on x86, I'm a Debian man, and it has done a superb job as a router and web server at home. The upgrades are superbly simple for a Linux-based operating system. And, should I be bothered, I'm sure it might make a reasonable desktop...
But you have piqued my curiosity - I am intrigued, what, pray tell, do you mean by "manual upgrades," "install hassles" and "a lot more software available for
Comment removed (Score:5, Informative)
Nicely written article!! (Score:5, Insightful)
It covers the functionality well, does not break the continuity and was fun to read.
If only we had more articles like this, slashdot might gain few more subscribers.
you guys are so mean (Score:5, Funny)
are you trying to break a new record or what? ^_^
twist on an old alaskan joke. (Score:4, Funny)
About spatial navigation (Score:5, Interesting)
The defining characteristic of spatial navigation is that a folder window IS the folder. That's why there cannot be two windows on screen that show the same folder, and why there are no navigation controls. The fact that folders open in the same place as when you left them is just a result of the fact that the position is an attribute of the folder itself, not of a windows which is a viewport of a folder. It's a subtle difference that people who have worked with explorer-like browsers for too long may have some difficulty adapting to.
Personally, I feel more comfortable with an explorer-like fs browser, maybe just because I'm used to it. It seems easier to manage large trees this way. But I can easily see why new computer users would be less confused with the spatial model. It's hard for some people to understand (and remember!) that a dozen of shortcuts to "My Documents" in different places all point to the same folder "underneath".
Re:About spatial navigation (Score:4, Insightful)
True Spatial Navigation is quite good really. As long as you have options for opening the parent folder, and autoclosing the parent folder when opening a new folder to keep clutter down.
No pattern match in file-selecter (Score:3, Insightful)
Favorite quote (Score:2, Funny)
Watch out for line breaks in article (Score:5, Funny)
As a part of the Bangla/Bengali GNOME l10n team, I decided to give the GNOME HEAD
those bengali guys sure are strange...
Spring loaded folders (Score:5, Insightful)
But I am a bit worried, some folder hierachies in Unix is quite deep.
Perhaps they should introduce something like the Mac spring loaded folders.I.e. if you want to move a file down in the hierachy you just drag and hold it over a folder, after a short while the window opens, and you hold the file over a folder in that window, until that opens and so on. When you finally reach the right folder you drop the file, and all windows you encountered on the way is closed automatically.
Gnome for the Developer (Score:3, Insightful)
Not trolling or anything, but here goes...
As a developer, I have always been interested in writing software for Gnome since 1.x. The one thing that has really set me back from doing so is the fact that with each and every iteration, something in the very core of Gnome changes and more often than not, those changes mean that you would have to recode large chunks of your software to cope with the changes.
Yuh, sure all your Gnome 1.x apps will still run but it won't be able to use any of the new features in 2.x. This comes naturally, since this is after all a "major release" upgrade. They've really done it with 2.x this time, something major changes with each "minor" version is released. I know this is all about bringing Gnome closer into the "integrated desktop where you have everything you need to do everything you need" that it is trying to achieve.
Case in point, this whole new-fangled "Object-Oriented" metaphor. Now not only do I probably have to learn a whole new set of interfaces to get desktop integration going for programs that I write for Gnome, I also have to learn how to operate this contraption. I mean come on! Do we really need all this HIG crap?!? My UI was "usable", at least for me, before all of this HIG things were implemented. If the developers want to implement this HIG thing, then go ahead and do it but it would also be nice to let users with "bad habits" choose to revert to the old UI behavior when they want. And for heaven's sake, leave the API's unchanged until the next major release! Being a developer for Gnome is a lot like being Sisyphus. [colorado.edu]
Now I realise why there are more apps written for KDE than for Gnome.
</rant>
Yuh, I know this rant probably doesn't make any sense to you. But maybe that's because you haven't been around when Gnome 1.x was new and Miguel was still sane.
(puts on asbestos underwear and ducks under the sink)
Re:Gnome for the Developer (Score:3, Insightful)
Yes. Or rather, each and every one of us might not be in dear need of it, but if we want Linux and free software to grow into the mainstream, then we sorely need human interface guidelines and more of the kind. Open source programmers write software to scratch their personal itch--that itch most often doesn't include creating user interfaces that follow good user interface practices,
Re:Gnome for the Developer (Score:3, Informative)
I have several apps originally written against GTK 1.3 (a prerelease of 2.0). They compile perfectly against GTK 2.4. Nowhere has backwards compatibility been broken.
Now not only do I probably have to learn a whole new set of interfaces to get desktop integration going for programs that I write for Gnome
The Nautilus changes are irrelevent to other GNOME apps. Unless you've was jimmying around with Nau
I don't get it (Score:3, Interesting)
I thought (and admidt I may be wrong) that the point of 'spatial' was to change the way files are stored all together. So that instead of putting an mp3 in
I'd like to see something to replace the file/folder Navigational method. It breaks down once you've got over 1000+ individual files scattered on your hard disk.
Re:Windows Longhorn renders all this obsolete (Score:5, Informative)
GNOME ... catches the SVG fever ... quite a few of the games have switched to SVG based graphics, which is a really nice thing, and a move towards the right direction
FYI : SVG = Scalable Vector Graphics
Re:Windows Longhorn renders all this obsolete (Score:5, Funny)
...due somewhen in 2006 will render a 2004 software obsolete. Hey Sherlock, here's a cookie for your perspicacity !
Re:Windows Longhorn renders all this obsolete (Score:3, Informative)
http://www.gnome.org/~seth/storage/fea t ures.html
I would be surprised if there was many new things in Longhorn when it finally gets released. Not so much because Microsoft hasn't the technical knowhow to produce something new, but if Microsoft alters their GUI too much existing windows users will not feel at hom
Re:Windows Longhorn renders all this obsolete (Score:3, Interesting)
Microsoft only innovate in ways to manipulate the law.
Re:File selector! (Score:3, Informative)
Re:File selector! (Score:2)
could be, if we were able to see it:
Forbidden
You don't have permission to access
Apache/1.3.29 Server at sdg.agreatserver.com Port 80
agreatserver? (Score:2, Funny)
Complete Text (Score:3, Informative)
Sayamindu Dasgupta
The boring intro...
As a part of the Bangla/Bengali GNOME l10n team, I decided to give the GNOME HEAD branch a spin - in order to find out what's new, as well as to get an estimate of how much we would have to translate (I hate that part of the job) to attain supported status. The last time I did this, I also wrote an article about what I saw, but unfortunately, I never learn from my mistakes - so here I go again....
However, before jumping in in
Re:Wow (Score:2, Interesting)
I don't think so. On my laptop (166MhZ, 64MB) I get along with my WindowMaker. (Of course it depends wich applications you want to use.) On my Desktop at work (Win2000 with cygnus) I also run a WindowMaker and I'm so contempted that I switched to WindowMaker at home as well (360MB, 850MhZ). Regards
Re:Wow (Score:2, Interesting)
Perfection is achieved not when there is nothing left to add, but when there is nothing left to remove.
-Some Wise Guy
I use fvwm2 and I have an XP2600+ and a gig of RAM. I use a lot of Gnome-ish apps but evey time I use a different wm it lasts about half a day and I'm back to fv.
There is really only one reason you (or I) should stop using it; because you want to. That being said, Gnome sure is purdy.
ICEWM (Score:2)
Re:ICEWM (Score:3, Insightful)
dillo for browsing and nedit for editing works fine on it. For real text processing even abiword is workable.
You can use such a machine perfectly well, you just have to be picky about what you use on it.
Jeroen
Re:Wow (Score:2)
Re:Wow (Score:2)
Anyway, try XFce4 if you want eyecandy on a lowspec box. Blackbox is also a nice environment once you get used to the lack of an iconbox (minimized apps just disappear). Windowmaker is okay for lowspec desktops but uses too much screen real estate for a laptop IMHO.
Re:Yuk (Score:4, Informative)
GNOME is quite themable; if you don't like the muddy colours, use another theme.
Re:Its called KDE 3.2. (Score:5, Insightful)
It'll be interesting to read a decent "neutral" KDE 3.2 vs Gnome 2.6 article though! And it also has to be said that the competition between KDE and Gnome really had driven both communities to excellence. Als competition has not deterred them from cooperating in freedesktop.org - something to be encouraged until hopefully one day somehow the libraries can be unified.........
I tried to use GNOME (Score:3, Interesting)
So, I switched to KDE, purely so I could carry on working. And suddenly I noticed everything was a LOT faster. Even simple things like application window redraws were way faster.
So when I rebuilt the machine, I didn't even bother installing GNOME. I'll look at it again when it's about 4x as fas
Re:I tried to use GNOME (Score:3, Interesting)
Re:Its called KDE 3.2. (Score:3, Informative)
About as interesting as a "neutral" Britney Spears vs. Paris Hilton article.
something to be encouraged until hopefully one day somehow the libraries can be unified.........
They could have been unified long ago if the Qt license (GPL) didn't prevent it. You see, ultimately, the difference between KDE and Gnome doesn't come down to technology, it comes down to licenses, and the Qt license just doesn't work for many peop
Re:Its called KDE 3.2. (Score:3, Interesting)
About the licensing; You're absolutely right. Trolltech and KDE have worked out an agreement http://www.kde.org/whatiskde/kdefreeqtfoundation. p hp that I think addresses most issues people have with the QT license. Trolltech has developed a great desktop environment and cross OS development toolkit and commercial licensing has paid for much of it (which in turn allowed Kdevelop to become such an incredible tool for linux/windows/osx GPL development).
Re:Its called KDE 3.2. (Score:3, Informative)
I should also point out that some people have trouble supporting the Qt licence that KDE is built on. Qt is open (sort of) and closed (sort of), and there seems to be little concensus about how open it is -- having read the license myself, I'm still not sure. Thus the reason why the Desktop Linux project isn't supporting it.
A better way to work your post is that the Gnome 2.6 beta screenshots appear
Re:So good, so dull.... (Score:3, Informative)