GNOME 2.6 Reviewed 169
Kethinov writes "I just read this article reviewing GNOME 2.6 via the 2.5 development version. Many screenshots, plus extensive discussion on the new direction Nautilus is taking among other things. Worth a read. (A mirror would be nice ;)" Sorry - I duped this. Mea culpa.
Mirror list (Score:5, Informative)
Re:Mirror list (Score:4, Informative)
Article Text Mirror (Score:5, 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 into this guided tour, please remember that I have been involved with the GNOME community for the past few months as a helper in the GNOME Summaries, and I may not be able totally impartial towards GNOME. Feel free to consider me biased.
The Vital Statistics
Before going into the real stuff, let me give me a brief overview of my system, so that when I mention something as fast or as slow, you would be able to guess how it would crawl in your system.
* Processor: AMD Athlon XP 2600+
* RAM: 512 MB of PC 2700 DDR RAM (with 875 MB swap)
* Motherboard: Nforce 2 based mobo from Leadtek
* Storage: A 40 GB Seagate Barracuda HDD
* Distro: Mandrake 9.2
* Kernel: 2.6.2
The Installation
I had gone through (successfully) the GNOME dependency maze before, and to avoid losing my sanity, I decided to use jhbuild (one can also use GARNOME or cvsGNOME - maybe I'll test one of those with GNOME 2.8)
Using jhbuild is quite easy - just set some variables in ~/.jhbuildrc, and you are ready to roll. Jhbuild grabs the latest source code from CVS (taking care of the dependencies), compiles them, and installs them in whatever $prefix you want them to be in. OK - there was one major problem - but that was at a later stage, and it got fixed really quickly.
First Impressions
Fig 1. The default GNOME 2.6 desktop
Jhbuild took around 6 hours to get a bare bones GNOME system up and running, and surprisingly, there were very few errors, and I had to manually intervene only thrice.
I logged in as root the first time (yaya - I know security risk and other stuff..), to be greeted by a clean and polished looking GNOME desktop (Fig. 1) . (Note that I am running the Freedesktop.org Xserver here - so don't expect a stock GNOME 2.6 install to have panel shadows).
Seeing an icon named "Computer" right on the desktop - my first reaction was to click on it, expecting Nautilus to pop up with my "/" directory or something like that.
Nautilus goes spatial
However, as soon as I clicked on that icon - my reaction was "Yikes!! What have they done to Nautilus ??". Gone was the old and familiar explorer like interface. In it's place was a really minimalistic window, with no toolbar, just a plain menubar. I was quite confused - I even clicked on "Help" -> "About" to verify that the "thing" was indeed Nautilus. After some head scratching I remembered a post at FootNotes, in which the Nautilus developers announced something about going "Spatial". People had been pretty much excited about this - though I personally had no idea about what this stuff was all about. Now I thought I understood.
Fig 2. Spatial Nautilus - Showing "Computer"
All my disks had been correctly identified by Nautilus, and was showing up in the "Computer" window (Fig. 2). But that was not very important at that point - all my attention was riveted on the new UI. After some Googling and RTFM sessions, I figured out that Nautilus was following a "Object Oriented" metaphor, instead of the normally used "Navigational" metaphor. The most user visible aspect of the OO metaphor is that there is a always a direct, one-to-one relationship between folders and windows, and the window for each folder remembers where you placed it the last time - i.e, the next time it will pop up in the same position. This new interface is partially inspired by the interface described in http://arstechnica.com/paedia/f/finder/finder-1.ht
Spatial is a step backwards (Score:5, Insightful)
Mod this however you want, but the only thing I though of when using Gnome's new 'Spatial' file browser last week was navigating around Windows 3.1. Not only is this a bad idea, but the implementation was inconsistent on the desktop. The taskbar icon started the familiar navigational version of Nautilus, the Desktop icon launched the spatial version. What should have been done was improving Nautilus itself, not making a drastic change to the way it works.
This is a step backwards, and one that will slow down making any inroads into the corporate or personal desktop.
A paradigm a day, grows the complaints, right away (Score:1, Insightful)
And people wonder why the GUI hasn't changed appreciatly in the years since Xerox Parc. How can it, if every idea is greeted like the above? Jump over to OSNews and see the complaints about "Looking Glass". Any time success is defined by how much you emulate the old, then we will never progress.
Re:A paradigm a day, grows the complaints, right a (Score:3, Insightful)
Its was crap then, its crap now. Redoing other peoples mistakes, is just bad way of doing things.
Usability studies only take you so far, Real world testing proved it wrong.
Spatial is a step backwards (Score:4, Interesting)
As my grandpappy used to say - Don't kill the cow because the milk is bad.
Re:Spatial is a step backwards (Score:2)
No, kill it because steaks are good!
(why yes, I _did_ feel like burning some karma today, thank you :)
Re:Spatial is a step backwards (Score:2)
Re:Spatial is a step backwards (Score:1)
I agree that all versions up to and including the Gnome 2.4 version of nautilus have been slow but they have made some huge performance gains with the Gnome 2.6 Nautilus. I've tried out the Gnome 2.6 beta 1, beta 2 and rc1 via garnome and things seem much snappier and loading a directory with 100's of files doesn't take 5 secs anymore, it is near ins
Nope (Score:4, Informative)
Absolutely, 100% wrong.
Instead of completely tearing apart your idea that spatial is a "step backwards," I'll let a better-written article [arstechnica.com] say it for me.
Re:Nope (Score:2)
Nobody said it was new. But it is better. I deal with tech support at my real estate company company. Absolutely none of the agents here understand the concept of the "Up" button, or Back and Forward buttons, etc. when opening folders.
They don't understand that double-clicking the yellow folder opens a "browser" displaying that folder, they think they're opening the folder itself. It's how the human
Re:Nope (Score:2)
Never said such.
that your realtors don't get it only means that they need to invest some time grasping the file system metaphor (which is not difficult but does take some effort).
It takes effort to grasp a "file system metaphor" because it's silly and unnatural. The natural reaction to opening a folder is to expect that window itself to BE the folder. Nobody ever uses "Up" or "Back" or the address bar except more tech
Re:Spatial is a step backwards (Score:5, Insightful)
Your experience with Gnome isn't enough evidence to to judge against "spatial" interfaces as a whole. As you noticed, the implementation is inconsistent- suggesting that the problem is not with "Spatial" itself, but that particular program.
However, pro-"Spatial" posters who jumped at you with "100% wrong" are also incorrect. In a deeper way, "Spatial" is truely a step backwards: because spatial filebrowsing is non-scalable.
It only works for small problems, where the total complexity is bounded. Back when the Mac was young and "Spatial" was in it's prime, users operated on single floppies or 100 megabyte HDs. The solutions that worked then become unbearably messy when a 100 gigabyte HD may have a quarter-million files.
And then there's networking. Considering that it may be useful to treat the drives of other computers or the whole internet with the same file-browser that handles your local data, and the quantity is just overwhelming.
Non-spatial file-views are the only way we can expect to view local and remote files through the same lense.
To make an analogy of a library: If you only have 20 books, then a card-catalog system is a waste of time. Just leave them out visible on a table, and let vistors find them "spatially". But with 20k books, the catalog is an important improvement, even though users can no longer retrieve volumes from "where I left it last time".
Re:Spatial is a step backwards (Score:1)
more files and we have the extended navigational interface. with remote filesystems the user can be presented with a simpler navigational interface with special buttons that relate to the type of network environment the filesystem exists in.
the computer can do all that, and the user can benefit.
Never mind spatial, how awful would THIS be? (Score:2)
But from the context of your post, it is obvious that you really mean "there is nothing wrong with using different metaphors for the same task, depending on some arbitrary (and not really predictable, intuitive, or easily explicable) face-changing of the UI, chosen by the damned computer for the hapless user.
Ow, my head hurts just imagining how obstinate such a system would be to use.
When you see your idea explained the way it r
Staircases and Elevators (Score:2)
Libraries still lay books out spatially - the fiction section is on level 3, the math books are on the 5th floor, the literary criticism in onthe 2nd floor etc. That kind of makes sense, and helps people navigate in a rough sense to what they want.
I would claim, however, that the difference between spatial and navigational is similar to the difference between staircases and elevators. Imagine you're in a huge library.
Re:Spatial is a step backwards (Score:3, Insightful)
Mostly you just move inside your home dir. I have never used the old nautilus because it feels very "too much". With this new one I have some shortcuts on my desktop for my music and movies and now I at least use it sometimes.
It's also about 90% faster than previous versions and there is the option to "browse" the old way
Re:Spatial is a step backwards (Score:2, Flamebait)
But it's nice to have choice (Score:3, Insightful)
However, I'm not annoyed it went in. The GNOME desktop is kind of like a Mac desktop, only with you in complete control, and running on whatever hardware you choose. If Steve Jobs and the Apple desktop guys decide they don't like spatial, bam, it's gone, and tough luck to you if you liked it. With GNOME, you have more freedom than that.
Maybe some Mac folks who used and liked spatial from pre-OS X days will adopt GNOME now.
stev
Re:But it's nice to have choice (Score:2)
not that excellent. (Score:2, Informative)
Re:not that excellent. (Score:5, Insightful)
If you want a ligh one use fluxbox [sourceforge.net] or if you uber-cool-unix-hacker ratpoison [sourceforge.net]
But that's what people want (Score:5, Insightful)
Re:But that's what people want (Score:1)
Re:But that's what people want (Score:2)
Re:not that excellent. (Score:2, Insightful)
A) Productivity can be improved a little by making the workplace more comfortable/pleasant.
B) Many people in the workplace (i.e. if you want to capture the desktop market) don't want to put up with an ugly desktop. MacOS is pretty, even Windows is getting prettier (I can't exactly call that Luna theme 'pretty', but, well, they're working on it). To take Windows from a user a
I like to be able to READ (Score:3, Informative)
From my own experience, GNOME 2.x needs about 128MB of memory(256 if you want to run OOo too), and a 233mhz PII processor. That's hardly demanding these days, even in poorer countries. Those are the scraps we're throwing away here in the U.S. and elsewhere, afterall.
But that's not even considering that you can still use non-AA fonts with GTK2. Use the fonts that come with X, and don't se
Re:I like to be able to READ (Score:2)
But that's not even considering that you can still use non-AA fonts with GTK2. Use the fonts that come with X, and don't set GDK_USE_XFT. Enjoy some nice jaggy fonts :)
If you're gonna promote non-AA fonts, at least let's do it properly. Actually, yes, it can be a nice experience to only activate AA from a certain size upwards, say 10 or 12 pixels. And the way to do that is either through Gnome's own configuration, or by changing your FontConfig settings via ~/.fonts.conf. And using some quality TTF font [sourceforge.net]
Re:not that excellent. (Score:2)
Re:not that excellent. (Score:2)
I want to turn off full window dragging/ resizing.. I want only the simple outline. i also want to turn off EVERY other bit of eye candy... we tried and tried and finally switched all the xterminals over to windowMaker and cut the bandwidth to the x terminals by 90%.
both KDE and Gnome need to give users the ability to turn EVERYTHING off.
Menus and DDLs are nice - a bit like OSX (Score:5, Interesting)
Re:Menus and DDLs are nice - a bit like OSX (Score:1)
Those hordes you talk about are hardly going to download and compile GNOME CVS in the first place. They'll get it from their $distro of choice, which will have packaged things according to their target (supposably, at least).
Re:Menus and DDLs are nice - a bit like OSX (Score:1)
I hate being a spelling Nazi, but more than likely you also PRONOUNCE the word as "supposably" which actually means something similiar, but a bit different.
Re:Menus and DDLs are nice - a bit like OSX (Score:1)
I know... "supposably" is a word from a Friends episode. Joey thinks that the correct spelling is "supposably" and tries to convince himself and his friends.
Nevermind.
Re:Menus and DDLs are nice - a bit like OSX (Score:2)
Oh the other hand, I haven't seen that Friends episode (which isn't too amazing since I've only seen about 20-30 episodes total...) but I imagine it is probably funnier than many of the ones I HAVE seen...
Re:Menus and DDLs are nice - a bit like OSX (Score:5, Insightful)
"XP-using Teletubby-land loving hordes"
You must get modded a +5 Interesting...
I haven't laughed that hard in a while.
Now as another poster said. Very few are going to download this on the web and compile it. Most will wait for SuSe/RedHat/Mandrake et all to put it in their distibution. Notice that this guy said it took almost 6 hours to set up! Heck he even considered it good that it only had 3 errors he had to manually fix. No "teletubby" is going to be able to do that.
GNOME 2.6 view from a software engineer. (Score:3, Troll)
Such editorials are hard to take serious since they are build up on basicly NO deeper knowledge of the matter. Most people I met so far are full of prejudices and seek for excuses or explaination why they prefer the one over the other while in reality they have no slightest clue on what parameters they compare the things.
If people do like the gance ICONS over the functionality then it's quite ok but that's absolutely NO framework to do such comparisons.
I do come from the GNOME architecture and spent the last 5 years on it. I also spent a lot of time (nearly 1 year now if I sum everything up) on KDE 3.x architecture including the latest KDE 3.2 (please note I still do use GNOME and I am up to CVS 2.6 release myself).
Although calling myself a GNOME vetaran I am also not shy to criticise GNOME and I do this in the public as well. Ok I got told from a couple of people if I don't like GNOME that I simply should switch and so on. But these are usually people who have a tunnelview and do not want to see or understand the problems around GNOME.
Speaking as a developer with nearly 23years of programming skills on my back I can tell you that GNOME may look polished on the first view but on the second view it isn't.
Technically GNOME is quite a messy architecture with a lot of unfinished, half polished and half working stuff inside. Given here are examples like broken gnome-vfs, half implementations of things (GStreamer still half implemented into GNOME (if you can call it an implementation at all)) rapid changes of things that make it hard for developers to catch up and a never ending bughunting. While it is questionable if some stuff can simply be fixed with patches while it's more required to publicly talk about the Framework itself.
Sure GNOME will become better but the time developers spent fixing all the stuff is the time that speaks for KDE to really improve it with needed features. We here on GNOME are only walking in the circle but don't have a real progress in true usability (not that farce people talk to one person and then to the next). Real usability here is using the features provided by the architecture that is when I as scientists want to do UML stuff that I seriously find an application written for that framework that can do it. When I eye over to the KDE architecture then as strange it sounds I do find more of these needed tools than I can find on GNOME. This can be continued in many areas where I find more scientific Software to do my work and Software that works reliable and not crash or misbehave or behave unexpected.
Comparing Nautilus with Konqueror is pure nonsense, comparing GNOME with KDE is even bigger nonsense. If we get a team of developers on a Table and discuss all the crap we find between KDE and GNOME then I can tell from own experience that the answer is clearly that GNOME will fail horrible here.
We still have many issues on GNOME which are Framework related. We now got the new Fileselector but yet they still act differently in each app. Some still have the old Fileselector, some the new Fileselector, some appearance of new Fileselectors are differently than in other apps that use the new Fileselector code and so on. When people talk about polish and consistency, then I like to ask what kind of consistency and polish is this ? We still have a couple of different ways to open Window in GNOME.
- GTK-Application-Window,
- BonoboUI Window,
- GnomeUI Window,
Then a lot of stuff inside GNOME are hardcoded UI's, some are using *.glade files (not to mention that GLADE the interface builder is still not aware of the new Widgets in GTK and even not aware of the deprecated ones), then we have *.xml files for BonoboUI windows etc. As you can see it's a pain to maintain all this junk. These are just a little spot on the entire Mountain. I can countless bring up more stuff. Sure these things are being worked on. No doubt but as I said they WORK on it this means that there is NO real progress for the future since people write new apps for GNOME and probably use old API and then they need to change huge parts of their code only to adopt the new API rather than working on the application itself to bring it forward with better features the user needs.
Why do I say these things in public and still use GNOME. Well when I started, I was developing stuff using the Motif widgetset and during that time around 1999 KDE and GNOME were looking quite similar from features and stuff. So I decided to work on and for GNOME although I am not quite happy with many so called 'solutions' inside GNOME and I think that we need to discuss them (on whatever place it is) to make people who like to contribute to GNOME know where the problems are and how we can solve them (if possible).
From my person experience KDE is far far superior of the inferior GNOME when it comes to technical aspects. Even if there are a few Menu entries to much or the Toolbar is overblown in Konqueror these are all cosmetical things that can be changed if needed (and if the developers think it's a good thing) but looking at the amount of KDE users and applications that got stomped out of nothing I do believe that there are a lot of people simply happy how KDE is as it is now.
If they change the Fileselector in KDE then it's inherited by other applications. So the author doesn't need to change huge leaps of code since they simply inherit it. If someone changes the Addressbook object then it's being inherit in other applications, same for Clock, Bookmarks etc. The Fileselector looks similar in all apps, the Toolbars and Menu look similar in all apps etc. They have quite nifty features that I am missing in GNOME. Even nowadays I ask myself if the developers working on GNOME are still on track of what the user really wants or if they are not caught in a tunnelview here by doing something no-one can really use.
When I hear people talking about all these cool usability studies SUN made then I need to smile here since this thing is laying back a few years now. And SUN already started working on their GLASS Desktop based on JAVA (no it's not GNOME based). The reason why SUN still works on GNOME is as far as I was told is that they had a 5 years contract with GNOME to do so. Anyways you can't depend on old usability tests. To warranty true usability these tests needs to be re-done every now and then so you can guarantee some sort of quality assurance that the stuff is still on track and truly usable for people.
Usable not as in which button to press, usable as in 'can I find the apps I need to do my business work'. or 'can I copy files and subdirs from FTP and have the stuff arrive correctly on my Desktop' (gnome-vfs still horrbly fails here).
Well I think people should really do an article based on these things since they are elementary for a Desktop. Neverthless I do believe that both sides KDE and GNOME do work hard on their Desktop but truly I believe that KDE makes better steps forward and imo in the right direction too. Even alternative stuff such as MorphOS or XFCE are far more useroriented and friendlier to use than what GNOME offers today.
> Perhaps GNOME is a bloody mess inside and KDE is a
> masterpiece, but does that really matter to the user?
Yes it does matter. We today place the stones for the road tomorrow. And we should decide wisely which stones we lay on that road. Should be go for an inferior Desktop which stagnates because developers are messing around in the Framework or should we go for a technical supperior Desktop ? Yes USERS do care a lot and it matters a lot of them as well. Since these users want to use polished applications, applications that are tightly integrated, that share one database for their Addressbooks, one database for their Bookmarks, they simply want to put all their Addresses in one database and be sure they can use these things in their Word like application (serial letters) in their Cellphone syncing app, in their Palm or PowerPC syncing app, in their Email client and so on. It matters a lot for the user if he can reliable use a FTP client or Filemanager to copy a bunch of files from A to B without worrying whether the stuff appeared correctly or not. And yes it matters a lot for the user whether he can be sure that new applications can rapidely be developed (even by himself) in a short time due to taking objects. And yes it also matters for us all whether a nice Desktop is being used which works reliable in all areas and guarantees new applications since we wanted to demonstrate outside world (non Linux people) how far Linux and the Desktop really are. How can we demonstrate the world outside that KDE is in many areas even far supperior over WindowsXP (in Desktop functionality) if we show people how nice icons GNOME has and as soon they start using it figure out that it's a mess ?
And yes, there is nothing wrong for KDE being similar to Windows. I want Windows for Linux. At least it offers me a cool Desktop with similar functionality and cool stuff. Hell I don't even come from Windows I used to be an AmigaOS person before that.
Better a Windows look and behave like rather than a Desktop that fit's nowhere where people and industry needs to spend hours and probably millions of Dollars into teaching their people how to do simpliest things. Now tell your customers who pay for your service how to use gconftool-2 for example. They will chop your testi**es off and put them in a glass with alcoholics.
> the difference is that Gconfig it is aimed for advanced
> users and Kpanel for general use.
And here is the problem. GNOME these days aims for the unexperienced users. Quite a contradictorily to the aims of GNOME don't you think. Most important settings are simply hidden behind GConf (and not Gconfig better you get off and learn some basics before teaching knowledged people what the differences are).
> I don't want I windows on Linux, the reason I use Linux is
> to get off MS, and what about Mac users who don't like
> Windows and want something else?.
Honestly, KDE is closer to both of them than GNOME. KDE offers the MacOSX way of Menu system (Top Menu), KDE has a cool Liquid Theme, KDE can look quite close to anything you like. It can even look like MorphOS.
But back to a normal conversation. You should look back in the mid 80's and compare the things today. Most Desktop solutions are all the same.
- Window
- Window can be moved,
- Icon on Desktop,
- Icon on Desktop can be moved,
- Filemanager,
- Filemanager can do things,
- Panel, Toolbar, Top Menu
So saying that Mac Users won't like KDE is plain stupid, the same stupid way saying Windows users don't like KDE etc. There can also be people who do like GNOME, there is no problem. But we should clearly look for the superior Desktop solution and it should be even clear to you that KDE is technically FAR superior. It's so much superior that comparing KDE and GNOME is plain wrong. It's like comparing a Ferrari with an Austin Mini.
> I do feel that Gnome is more likely to be successful on
> the corporate workstation than KDE
I don't believe so. Even corporate people have eyes in their head and a brain they can use. When they spent some time into Linux and know more about the technical stuff and probably the two desktops they then will decide wisely. I recently had a conversation with someone who wanted to change his entire company (1200 Desktops) to GNOME but then they decided to use KDE after they figured out how messy GNOME really is.
> because there are less option to fiddle around with and it
> seems simplier to get things done
What things do you think they get done that simple ? I would know a couple of examples of the things you can do simplier on GNOME than e.g. KDE ? But ok be it like that, this still doesn't change the broken Framework issue which is basicly the all and everything for a Desktop. No matter how less options you have, no matter how clean you assume the desktop to be, no matter how polished or nice you find it yourself. It still won't change the broken junk inside it. As many people already explained (since they elaborated correctly) GNOME will take years (IF EVER) to reach quality of KDE.
Forget the ugly icons, forget the bazillion of Menu entries and forget all the tons of Options. These are all things you can change easily and quickly. Unfortunately you can't easily change the broken stuff in GNOME that quickly. I wish it would be possible but as sad and realistic it sounds, it won't happen.
> sure stock Gnome isn't as polished as KDE, but Ximian
> Gnome is. Gnome 2.6 looks like it might just Gnome that
> extra bit of polish that it needs as well.
Yeah but thre rest remains GNOME, the same incomplete and unfinished Framework. Ximian GNOME may be a name in the public, but new apps need to be developed as well and that's still the same problematic issue than using stock GNOME. You still deal with the problems I have described above.
We need a stable desktop, a desktop with good framework, nice applications and where we can be sure that rapid application development is possible. A Ximian GNOME won't change anything here.
> Computer users usually don't know much about computers, I
> can't imagine a customer trying to find and specific option
> here.
Excuse me, but why do these people want to use Linux then ? If they have no clue what they are doing they better head off using Windows. Every farmer can give help with Windows, every neighbour can and even every WalMart store can help these people in Windows related questions. Why do they want to bother with Linux then ?
New people unfamilar to computers make their first touch with Windows. They learn to use it, they using it fine and they strangely get their stuff done the way they like and Windows is overblown with configuration options.
Even my sister is far better in Microsoft Word than I ever was or ever will be (not to mention that I am not interested either). But you see that people as unexperienced they are are usually willing to learn and do it. They learn by mistakes and don't make them again the next time.
Every now and then my sister comes up to me and tells me that her printer doesn't work. Hell it's even easier for me as Administrator and even as long years of Linux user to fix her 1 second problem with the printer on Windows rather than on Linux. Windows is dead simple but yet full of configuration stuff. People not interested in config stuff won't fiddle with the things either.
Even cars, videorecorders, cellphones, pda's, dvd burners, mp3 players are getting more features and things. And when I see people talking about technical stuff they usually go for the things with many options because they think it's correct with their price.
Anyways you should clearly read my comments. All the options, icons and much menu entries you can IGNORE since these are things you can easily CHANGE. Changing all the stuff in KDE is far easier than fixing the broken Framework in GNOME.
> Yes people are willing to learn, but they are more worried
> aboyt getting their work done as fast as posible, less
> clicks, less options, just do what they need.
Ok and what WORK do these people get done with GNOME they can not get done with KDE ?
For my knowledge they can get the same work done with KDE as they would get done with GNOME. So far we hopefully agree.
Now let's get a look beyond the tunnel (having a tunnelview is kinda pointless here).
Say that person wants to get REAL work done. Say he or she want's to do some astrological stuff. Where will he get the software to get the work done ? GNOME doesn't offer such a software so he or she can't even start to work.
Say people come in #gnome every day complaining there is no CD burning application like K3b now how can they get their work done if the application is missing ?
Say people want to do presentation stuff like PowerPoint, where is the application on GNOME so these people can get the work done ?.
Say people want to do 3D stuff for their mechanical course, where do they get the application for GNOME ?
Say people want to do UML for their university course, where do they get that program for GNOME ? DIA ? Hell I am a practical example here that DIA is unusable to do a shite.
Now where is the software on GNOME to get exactly that work done ?. Looking over to KDE the software is existing already.
Ok I am not blaming GNOME for not having all this. NO. But I wanted to make you understand that a good Framework is required to guarantee rapid application development. Rapid application development means that the users do not need to wait 2 years until they get the work done, since they already have the software today to get the work done. And this software is in a way to be improved. They have no problems changing huge parts of their Code to fit the fixed Framework since the Framework on KDE is already in a very good condition. The developers concentrate on the fun stuff improving and echancing their applications rather than fixing stuff or get their app understanding the new changed API.
You know, a good Framework means that you can quickly develop programs. Programs that people can use to get serious work done.
I always wished GNOME would have such a great development Framework like KDE has but it sadly hasn't and this is what I like people to understand. There is no point blaming one desktop and favoriting another one just for the Icons of for the Themes (as this editorial shows) it matters more that we have a good framework for the future and guarantee that apps are being written in masses.
This is all I wanted to say, nothing more, nothing less. If you are not willing to understand this (or not able to understand either due to limited knowledge) then this is your problem not mine. I took quite a lot of time to explain these things to you. By now everyone else reading this should have understood the points.
Let me give you a view examples of what I think of being a broken framework:
a) When I implment new features but do it just half. Adding GStreamer to GNOME for example which is indeed a nice thing but adding it only to half of the apps and skipping the others is a bug.
b) Fixing half of the stuff in apps. Say you committ a patch that fixes 2 dialogs in Nautilus but leaves the others as they were 2 years before is imo a bug. Makes using the app become, well ugly.
c) Offering multiple ways to open a Window in GNOME is a bug. GTK+, GnomeUI, BonoboUI. This leads to inconsistency and total clutter.
d) Writing a new Fileselector but have the default apps use a mixture of old and New Fileselectors is imo a bug. By the way why should a developer waste time fixing all old and new Filedialogs ? If the stuff is properly written then you simply inherit the new Fileselector without noticing it. It's simply there. Here is a proof that not everything in GNOME 2.0 is re-written. Much of the stuff is simply ported from 1.x.
e) When copying files via Nautilus (say ftp.gnome.org) and you copy a subdir which includes MORE directories and files from that FTP to your Desktop and you get stuff like
(copying file 98 of 23)
Or get 0byte files copied from that FTP to your Desktop then this is a bug.
f) Gnomifying OpenOffice is an even bigger bug. The entire OpenOffice framework is based on the Staroffice Foundation Class (Their own Widgetset). Gnomifying all this is simply an idiotic task and leads to fragmentation in the code. Again they will do this work only hal. Only what you see will be changed not the rest. So the result is a mixture of old code and new changed User Experience.
g) Hardcoded UI is a bug (at least under GNOME), it leads no space for UI designers to fix all the stuff without code skills. Where should they start ? In the Hardcoded stuff ? In the *.glade stuff ? In the
h) Having all apps do their own bookmarks system is a bug, There is no central bookmarks solution. Same for Addressbooks etc.
i) When I call out for a bounty and have people called up to 'tweak and fiddle' Evolution support into the Panel Callendar then this is a bug and not a feature. A feature would be if I changed the Callendar Object so when I inherit it into other applications that all these apps will benefit from the Evolution support and not just one.
----
And yes what you write is indeed also a big problem (at least your text is partially right). A lot of undocumented API changes. A lot of undocumented changes itself.
E.g. I wrote a little Application which uses a GtkCombo I was in the assumption to use a good API from GTK and then one day they changed the Widget and marked this one DEPRECATED and this in a new App that I wrote.
The changes are quite huge and I feel quite frustrated having this one changed to adopt the new Widgets. It's not just trivial changes these changes I have to do are quite huge and will take me a couple of days. The days I usually have to stay motivated to do the work. Now instead of improving my application I need to fiddle around to remove the old stuff, go through 10 source files and remove the stuff. Not to mention that I also need to re-write huge chunks of code only to fix the stuff.
While the old GtkCombo allowed me to simply attach a GList to it (my 'History' function is based on a GList which contains 5 Listentries which have Data applied) I now need to create an entire TreeModell again and populate that Tree with these values.
What I do here is changing a well thought interface (which I spent hours to figure out before) into a new interface and what I do is tweak and fiddle the stuff in a way to make it fit there. Which then leaves other parts of my code get slightly unoptimal as I used to have in mind before.
Why so frustrated and why attacking my person ? Do you fear that I could be right and you not ? Your reply is far to ridiculous and only a try to publicly destroy my creditibility rather than a sign of willing to accept the critics as I write them (since they are right) and start discussion with the community and have these problems solved. People like you are more up to attack those who bring up constructive criticism and feedback rather than true willing to change the true things.
> What are you actually trying to say. Does every
> application need to add GStreamer? Why don't you specify
> precisely what features are not implemented and state
> where GNOME has stated officially or unofficially not to
> implement it.
Not every application needs to embedd GStreamer that's pure rubbish. But the audio stuff should and should do that correctly. Right now in GNOME we deal with direct Xine calls and GStreamer calls. Developer have been chosing Xine in many tools (Totem and Rhythmbox) due to stability reasons because GStreamer still is unfinished, no stable API and no general stability. They do still offer the posibility to include the GStreamer stuff but what benefits does it give when it locks up during playback or simply doesn't play back at all. Go and get a look in the code yourself id you don't trust my words. Let's continue with the new GMixer, it was hyped that it now supports the GStreamer stuff but yet it doesn't. When I select 'alsasink' in GConf-Editor then I would like to be able to Mix the alsa stuff and not get a dialog that the sound devices an not be found. The reason why it can not be found is it still expects the OSS emulation in Alsa to be active so it just mixes the OSS part of alsa but not the native part. I thought it uses GStreamer here, so I do assume it to use the right sinks and right devices to Mix. Just one example.
> Still short on specifics. If you are such a great software
> developer and you claim to have been working for GNOME but
> yet you have not been able to solve even one of the
> problems you whine about years on end.
The problem here is you can't simply sent in bugfixes or patches when your innerst tells you that this is plain wrong and needs to be re-done correctly. See it like a house where you continue glueing stuff into it. A bit here, a bit there a bit in another place and you see how the stuff you are doing makes no sense but yet you continue because you can't convince the other owners that it would be better to trash the entire house and start from scratch.
> Where are all the bug reports you have filed? Where are
> all the patches you are submitted that the GNOME 'people'
> have refused to commit. Please give us more facts, and
> soon.
They are either on bugzilla.gnome.org or made their way in the Applications in case they got accepted. I know you are trying to pick here but you won't be successful. For further information you can look into ChangeLogs. But this isn't your point at all, you will reply and tell me that you wasn't able to find a shit (many others have tried this before). I think you should get out of your tunnelview and your evangelism here and start looking into the real problems. Guess why there aren't any changes in GNOME because people and developers fear to do these changes or raise constructive criticism because it ends in things like this. Ignorance, Elitism, Tunnelview and even worse Namecalling.
> How about you give an example of the clutter that this
> causes. Are you complaining that GTK+ has only one way to
> open a window, or that GnomeUI has only one way to open a
> window or that GTK, GnomeUI and BonoboUI altogether have
> three ways to open a window?
The problem here is interoperability with the rest of GNOME. Try opening a couple of applications on your GNOME desktop. Say one program written using GnomeUI, one written in GTK+ one written in BonoboUI. Now go to:
Desktop-Preferences -> Menus&Toolbars
And fiddle around with the values there. You will see that some programs imidiately change the Toolbar and Menu behaviour, some not, some change their appearance after they got opened and closed and some even do not react on these settings at all. Just one example only to satisfy your questions here.
Technically they are a pain to maintain too. Specially for UI people, those who go from app to app fixing all the paddings, Layout of buttons and widgets etc. There is a big difference if you use one GUI designer or one system to change all this or need to learn 3-4 different but common used ways to change all this.
It is problematic having hardcoded UI in the code (which requires that an UI expert needs to learn to programm to solve these things) or if you use GLADE (which can create *.glade files or simply embeddable code) or if you use BonoboUI with it's *.xml files. They are all totally differently, different attributes, different behaviour etc. And yet I do see people using all these things in their own apps over and over again. Sure core developers may use the correct way for their upcoming products but not the new developers who start working on their apps. They use GLADE to build the interface but forget or don't know that GLADE isn't aware of all the new DEPRECATED widgets or new widgets that have been introduced lately. Go and look yourself.
> just tells me that you don't know or understand sh*t about
> things in GNOME as you claim all the time. It also brings
> doubt your claimed knowledge about software development
> because I don't need to remind you of what happens during
> API changes such as the one going on in the FileSelector.
No I was more demonstrating how good the KDE framework for these kind of things are. They change the Object Fileselector one time (regardless what changes they do) and it's automatically inherit into other apps. While in GNOME they now offer 2 Fileselectors the old and the new one. Different API is a problem here but this is a sign that the stuff is simply an artifact from GTK 1 and GNOME 1 times. If it was a total rewrite as you want to make me believe then this would have been introduced far earlier.
What I also speak about is the consistent look of these Fileselectors. The new Fileselector now offers this stupid 'expander' widget where you first get a locationbar (at least some apps show this) and then need to press the expander to get the rest of the files shown. To much magic and to much 'usability experts' have made a huge mess once again for a simply shitty fileselector. Jesus we use Fileselectors of 20 years and longer they do what the name says showing files and directories where we can simply dive in and do the task. No magic techno stuff that yet requires 3 mouseclicks to actually do what I want.
> This one and all the rest of your 'examples' are just too
> funny. You have just gone to 'bugzilla' and copied things
> over.
No I didn't copied them but it's ok for me that you confirm these problems to exist. Now we have GNOME 2.6 in a couple of days and these problems are still there since GNOME 2.0 or even earlier who actually knows. You seriously want to go enterprise with these problems ? And when will they get fixed ? Is it even possible to fix these issues ?
> Unless you can show an official or unofficial policy
> from GNOME not to fix these issues, they are moot. Just
> because they are not fixed when you want does not make the
> framework broken.
As long these things are not fixed and even unknown whether they can be fixed at all - yes I do have the tendency to say that these things are broken. People who write a FTP client for GNOME use an alternative library to do these things since they can not reliably use the ones offered in the GNOME framework due to these errors. People writing a Webbrowser for example can't use the HTTP backend of gnome-vfs due it not to work reliable not doing redirections for URL's etc. Sure there are always bugs in such projects. I am the last person admitting that there aren't bugs. Every bigger project has a lot of them and this is natural and just the way it is.
But here are the fundamental problems I do see in GNOME. They spent to much time rewriting stuff over and over again and want to do everything the right way (excuse me, there isn't something as the right way, there is just one way and another way but the right way doesn't exist). You need to finish a project and then head over to the other one and make sure that with increasing version of GNOME that the stuff you offer to the people is less painful and usable.
Nautilus used to show signals of becoming a well not as crappy Filemanager as it used to be and now it has been changed into a Spatial Filemanager. This is a drastical change for the Users. While they have done such drastical changes in the behavior of Nautilus they forget to fix the other things due to lack of resources. Imo it would have been better fixing gnome-vfs and all the other tiny bits and bytes rather than re-writing stuff that has been written before and has shown signal that they work. This is going over and over in GNOME and still no sign or signal where we as users can see (look here the evolution of the software is finished, we can have it stay that way and lets continue working on other bits). No they are busy throwing over concepts and re-write them over and over again. And all the developers outside who work on their own software need to play catchup to have their app following the new changes. Instead doing the funstuff to continue improving their app they stick into all these messy changes.
And hey, this is just my very own opinion. That's why I do fullheartly welcome the Quality and Assurance team in KDE. They will clearly signal the developers 'hey what are you doing now ?'.
> I'm sure I'm not the only one tired of seeing all these
> verbose spillage of fud from you every time a GNOME
> article shows up.
Whatever you think. There are people outside who agree with me there are people outside who agree with you. That's life but I do see a reason here to make people understand these things before writing editorials like these. A good solid framework and nice applications are important.
If people come over and over again with their counted Applications they like to use and others come over with the same old junk over and over. The same way I come over with the same stuff to make people understand the problems here.
GNOME has copied a lot of stuff from MacOSX and Windows in the past months and years. Sadly the wrong bits were copied.
A last thing to add from my side that people do not think about. KDE already offers all these things already. Two years ago when I used KDE 3.x I already noticed a lot of stuff in KDE that were missing and still are missing in GNOME.
I do know that one day someone will fix the broken gnome-vfs. But when ? As long as these things are not working properly people use other libraries to solve the solutions they need to solve. GNOME may (or may not) get all these things one day. Say in 2 years by now. But KDE had exactly all these things 2 years ago already. There is a development difference of 4 years between both Desktop solutions. While GNOME is catching up to what KDE offered 2 years ago KDE continues to quickly expand in all areas and the applications it offers are growing as well and new applications can easily be developed in a short timeframe.
These things you should take into account to when doing such editorials. Not just looking at fancy icons and compare two screenshots. I would say the same things about GNOME if GNOME were in the position to be much enchanced over KDE. Although even KDE is lacking a bunch of things that I would see more improved.
- Split out applications in own Modules like in GNOME rather than having all put into kdelibs, kdebase, kdeutils etc.
- More clean layout of includes in the includes directory like GNOME does (by default and not per distro excuse during install).
- Make sure the
I here again do like the way GNOME does it. As you see neither of both are perfect.
Re:GNOME 2.6 view from a software engineer. (Score:4, Insightful)
Nice to see you using the "worked on GNOME for 5 years and got ticked off" line, it makes it much easier to put together posts you've made on "osnews.com". Haven't seen you posting much there lately, but I assume that's only because you've been banned there.
How long did you have this rant stored on your copy of notepad... er, I mean, whatever text editor comes with MorphOS? Why did you post as an AC? I've got nothing personal against you, but man.... I've got to call a cheese a cheese.
Greatly exaggerated (Score:2, Informative)
The Gnome API on the other side has been stable since 2.0 (the change from gtk1.2 to gtk2.0).
I admint, though, tat gui programming in C is non-trivial, but there exist multiple bindings for Gtk/Gnome. Ruby, Perl, Python, PHP, Java and C#. Pick your favourite language.
I don't think that the (as you called) gnome-ific
Re:GNOME 2.6 view from a software engineer. (Score:5, Funny)
Re:GNOME 2.6 view from a software engineer. (Score:1)
Re:GNOME 2.6 view from a software engineer. (Score:5, Insightful)
As far as I'm concerned, Konqueror is KDE's killer app. It's the one thing I can't give up, the thing I miss most when I have to use a Windows or Mac OS machine.
I can't imagine anyone disliking it!
Kant we all just get along? (Score:1)
Re:GNOME 2.6 view from a software engineer. (Score:2)
There were one or two sites (i.e. ESPN) that didn't render properly in KDE 3.1, but in KDE 3.2, I have not come across a single site that doesn't render correctly in Konqueror, and I use it every day for Web browsing (among a hundred other things). In fact, both flash and java load faster when used with Konqueror than the
A repost... any new articles? (Score:5, Insightful)
Re:A repost... any new articles? (Score:1)
Forget being packaged up, Gnome 2.6 still (to my knowledge) hasn't been released yet. The gnome.org site still doesn't mention anything about 2.6 (beyond the 2.5 roadmap), just the delay from the intrusion. The desktop releases directory stops at 2.5 as well.
At least once the Gnome team finishes whatever integrity checks they've got going, we'll start hearing from the Gentoo zealots.
full mirror (Score:3, Informative)
Re:full mirror (Score:1)
GNOME catching up to Windows... (Score:5, Interesting)
Like when your connection goes down? Wouldn't you like to know when that happens? I rather would. And, not to troll, but Windows has had that since NT 4.
What is with some developers and their attitude towards little Windows-like widgets? Some of those things are actually useful. And if you ever want GNOME to approach the functionality of, say, Windows XP (and I do say functionality; the XP interface simply does a hell of a lot more) you need to focus on both "polish and more polish" and the inclusion of useful little applets.
Re:GNOME catching up to Windows... (Score:2, Interesting)
These balloon tips will be removed in longhorn I believe. So we won't have to deal with them for too many more years. Registry tweaks can also disable specific balloons (eg low disk space on drive d) as well.
Overall, I like the balloon tips but I think longhorn's sidebar will really step things up another notch.
Look beyond the suburbs of GNOME and KDE (Score:3, Interesting)
GNOME and KDE are not the only desktops for Linux, despite what many seem to think. WindowMaker (with cousins like fluxbox) are much older and support tiny programs called dockapps [dockapps.org] that do anything you could want them to. The variety, configurability and stability of this tiny applets beats Windows,
Re:Look beyond the suburbs of GNOME and KDE (Score:2)
You say this dispite the fact that many, many people always complain about "hundreds of desktop environments and window managers"?
No Easy Answers & You Can't Get Rich Quick (Score:2)
It is no less daunting than memorizing all the trivia surrounding baseball or football (or any professional sport, for that matter). 'Joe User' can follow such spor
Re:No Easy Answers & You Can't Get Rich Quick (Score:2)
I don't understand why all the critics on Slashdot can't see that.
Re:GNOME catching up to Windows... (Score:1)
Re:GNOME catching up to Windows... (Score:2)
I hate using Windows, because these balloons keep popping up and there's no obvious way to get rid of them. Sometimes they have a close button, sometimes they don't. Sometimes clicking on them closes them, sometimes it runs a program. Sometimes they have a relatively short timeout, sometimes it lasts for ages. They're totally unpredictable for someone who uses Windows as rarely as
Re:GNOME catching up to Windows... (Score:2, Insightful)
Slashdot, have you no pity? (Score:5, Funny)
Why must you tease me with your promise of screenshots? Gets me every time...
I'm always fooled into this false sense of security based on the fact that no one really rtfa's, and click on the link, only to find the slashdotting effect has forced me to go work instead of look at pretty pictures.
Save Dialogue (Score:3, Interesting)
Does that "save" dialogue make sense to anyone?
I'd have thought that saving would be the easiest thing in the workd and yet it's not obvious where the file is being saved at.
Re:Save Dialogue (Score:1, Interesting)
The new "spacial" nautilus hides file pathes from the user (which might be a good thing or not) and that's hailed as a useability improvement (see the spacial link in the article). On the other hand the new file dialog seems to be centered around a new file path widget. Does somebody understand that?
a step in the right direction (Score:4, Informative)
the new file selector for one is very nice, although it still has a few rough edges.
personally i'm not too fond of the new 'spatial' nautilus even though i've been a mac user for many years. i miss (or missed) a shortcut to close all open windows for example. nautilus *is* blazingly fast though. also, browsing samba networks works very nicely.
i'm very curious as to the final release. with it's shortcomings gnome remains my most used desktop environment.
great going guys, keep up the good work.
Spatial Not worth it (Score:4, Interesting)
Its a mistake, Every one used Directory Opus to deal with files on the Amiga for a very good reason. Spatial handling is messy, and a pain in the arse.
There not just redoing things, there now repeating other peoples mistakes. ArsTechnica is quite good normally but spatial file handling was never any good.
Re:Spatial Not worth it (Score:2)
Re:Spatial Not worth it (Score:1)
We've invented things to stop that from happening in other applications ( Tabbed browsing, virtual desktops ), why bring it back for file browsing?
Re:Spatial Not worth it (Score:4, Informative)
Re:Spatial Not worth it (Score:1)
Why bring all the extra overhead of opening and closing windows? Why change it at all in fact.
I think its a mistake, Spatial is obvious, infact so obvious is was the very
Re:Spatial Not worth it (Score:2)
Re:Spatial Not worth it (Score:3, Interesting)
Re:Spatial Not worth it (Score:1, Informative)
Press CTRL+L in the file chooser.
Re:Spatial Not worth it (Score:1)
As for that fileselector - I still haven't figured out how I'm supposed to be able to type the full path name in so I can open the directory or file I want. That is a MAJOR obstruction.
After you have the fileselector open its Ctrl-l (That's an L) and that'll let you open a location and that has tab completing.
Re:Spatial Not worth it (Score:1)
Why "My Computer" I though KDE was the one being accused of being a Windows Look-a-like.
Re:Spatial Not worth it (Score:2)
There's a section marked "The big gnome 2.6 mask" if you delete that you can emerge gnome-2.6_rc4 and that'll get you most of the 2.6 goodies.
When you redo an emerge sync it'll mask it again, and you'll have to edit the file. There's a way around that but this way is the quick and easy way to get going.
Re:Spatial Not worth it (Score:1)
Is Nautilus still a buggy bloated POS? (Score:3, Interesting)
The only problem is that I am really used to Gnome's look-n-feel, but I guess since I am using Fedora, that won't be as much of an issue due to the whole Bluecurve thing.
Re:Is Nautilus still a buggy bloated POS? (Score:3, Informative)
Well, coming from Fedora Core 2 test 2, I can tell you this about Nautilus:
1) It's not slow anymore - Nautilus 2.6 is damn fast (finally!
2) I haven't really come across any bugs yet - not that they aren't there, but there are no big ones that I can see
3) This is the best Nautilus yet for features, too, though some people insist on a file manager they can tweak the hell out of. If that's what you want, stop using Nautilus immediately, because it will never be what y
Re:Is Nautilus still a buggy bloated POS? (Score:2)
The Nautilus in Fedora Core 1 was orders of magnitude faster than the one shipped with Redhat 9... however, it was still slow compared to Microsoft's Windows Explorer. It w
Re:Is Nautilus still a buggy bloated POS? (Score:2)
Re:Is Nautilus still a buggy bloated POS? (Score:2)
As for me: I'll stay with GNOME and Nautilus. I don't find it useless, it does everything I need in a minimalistic interface.
The new Nautilus is *sooo* fast that it isn't even funny anymore. It's even faster than Windows Explorer.
Re:Is Nautilus still a buggy bloated POS? (Score:2)
Just as you can get locked in to the Windows interface, you can get locked in to FOSS desktops. I plan on switching with Fedora Core 2, and once I am used to KDE there... I will probably switch to KDE on Debian Sarge once it goes stable. This is a case where Redhat's Bluecurve project pays off, as it will lessen th
Re:Is Nautilus still a buggy bloated POS? (Score:2)
Really? I can use KDE flawlessly. Back when I began using Linux (before all the Bluecurve stuff), I had absolutely no problems using GNOME or KDE. Buttons still look like buttons and menus still look like menus. You still have a window list and a "start" menu.
"The versions of Gnome shipped with Redhat 9 and Fedora Core 1 are extremely buggy... mainly due to Nautilus."
No problems here. Nautilus has never crashed on me ever
Re:Is Nautilus still a buggy bloated POS? (Score:2)
Re:Is Nautilus still a buggy bloated POS? (Score:2)
Ugh. (Score:5, Interesting)
Look. Unlike Windows, this stuff is going to be going on to multi-user systems. There will be tens, hundreds of instances of each of the applications running on a particular machine... Over the network... Performance for X based applications is *absolutely crucial* in the corporate environment. That *is* where Gnome is going, isn't it?
Gnome 2.0 (Solaris packages) performs poorly in comparison to other X based UIs like CDE and Openstep. Both in local and network performance. So, does 2.6 suck or is it acceptable, is it even better?
Re:Ugh. (Score:3, Insightful)
Being just as bloated and slow as Windows XP helps nobody. It's hard to get people to convert, it's a problem for third world countries, and it just gets people on the upgrade treadmill we used to mock Wintel ab
Re:Ugh. (Score:1)
Third world is not where the money is, why should RedHat care at all. Gnome hackers are going to have at least half decent computers why should they care too much? I mean come on, No matter what the spec your going to have at least a $100 monitor, and a decent base unit is only gonna cost you $250 to $300. Yeh whine all you want about not being able to run 100 GNOME processes but your a hippie to care. I mean shit GNOME specs are pretty damn low as then are (700Mhz +
No, the boxes I use are dual 3GHz machines (Score:2)
They cost around 10k. Now. How many users will it support? 50? 100? 200? If you double the requirements you half the number of users and double the amount of money the corporation has to spend on new machines.
More important than that is the LAN performance. Have you got any idea how much it costs to put in gigabit switches and flood wire a building with cat5 or cat 6 cabling?
Why? Why? Why would you do this? Why not just put a machine on every de
Re:Ugh. (Score:2)
On the other hand, I use KDE apps in the same manner and the performance is great. There's a little bit of lag compared to apps running locally, but nothing that makes it unbearable to use.
Does anybody have any idea of why Qt performs so much better than Gtk+ in this regard?
I'm impressed (Score:2, Insightful)
People complaining about applications/desktop environments beeing bloated should get a n
Have they fixed the panel in 2.6? (Score:3, Interesting)
It seems like every other time I login all my icons, launchers, and applets have been magically rearranged on the panel. Man that pisses me off to no end.
The worst problem is when your system locks up or otherwise crashes and you're using ReiserFS. Oh man, I feel so lucky when my entire desktop and all the panels don't get trashed. I can't count how many times I've lost my entire GNOME setup due to my system locking up. Something about the GNOME preferences system, it must hold lots of files open all the time or something. This is one problem I can not tolerate and for a while I switched to KDE solely because of this insanely stupid behaviour.
Re:Have they fixed the panel in 2.6? (Score:2)
No, it doesn't stop them from moving around by themselves. Something is broken in the configuration/preferences system (it's been like this as long as I can remember using GNOME).
Re:Have they fixed the panel in 2.6? (Score:2)
Proposal for Spatial (Score:2)
The general idea is to modify the windows-list applet so that when it's on a vertical taskbar, it shows a GtkTreeView of the windows spawned for that desktop. Since subdirectory windows are now children of
Re:Proposal for Spatial (Score:2)
Use middle click to open the directory and close the parent, use the backspace key or the selector at the bottom of the window to open the parent again.
> Metacity not popping up windows in the most logical places,
In spatial nautilus they should pop up at the same position that they were at the last time you used it.
Re:Novell has chosen to standardize on Qt! (Score:2)
Re:In case developers didn't get the clue: (Score:4, Funny)
Re:In case developers didn't get the clue: (Score:1)
heh heh... A vicious but fun read. I'm not quite to that extreme yet, but I did manage to achieve a -1 flamebait all the same. ;-)
I didn't quite get the humor of clicking on a "dildo" mentioned by your parent's post. And did an AC up there actually comment that it was a "clean foot, with a clean smell"? Hoo-boy... Maxi-Oxymoron! Talk about steppin on some sensitive toes!
Well, my smoldering karma probably doesn't smell too great right now either, so I'
Re:wouldn't call it that new (Score:1)
Re:Good But Some Strange and Bizarre Decisions (Score:2)
CD burning in the file manager is exactly where it needs to be. If you want to transfer files from a floppy or a network volume, you use the file manager. If I want to transfer files to a CD, I would logically use the file manager. A CD is a storage medium like any other, be it a hard drive or floppy. Makes sense to me.
I also disagree with the Mac interface comment. By extension, if people want thier interface looking like Wind
Re:Good But Some Strange and Bizarre Decisions (Score:2)
You, sir, sound like someone trying to sound smart but are failing miserably. I've already