[Fxruby-users] Re: Fxruby-users digest, Vol 1 #57 - 2 msgs

[jeroen <je...@fo...>]

> Message: 1
> Date: Thu, 11 Sep 2003 17:01:17 +0200
> From: =?ISO-8859-1?Q?Kristoffer_Lund=E9n?= <kun...@ho...>
> To:  fxr...@li...
> Subject: [Fxruby-users] Default associations in FXFileList and FXDirList
> Reply-To: fxr...@li...
>
> Hello!
>
> I am toying a bit with FXFileList and also FXDirList - pretty easy to
> get running, but I wonder about the associations to the files, and their
> icons.
>
> I've tried ot google a bit, and I've went through this list and searched
> the original FOX documentation - I'm sure it is there somewhere, but I
> must be looking in the wrong place then...
>
> Are there any good way to import the default icons, or has anyone
> aldready done the job of creating something that imitates the usual
> options? Seems a bit silly to manually tie mp3 to this icon etc when the
> system already does that somewhere else - that information is apparently
> available as other applications can get at it. Any ideas and tips are
> welcome, otherwise I guess I'll have to do that work and share it
> instead. ;-)
>
> Also, I am having a bit of trouble with FXDirList - no matter what I set
> directory to, it always starts at 'C:\' - am I doing something wrong?
> All I do is create it, then set the directory, which works with FXFileList.
>
> I am trying this out on an Win XP box, with ruby 1.8.0 and FXRuby 1.0.22
> (I think). Got it all in that package that the Pragmatic Programmers put
> together for Windows. However, I will not only be on this platform, so
> if there are any Windows specific issues, I'd be thankful if that was
> noted. :)
>
> -- Kristoffer

Kristoffer,

The FXDirList in FOX 1.0 did have this bug under Windows; the new one in
FOX 1.1.x however shows the list of drives as it was supposed to.  

The workaround for the old FXDirList is to prefix the drive letter in
front of the path; if you don't, the routines which turn a path into
a normalized absolute path will slap the default drive letter in front
[it will also expand environment variables and simplify the path].

As for the file types, it is as follows.  On Windows, FOX uses the 
registry but continues to follow its own bindings-database; it *is* 
possible to write a tool which populates this bindings database
from the "normal" Windows associations [the native file- associations
are splattered all over the place, and in some cases the icons have to
be lifted out of executables].

On Unix, one can simply drop a text file (the FOX registry is human-readable
text on UNIX) into $HOME/.foxrc/Desktop and have bindings available for 
all applications.



	- Jeroen




+----------------------------------------------------------------------------+
| Copyright (C) 20:20 09/11/2003 Jeroen van der Zijp.   All Rights Reserved. |
+----------------------------------------------------------------------------+