Linked by Eugenia Loli on Tue 4th Oct 2005 22:09 UTC, submitted by Manuma
Thread beginning with comment 40278
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/19/13 23:15 UTC
Linked by Thom Holwerda on 05/19/13 23:11 UTC, submitted by Drumhellar
Linked by Thom Holwerda on 05/18/13 21:06 UTC
Linked by Thom Holwerda on 05/18/13 7:37 UTC
Linked by fran on 05/18/13 1:38 UTC
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Linked by MOS6510 on 05/17/13 22:22 UTC
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Linked by Thom Holwerda on 05/16/13 17:04 UTC
More News »
Sponsored Links



Member since:
I _greatly_ appreciate the offscreen stuff, because it happens to perfectly suit the needs of a project I will have to tackle. The specific application (with a MacApp legacy) relies on printing partially reformatted dialog contents for documentation of its use, and this looked _hard_ and like a big roadblock until now. With the new features it should be either direct-to-print via cairo (haven't looked at the source yet) or at least pixmap-to-print. So YAY! for me and my specific needs.
However, I doubt this is very interesting to most. And as Nautilus maintainer, IMO, Alex should've focused on bringing that up to standards first. It's still so _abysmally_ slow with even a low 4-figure number of files per folder that it's not funny. 2.12.0 still takes in the order of 10 seconds on a 2GHz AMD machine. Worse, when this combines with the new spring-loaded-foldout on a d-n-d copy, it forces desperation upon the user because s/he not just can't continue, but has to hold down the mouse button to avoid dropping the files somewhere in nirvana.
I use Gnome for 95% of my daily work, but in this case it's actually faster to load the whole Qt-lib-chain, navigate to the given folder, and _still_ have Konqueror not just run circles around it, but de-class Nautilus into the realm of the ridiculous. Right down there with the 10.0.0-Finder.
Printing is also absent, so there's a lot to do.
Now, folks, the question arises "It's FLOSS, so why don't you scratch your itch and code it yourself?". I actually might have considered delving a bit into Nautilus and read a bit of the mailing list. It seems to be that Alex is rather quick at patch rejections with either a "this won't work" or a "this is not how i like it" attitude rather than a somewhat more constructive approach - so at least some efforts will be lost in friction. The first reason likely comes from bad maintainability of the code base, but then I'd say it's his task to bring it into shape for larger participation. Maintaining such a core component IMO brings a bit more responsibility than happily hacking along as a part time job besides making GTK offscreen-happy.