Hi,
Akkana Peck <[EMAIL PROTECTED]> writes:
> It really is fairly tricky with the new file selector to explain to
> people how to get to files in ~/.gimp (for instance, to save or
> manage custom brushes, gradients etc.)
Perhaps the question that we should ask ourselves is, why do we
require use
Hi,
Akkana Peck <[EMAIL PROTECTED]> writes:
> It really is fairly tricky with the new file selector to explain to
> people how to get to files in ~/.gimp (for instance, to save or
> manage custom brushes, gradients etc.)
While we are on it, could you perhaps try to make a list of use cases
where
On Wednesday 15 February 2006 16:18, Sven Neumann wrote:
> The user should never ever have to do this. We need to either
> move some of our resource files into a visible folder or we
> need to provide a user interface to manage resource files that
> doesn't involve using a file manager.
All of wh
From: Leon Brooks <[EMAIL PROTECTED]>
Date: Wed, 15 Feb 2006 18:28:22 +0800
On Wednesday 15 February 2006 16:18, Sven Neumann wrote:
> The user should never ever have to do this. We need to either
> move some of our resource files into a visible folder or we
> need to provide a u
On 2/15/06, Robert L Krawitz wrote:
>All of which sounds like _much_ more work (and many more design
>decisions) than simply making the file selector work consistently.
>
> Not to mention that someone might want to edit files in a hidden
> directory for other reasons (e. g. thumbnail files
> Von: Alexandre Prokoudine <[EMAIL PROTECTED]>
> >All of which sounds like _much_ more work (and many more design
> >decisions) than simply making the file selector work consistently.
> >
> > Not to mention that someone might want to edit files in a hidden
> > directory for other reasons
On Wednesday 15 February 2006 10:42 am, Robert L Krawitz wrote:
>From: Leon Brooks <[EMAIL PROTECTED]>
>Date: Wed, 15 Feb 2006 18:28:22 +0800
>
>On Wednesday 15 February 2006 16:18, Sven Neumann wrote:
>> The user should never ever have to do this. We need to either
>> move some
