Re: [darktable-dev] Feature request: Warning for keyboard shortcut collisions

[Patrick Shanahan]

* Hobbes Pirakitti  [11-23-18 17:49]:
> Hi! I am a new darktable user, and I'm exploring how darktable can fit into
> my raw processing workflow.  I like the ability to set up shortcuts.  One
> feature request I have regarding shortcuts is that I would like darktable
> to pop up a warning if the shortcut I am trying to assign is already
> taken.  Is this is right place to make this request?

  https://redmine.darktable.org/projects/darktable/issues/new

is where the dev's track.
-- 
(paka)Patrick Shanahan   Plainfield, Indiana, USA  @ptilopteri
http://en.opensuse.orgopenSUSE Community Memberfacebook/ptilopteri
Registered Linux User #207535@ http://linuxcounter.net
Photos: http://wahoo.no-ip.org/piwigo   paka @ IRCnet freenode
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] Feature request: Warning for keyboard shortcut collisions

[Hobbes Pirakitti]

Hi! I am a new darktable user, and I'm exploring how darktable can fit into
my raw processing workflow.  I like the ability to set up shortcuts.  One
feature request I have regarding shortcuts is that I would like darktable
to pop up a warning if the shortcut I am trying to assign is already
taken.  Is this is right place to make this request?

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

[darktable-dev] what happens with linux color management ?

[Aurélien Pierre]

Hi everyone,

my darktable is installed on Ubuntu Budgie (fork of Gnome 3), but it was
the same when I used Gnome Shell.  I have a custom screen ICC profile
installed in gnome-color-manager, and loaded in darktable through colord.

When I change the ICC profile on Gnome with darktable open, the colors
of the darkroom preview change too (no matter if darktable uses the
system display profile or one built-in profile, like Adobe RGB). That is
the contrast and white point of the picture, plus the color of the UI.

So that means that the OS is stacking another color transformation on
top of darktable's one.

Fromthis article

(2011), I get that gnome expects apps to take care of themselves :

One of the things I tried to deliberately ignore designing colord
was actually flipping pixel values. Colord is a very high level
daemon that can say to apps like Krita or GIMP “Use this profile for
this device” rather than them supplying a 140Mb memory buffer and an
operation list. This means we can do the conversion on the CPU using
lcms2 for some programs and using the GPU using a shader in things
that use 3D. By not trying to wrap lcms we can let the application
do the pixel conversion in the right layer in the right way.

Of course, the downside of this is that you have to patch
applications to actually do the right thing. We can make this easier
by doing some framework code for Clutter and Cairo, but sooner or
later the application has to know about color management in one form
or another. This is going to be my main focus for GNOME 3.4; now we
have all the framework installed and working and we can say to
application authors “It's already installed, so don't worry about
the additional dependency, just commit my patch and it'll just work”.

But gnome-color-manager has no documentation, and even the Gnome color
dev documentation is pretty useless (a lot of "how to", no "what's going
on", but they found time to design a cheesy kindergarten theme).

Looking at GDK pixbuf doc, they don't have tags to explicitely say "hey
that's already color-corrected so bug off". The Wikipedia entry ofLinux
color management 
is as helpful and factual as a marketing director motivational speech
(let's increase the leverage of color management by ensuring the quality
of good devices, with a pro-active method to supervise critical elements
in a proficent way — sure !).

As of now, I have seen no block diagram to describe the full color pipe
in Linux, nor any way to ensure the quality of the transform.

>From the info I have gathered, the pipe I have put together is as follow:

|| darktable pipe -> LCMS/(Internal cmatrix color correction + TRC) ->
Cairo surface -> GDK pixbuff -> || -> Mutter compositor -> (OS color
correction ? TRC ?) -> Xorg -> Nvidia/Intel GPU driver -> (Color
correction ? VCGT ?) -> || -> HDMI DAC (gamma 2.2) -> Screen

So my question is : does anyone have any idea of what's going on with
color on Linux, or are we stacking ICC on top of shit just to pretend
it's color-managed magically, somehow ?

Thanks,

Aurélien.


___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Studying darktable source code, suggestions

[Sturm Flut]

Hi,

I usually come up with something I want to change (my first patch for
darktable added a "Compression Level" slider to the PNG output module)
and then work through the source code until I know everything I need to
get it done. This has been my general strategy for the last ~20 years,
and it has worked quite well for me.

cheers,
Simon



Am 19.11.2018 um 13:51 schrieb Germano Massullo:
> I am going to study darktable source code, in order to geto used to
> GLib/Gtk stack.
> Do you have any suggestion for me, of any kind? For example "start
> with this, then go through that, etc."
> I have read the book (not yet completed by its author) "The GLib/Gtk+
> development Platform" by Sébastien Wilmet, and then I have read some
> of GNOME development documentation, that I found to be too
> "reference", and "sterile".
> 
> Thank you
> ___
> darktable developer mailing list
> to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org
> 
___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Norwegian bokmål (nb) translation

[Pascal Obry]

Hello Pierre,

The link you sent is:

https://github.com/darktable-org/darktable/pull/1739

At the bottom of the page I see error reported by GtiHub saying that there
is conflicts.

Also your branch has multiple "merge with... ", "merge remote-tracking..."

To clean-up the history, and since you've committed on your master branch:

1. update your darktable to latest version of master (git pull --rebase)
2. resolve conflicts if any
3. force push your branch : git push mepi0011 master

Hope this helps. Thanks.

-- 
  Pascal Obry /  Magny Les Hameaux (78)

  The best way to travel is by means of imagination

  http://photos.obry.net
  http://www.obry.net

  gpg --keyserver keys.gnupg.net --recv-key F949BD3B

___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org

Re: [darktable-dev] Norwegian bokmål (nb) translation

[openhab.doc]

Hello Pascal,

thank you for the answer.

Can you please explain your comment a little more detailed?
I see no conflicts in my pull request.

Thanks
Pierre Metzner

Am Donnerstag, 22. November 2018, 21:10:03 CET schrieb Pascal Obry:
> Hi,
> 
> > https://github.com/darktable-org/darktable/pull/1739
> > 
> > 
> > I would be happy if the German translation is published together with
> > version 2.6.
> 
> This is the usermanual which is taken care by Ulrich. So I let him
> decide when to merge.
> 
> In the mean time, if you could rebase on master to avoid all merges and
> resolve the conflict in the PR it would be nice.
> 
> Thanks,




___
darktable developer mailing list
to unsubscribe send a mail to darktable-dev+unsubscr...@lists.darktable.org