On Fri, 2005-12-02 at 19:49 +0100, Christian Neumair wrote: > I hoped to significantly speed up Nautilus by caching each > NautilusFile's URI and exposing API for getting cached file info.
I'm putting the work on file chooser optimization on hold until Kris commits his async API changes for GtkFileSystem. In the meantime, let's find out why Nautilus is slow :) One big problem I found with the file chooser is that it is hard to know when it is *really* done loading a folder and done displaying it. Does Nautilus have a place where it knows it is done loading? I remember adding a patch at some point to gdk_beep() when a directory was done loading, but this did not take into account the code that actually displays the icon view/list view. I don't know if once the directory is loaded, Nautilus has another async layer to populate the views and lay them out. [Hans Petter and I were playing with Windows XP the other day - their file manager is mightily fast...] Federico -- nautilus-list mailing list [email protected] http://mail.gnome.org/mailman/listinfo/nautilus-list
