Linked by Thom Holwerda on Tue 25th Sep 2007 18:40 UTC
Gnome Ars has reviewed GNOME 2.20. "GNOME 2.20 was officially released last week after six months of development. The new version includes strong incremental improvements that contribute to a better user experience and provide more flexibility and integration opportunities for third-party software developers."
Thread beginning with comment 274372
To view parent comment, click here.
To read all comments associated with this story, please click here.
Anonumous
Member since:
2007-06-13

Alexander Larsson (Nautilus maintainer) is doing the heavy lifting and working on a gnome-vfs replacement called GVfs that will be put in the right place of the stack, i.e. GLib/GTK+.

Thumbnails in the filechooser will be a cake walk when that's done.

It might land sooner than you think. He's even proposed it for GNOME 2.22.

http://mail.gnome.org/archives/desktop-devel-list/2007-September/ms...

Edited 2007-09-25 20:49

Reply Parent Score: 5

superstoned Member since:
2005-07-07

I don't get why there aren't filepreviews and such in the filechooser. Doesn't the filechooser just reuse code from Nautilus? Or is it something totally different? Of course, I'm looking at this from a KDE view, where I know Dolphin offers it's fileview to Konqueror and every filedialog in KDE - so they all have filepreviews, several basic viewing capabilities like list/icons/details and some basic editing like 'new folder'. That approach just makes sense to me - can't you guys do that in Gnome? Or is code reuse evil, or is it impossible due to architecture, or???

Reply Parent Score: 2

FooBarWidget Member since:
2005-11-11

"Doesn't the filechooser just reuse code from Nautilus?"

It doesn't. They want GTK to be independent and don't want it to depend on Nautilus, so they don't use Nautilus code and thus it doesn't support file previews natively.

Reply Parent Score: 2

Anonumous Member since:
2007-06-13

The VFS (GNOME-VFS) has traditionally been higher in the stack than the toolkit (GTK+/GLib). This made using GNOME-VFS in the lower parts of the stack hard (interfaces and abstractions had to be used).

GVfs/GIO will be put in the right place of the stack, namely in the toolkit itself. (And hence, no more abstractions are needed... on that level at least.)

Reusing too much stuff (some might be reasonable...) from the filemanager would just lead to another bunch of abstractions.

I guess KDE is a bit different since it builds a layer on top of the toolkit so abstractions are the rule rather than the exception? (Note: I haven't looked on any KDE code in a looong time...)

Reply Parent Score: 4