Having seen similar discussions in the past, I agree with HaJo:
--------------
> However, as good as it is in the image processing modules, I find it
lacking some matching quality in UI/functionality design. I have the
feeling that the developers focus on image processing and consider the UI
as a necessary evil that they can't live without. The UI is not bad, but
IMHO it lacks the matching "wow-factor" that the image processing possesses.
--------------
There is a much stronger emphasis on the programming side of development,
which seems to work fine (not an expert, I'm happy with it), and the UI
seems to be more of an unloved child. There has been some thinking going
into the UI design that introduced some very smart fixes (fine tuning
sliders being but one example). But consistency (also with well-defined
standards like orthography) and minimising surprises in the UI are the most
obvious places where darktable lacks. E.g. last time I looked, setting
metadata (& tags) during an import overwrote the default metadata and the
same tags and metadata were applied on a later import - that behaviour
definitely surprised me.
On another note, hovering over images has caused quite a lot of
time-consuming fixing of mistakes, trying to undo and - mainly -
discussions. I would like to add to that (sic!) and suggest that hover mode
allows viewing information on an image, but actions are _always_ applied to
selected images only. If no images are selected, then no action is executed
and a explanatory message shown (e.g. "no images selected"). That way,
hovering remains a valuable tool and surprises are reduced. (How many of
you use hovering in any other application?) The paradigm of the file
manager just works and is what people are used to. I select the things that
I want to act on (e.g. open/delete/move/...), then I act on them.
On 1 August 2013 08:28, Chris Siebenmann <[email protected]> wrote:
> A general thought sparked by this thread: maybe part of the problem is
> that it is not obvious when images are selected and thus how many images
> will be affected by an operation? I know that I sometimes have problems
> telling apart selected / unselected / hovered over on the lighttable and
> I've sometimes miss-guessed what's selected and not selected.
>
> (Right now the only way to tell whether or not the image you're hovering
> over is selected is by a small change in the state of the border around
> it. Selected vs non-selected in other images is just light grey versus
> darker grey, and if I wasn't thinking about it I'm not sure I'd spot
> whether all of the visible lighttable images were selected or none of
> them were.)
>
> - cks
>
>
> ------------------------------------------------------------------------------
> Get your SQL database under version control now!
> Version control is standard for application code, but databases havent
> caught up. So what steps can you take to put your SQL databases under
> version control? Why should you start doing it? Read more to find out.
> http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
> _______________________________________________
> Darktable-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/darktable-users
>
------------------------------------------------------------------------------
Get your SQL database under version control now!
Version control is standard for application code, but databases havent
caught up. So what steps can you take to put your SQL databases under
version control? Why should you start doing it? Read more to find out.
http://pubads.g.doubleclick.net/gampad/clk?id=49501711&iu=/4140/ostg.clktrk
_______________________________________________
Darktable-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/darktable-users
