Re: ANN: XRay 1.0b2 avaliable for download
Re: ANN: XRay 1.0b2 avaliable for download
- Subject: Re: ANN: XRay 1.0b2 avaliable for download
- From: Rainer Brockerhoff <email@hidden>
- Date: Thu, 4 Oct 2001 14:54:09 -0300
>
Date: Thu, 4 Oct 2001 08:54:23 -0500
>
From: "Eric L. Anderson" <email@hidden>
>
>
On Thu, Oct 04, 2001 at 09:49:07AM -0300, Rainer Brockerhoff wrote:
>
>
>
> I'll look into it, but this raises a UI question: is it OK to display data
>
> in one format in an editable field ("drxwrxwrxw") but accept editing only
>
> in another format ("777")? Sounds unintuitive to me, frankly. I think at i
>
> least it should accept changing one of the 'r's to '-', for instance... but
>
> then I'd have to write a special formatter to not let people change (or
>
> even select) the 'd'...
>
>
How about a preferences setting which sets how permissions are displayed,
>
either in symbolic or numeric. Then, which ever version is displayed is the
>
method in which they can be edited. In other words, if the display is set to
>
symbolic, then you can only modify the permissions symbolically.
Interesting point. At the very least, I'll change between the drwxrwxrwx and 7777 formats by clicking on the field...
>
Date: Thu, 04 Oct 2001 10:26:26 -0400
>
From: John Timmer <email@hidden>
>
>
Make the popup list of available types be a combo button, and have that
>
button accept drag and drop of other files. For the casual user, it's
>
probably the easiest way of getting at the type/creator of files they're
>
interested in.
Great idea, I'll implement this in combination with Ondra's idea below.
>
From: Ondra Cada <email@hidden>
>
Date: Thu, 4 Oct 2001 16:09:40 +0100
>
>
JT> >I know there are calls for that in Launch Services... calls like
>
JT> >_AppGetAllApplications and so forth. Perhaps a part of that API should
>
JT> >be published, at least to let us have read-only access to the
>
JT> >application lists.
>
>
Although I *do* agree that OS *should* do that for you, the workaround is
>
quite easy in this case: scanning all applications and constructing the list
>
for yourself would be quite simple -- I guess something in order of 10-20
>
source lines. Just use NSSearchPathForDirectoriesInDomains and NSFileManager
>
to scan all applications, NSDictionary to read in their Info plists, and
>
that's that.
There are more complicated steps to be done for Carbon and Classic apps, but you're right. I'll have a button for rebuilding application info somewhere, _and_ a means of including a new application by drag&drop. It's just that it's tantalizing to have this info already stashed somewhere and no way to get at it ;-)
Excluding applications would probably unnecessary...?
--
Rainer Brockerhoff <email@hidden>
Belo Horizonte, Brazil
"Originality is the art of concealing your sources."
http://www.brockerhoff.net/ (updated Oct. 2001)