On Sun, May 12, 2013 at 8:14 PM, Marie-Noëlle Augendre <[email protected]
> wrote:
> 2013/5/12 Pascal de Bruijn <[email protected]>
>
>> On Sun, May 12, 2013 at 2:58 PM, Jiew Peng Lim <[email protected]>
>> wrote:
>> > Hi,
>> >
>> > -For my first suggestion, I am not saying that we should rearrange the
>> order
>> > in which the changes are applied to the image,
>>
>> This is exactly what should happen. Without it, the whole process
>> becomes opaque.
>>
>> > but rather to rearrange the
>> > modules to suit the order in which we edit photos (For instance, if
>> someone
>> > always tweaks exposure before shadows/highlights, it is more logical to
>> have
>> > the exposure module above the shadows/highlights one, rather than the
>> other
>> > way round. regardless of the order in which the effects are applied on
>> > export). If this isn't possible without altering the order in which
>> changes
>> > are applied to the image, then scrap my suggestion.
>>
>> I think you're confusing a few things.
>>
>> We will likely always show modules in the order they are applied,
>> doing anything else, makes the process opaque and hard to troubleshoot
>> if any unexpected behavior happens. Stuff like this "regularly" bit me
>> in applications which do not offer this kind of transparancy.
>>
>
> What about offering the choice to the user:
> - default as it is: modules stay in the processing order
> - option to drag/drop (or whatever) in order for the user to choose the
> order he wants the modules to appear; and revert to default whenever he
> likes to.
>
The problem is that people will move stuff around, and then make very
invalid assumptions about order of application. This will confuse people to
a very high degree, and likely generate a lot of avoidable questions about
why moving modules around doesn't change the image.
So this is "easy" to want, if you don't have to do user support. But we do
have to live with the consequences of such a choice.
> I (think I) understand your technical point of view.
>
It's not just a technical point. It offers users insight into how stuff
works. The value of this is highly underestimated.
> But I also think that UI should be as user-friendly as possible;
> currently, I (and I guess I'm not alone) am loosing quite a lot of time
> looking around for the specific module I want to work with at that precise
> moment, and that happens for almost every picture I work upon.
>
Which is more or less why the favorites category exists, which you can
customize.
> Add all the lost seconds/minutes when you have many pictures to develop...
>
We've discussed something like a quick-access panel before, which only has
the most importantly sliders from several critical modules, but nothing has
been decided, as it is quite an involved process to design/implement. So
basically that discussion is in storage for re-discussion in the deeper
future.
As already pointed out, for 1.4 we'll be focusing on masks.
Regards,
Pascal de Bruijn
------------------------------------------------------------------------------
Learn Graph Databases - Download FREE O'Reilly Book
"Graph Databases" is the definitive new guide to graph databases and
their applications. This 200-page book is written by three acclaimed
leaders in the field. The early access version is available now.
Download your free book today! http://p.sf.net/sfu/neotech_d2d_may
_______________________________________________
Darktable-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/darktable-users
