>
> I'm just arguing against adding checkboxes arbitrarily just in case the
> user wants to do anything. That's bad UI design.
> I'm trying to discuss the costs and benefits of adding that complexity.
> Isn't this achievable with different tools and methods? Is it needed so
> frequently that is rea
El dom, 03-05-2015 a las 13:32 -0400, Robert Krawitz escribió:
> On Sun, 03 May 2015 02:34:26 -0300, Gez wrote:
> > El sáb, 02-05-2015 a las 12:40 -0400, Elle Stone escribió:
> >
> >> Well, you might be able to answer that question. I'm not qualified.
> >> Personally I don't use alpha channels exce
Elle, I'd be happy to help provide some alternate UI options for for
layers, GEGL, etc. Shall we collaborate a bit on a less cluttered UI
proposal first, then bring it back? I think that's the main sticking point
here. No one seems to be against the actual implementation if we can keep
it simple an
Offering another perspective on this topic, I don't personally care at all
about switching back and forth for specific operations if the results are
generally pleasing. Most people learn GIMP, PhotoShop, etc. by using the
tools and seeing what they do, then using those operations to fit their
speci
On Sun, 03 May 2015 02:34:26 -0300, Gez wrote:
> El sáb, 02-05-2015 a las 12:40 -0400, Elle Stone escribió:
>
>> Well, you might be able to answer that question. I'm not qualified.
>> Personally I don't use alpha channels except in the extremely rare
>> instance when I'm exporting a png with a tra
El sáb, 02-05-2015 a las 12:40 -0400, Elle Stone escribió:
> Well, you might be able to answer that question. I'm not qualified.
> Personally I don't use alpha channels except in the extremely rare
> instance when I'm exporting a png with a transparent background for use
> on a website.
See, th
On 05/02/2015 03:39 PM, Øyvind Kolås wrote:
I'm not entirely sure what you are proposing or how it could be implemented
>in the UI. Is this what you mean?
>
>1. Make a list of all RGB editing operations that are provided by GIMP.
>
>2. Decide for each operation whether it should be done using lin
On Sat, May 2, 2015 at 3:12 PM, Elle Stone
wrote:
> On 05/02/2015 02:44 PM, Øyvind Kolås wrote:
>>
>> On Sat, May 2, 2015 at 9:45 AM, Elle Stone
>> wrote:
>>>
>>> To be more blunt, the babl flips are Pippin's brain-child. If Pippin says
>>> "no user choice", is there any real benefit to anyone if
On 05/02/2015 02:44 PM, Øyvind Kolås wrote:
On Sat, May 2, 2015 at 9:45 AM, Elle Stone
wrote:
To be more blunt, the babl flips are Pippin's brain-child. If Pippin says
"no user choice", is there any real benefit to anyone if I write up a spec?
Wouldn't it just be a waste of everyone's time?
I
On Sat, May 2, 2015 at 9:45 AM, Elle Stone
wrote:
> To be more blunt, the babl flips are Pippin's brain-child. If Pippin says
> "no user choice", is there any real benefit to anyone if I write up a spec?
> Wouldn't it just be a waste of everyone's time?
I have not stated *no*user*choice*, but I h
On 05/02/2015 10:21 AM, Gez wrote:
El sáb, 02-05-2015 a las 06:09 -0400, Elle Stone escribió:
But you're not proposing to add a toggle to gradients alone, you're
proposing to put them*everywhere*.
Yes.
And your reason is that users have to decide how operations are
performed, no matter the
El sáb, 02-05-2015 a las 11:18 -0400, Robert Krawitz escribió:
> On Sat, 02 May 2015 11:21:37 -0300, Gez wrote:
> > El sáb, 02-05-2015 a las 06:09 -0400, Elle Stone escribió:
> >> > I'd like to see this discussion heading towards a real world list of
> >> > examples of real needs for such options t
On Sat, 02 May 2015 11:21:37 -0300, Gez wrote:
> El sáb, 02-05-2015 a las 06:09 -0400, Elle Stone escribió:
>> > I'd like to see this discussion heading towards a real world list of
>> > examples of real needs for such options that can't be satisfied with
>> > anything else than these toggles.
>>
El sáb, 02-05-2015 a las 06:09 -0400, Elle Stone escribió:
> > But you're not proposing to add a toggle to gradients alone, you're
> > proposing to put them*everywhere*.
>
> Yes.
And your reason is that users have to decide how operations are
performed, no matter the result, no matter if it make
On 05/02/2015 09:00 AM, Michael Schumacher wrote:
On 05/02/2015 01:28 PM, Elle Stone wrote:
On 04/30/2015 05:43 PM, Michael Schumacher wrote:
For examples have a look at the Save & Export and Single Window Mode
specifications:
* http://gui.gimp.org/index.php/Save_%2B_export_specification
On 05/02/2015 01:28 PM, Elle Stone wrote:
> On 04/30/2015 05:43 PM, Michael Schumacher wrote:
>> For examples have a look at the Save & Export and Single Window Mode
>> specifications:
>>
>> * http://gui.gimp.org/index.php/Save_%2B_export_specification
>>
>> * http://gui.gimp.org/index.php/Singl
On 04/30/2015 05:43 PM, Michael Schumacher wrote:
On 04/30/2015 11:40 PM, Elle Stone wrote:
What are specifications?
Something that describes how features are supposed to work when they are
implemented.
For examples have a look at the Save & Export and Single Window Mode
specifications:
* ht
On 05/01/2015 07:03 PM, Gez wrote:
You chose one of the few cases where both linear and perceptually
uniform could be valid options and none of them are right or wrong.
Of course I'm not against allowing two valid instances of the same
thing, like in this case.
I've already given other exampl
El vie, 01-05-2015 a las 18:03 -0400, Elle Stone escribió:
> On 05/01/2015 04:47 PM, Gez wrote:
> > El vie, 01-05-2015 a las 05:40 -0400, Elle Stone escribió:
> >
> >> >This is a color managment issue. It's fundamentally important. GIMP
> >> >shouldn't make decisions like "use linear here and perce
On 05/01/2015 04:47 PM, Gez wrote:
El vie, 01-05-2015 a las 05:40 -0400, Elle Stone escribió:
>This is a color managment issue. It's fundamentally important. GIMP
>shouldn't make decisions like "use linear here and perceptual there",
>other than to offer the user good defaults.
A color managem
El vie, 01-05-2015 a las 05:40 -0400, Elle Stone escribió:
> This is a color managment issue. It's fundamentally important. GIMP
> shouldn't make decisions like "use linear here and perceptual there",
> other than to offer the user good defaults.
A color management issue? You're proposing to le
On 05/01/2015 08:46 AM, Douglas Ray wrote:
On 1/05/15 12:00 PM, Gez wrote:
El jue, 30-04-2015 a las 17:40 -0400, Elle Stone escribió:
http://ninedegreesbelow.com/bug-reports/gimp-linear-perceptual-rgb.html
Is what's shown in the screenshots feasible in terms of linking the
operations to the pr
On 05/01/2015 09:25 AM, Ofnuts wrote:
It depends a bit what the workflow is. If users need to switch all tools
at random between linear and perceptual, this will be complicated.
Complicated or not, it really is needed.
But
if you can categorize workflows into those that are always perceptual,
On 01/05/15 04:00, Gez wrote:
Hi Elle,
You know I'm with you regarding giving users more control over how
operations are performed, but tossing buttons for toggling between
linear and perceptual everywhere in the UI is not a proper solution.
It would be extremely confusing, and people would start
On 1/05/15 12:00 PM, Gez wrote:
El jue, 30-04-2015 a las 17:40 -0400, Elle Stone escribió:
On 04/29/2015 03:57 PM, Joao S. O. Bueno wrote:
Now help us think on the next steps. For example get that e-mail
worked into a feasible specification: If you can, refine it, then
maybe try to get someone
On 04/30/2015 10:00 PM, Gez wrote:
I think that allowing that would complicate the UI and the the tools
themselves, as all of them should have both paths available.
All the tools need to provide the user with the ability to choose linear
or perceptual RGB at will, at the user's discretion. And
El jue, 30-04-2015 a las 17:40 -0400, Elle Stone escribió:
> On 04/29/2015 03:57 PM, Joao S. O. Bueno wrote:
>
> > Now help us think on the next steps. For example get that e-mail
> > worked into a feasible specification: If you can, refine it, then
> > maybe try to get someone with UI expertise t
On 04/30/2015 11:40 PM, Elle Stone wrote:
> What are specifications?
Something that describes how features are supposed to work when they are
implemented.
For examples have a look at the Save & Export and Single Window Mode
specifications:
* http://gui.gimp.org/index.php/Save_%2B_export_speci
On 04/29/2015 03:57 PM, Joao S. O. Bueno wrote:
Now help us think on the next steps. For example get that e-mail
worked into a feasible specification: If you can, refine it, then
maybe try to get someone with UI expertise that could fine tune that
your suggestions into specifications that could
Hi Elle -
Seeing your e-mail give the same kind of "and what can I do about it"
feeling I have when talking to Americo (he should also be reading
this mailing list by now).
There are obvious lots of improvements that _could_ be done so that
GIMP would be a killer application.
What you do on the
On 04/19/2015 06:44 AM, Elle Stone wrote:
The single biggest useability issue with GIMP 2.9 is the mechanism for
allowing the user to switch between linear and perceptually uniform RGB.
On 04/19/2015 03:40 PM, Liam R. E. Quin wrote:
> In the meantime in my own workflow the lack of "repeat last
The single biggest useability issue with GIMP 2.9 is the mechanism for
allowing the user to switch between linear and perceptually uniform RGB.
In the current UI, the user has no way to know whether any given editing
operation is performed on linear or perceptually uniform RGB. For most
operat
32 matches
Mail list logo
