[Bf-committers] integrating to desktops (Re: [Bf-blender-cvs] SVN commit: /data/svn/bf-blender  branches/blender2.5/blender/source /blender/windowmanager/intern/wm_window.c: Removed silly Global windowstate variable.)
kungfoobar at gmail.com
Sat Jan 5 00:41:56 CET 2008
Personally I don't like windows filechooser, I hate the GTK one, and I
love the KDE one, for the following reasons:
- I can write any path, use autocompleton and use patterns (* and ?)
to filter the content, mouse is not needed at all (which is what most
resembles my beloved terminal).
- It has thumbnails, previews and favourite sites. I can copy, move,
delete and rename files.
- It supports Kioslaves, which allows me to access any remote file
from a lot of protocols without having to mount anything. That's the
point of Kioslaves. Ok, there are a lot of ways to mount any remote
filesystem anywhere, but it has three drawbacks: I have to mount it
(what if the file listing is not available? e.g. most http hosted
files); the file dialog doesn't know which is a remote filesystem and
may try to make thumbnails of large files; and it cannot handle
I can write a FUSE app that maps every kioslave to a folder, for
example /kio/http:// to http, but it would solve only one of the
drawbacks mentioned above.
GSR, there is no need to use python modules that the user may have not
filename = os.popen3("kdialog --getopenfilename ~ '*.blend'").read()
In gnome, use zenity --file-selection
2008/1/4, Chris Burt <desoto at exenex.com>:
> As a user who follows this mailing list as closely as I can, I wanted
> to offer an "outside" perspective. Perhaps it won't be useful for the
> discussion, but I wanted to state that I, for one, like Blender's way
> of doing things and find the file selection dialogs of GTK and Windows
> etc. to be disorganized, and inefficient.
> If it came down to a vote, I would vote that Blender continue to use
> its own native file selector, which although could use improvement,
> feels to me like a solid and simple way of getting things done. As a
> user, I feel as though the addition of an OS native dialog box would
> add inconsistency to Blender, and in my opinion this should be avoided
> at all costs.
> On Jan 4, 2008 12:30 PM, Stephen Swaney <sswaney at centurytel.net> wrote:
> > On Thu, Jan 03, 2008 at 06:17:08AM +0200, Toni Alatalo wrote:
> > One problem you run into trying to mix widget toolkits is that most of
> > them like to have their own event loop. A lesser, but not
> > insignificant problem is the maintenance overhead of multi-OS GUIs.
> > I know Free Desktop is trying to bridge the gap between kde, gnome and
> > other Xll desktops, but I'm really not familiar with it. Supporting
> > open standards is good, but this leaves out Windows and possibly(?)
> > OSX.
> > --
> > Stephen Swaney
> > sswaney at centurytel.net
> > _______________________________________________
> > Bf-committers mailing list
> > Bf-committers at blender.org
> > http://lists.blender.org/mailman/listinfo/bf-committers
> Bf-committers mailing list
> Bf-committers at blender.org
More information about the Bf-committers