On Tue, Sep 3, 2019, at 04:28, Bruce Williams wrote:

> But now I'm wondering... is 2.7.0 the most recent build?

The versions built from master (currently the "2.7" development branch) are 
generally denoted by refering to the point in the commit history they were 
built from. There's a script in the tools directory of the repository that will 
return a nicely formatted version string, you can use it in your build script 
something like this:

 VERSION=$(./tools/get_git_version_string.sh)

That path is releative to the "src" directory, adjust accordingly.

> I ask because I was under the impression that the interface had 
> undergone a bit of an overhaul, and what I'm seeing looks just like 
> 2.6.2.

The changes are fairly profound, but some of it might not be immediately 
apparent. Custom widgets have been replaced by standard GTK versions, which may 
result in a slightly different "look and feel". There's been some changes to 
the bottom panel (the current behavior when clicking on the arrow to show/hide 
is a little odd, having more than two states). There's a new configurable 
information display in darkroom, replacing what was previously shown in the 
histogram, and the histogram itself can now be hidden... there's a new 
"culling" mode... and other stuff I can't list off the top of my head. Browsing 
through the commit history will show up relevant pull requests, and these will 
often have some informative discussion attached to them, if other documentation 
is lacking.

The tagging module has been improved in many ways, be sure to check that out.

Of course, the big one (for me, at least) isn't really "visible" at all: you 
can now Ctrl+Shift+Click on the headers of the various iop modules in darkroom 
and drag them to different positions in the processing pipe. The position will 
be saved when creating "Styles". This means you can now do stuff like move the 
"vignetting" module down next to lens correction and use it to actually correct 
(approximately) or simulate real lens falloff... it's worth emphasizing that 
modules should NOT be re-arranged just for UI convenience purposes, because 
doing so will alter the actual processing order.

Anyway, that's what comes to mind, hopefully it gives a starting point for 
further exploration.

-- 
jys
____________________________________________________________________________
darktable user mailing list
to unsubscribe send a mail to [email protected]

Reply via email to