Hi,
Be aware I'm not a developer so my comments can be wrong.
Am 09.04.2016 um 15:22 schrieb Christian Kanzian:
Hi,
I just read your message at gmane.
I've unsubscribed the mailing list due to time reasons. Anyway, Jereme
is
quite busy and may not answer.
1. How can I change the size of the entry fields? Is this possibility
already implemented? If yes, where can I find the documentation?
doc can be found here: http://www.darktable.org/lua-api/index.html.php
or you can build the pdf with
$cd ./build && make make darktable-lua-api
like the usermanual. What's written there is possible. If it is not
there you
simple can't do it.
That's one of the problems: Of course I try to learn from the
documentation (especially the Lua API documentation), but it is not
really very detailed and for me it is hard to understand where the
limits are. E.g., some problems may be possible to circumvent or may be
default Lua and therefore not documented in the API docs.
Yes I'm in the same situation. Here is the default Lua:
https://www.lua.org/manual/5.2/
Because I'm already middleaged, sitting all day long in front of a
screen I usually print this manuals for later reading ;-).
Takes a lot of time for me to get simple things working. E.g. until now
I still don't know howto reload a lua script without restarting
darktable.
Should be easy from a developers point of view. What's even more
confusing is, that sometimes you need to know how darktable is supposed
to work. e.g. darktable.gui.action_images.
Does your answer mean that everything I try to achieve is impossible at
the moment?
No, that was more related to the UI elements and all the formating.
Maybe everthing is possible.
What extensions are planned, is it likely that these things
become possible?
I ask because I have a bunch of ideas of new
features/modules for workflow speed-up that would perfectly suit the
idea of Lua integration, all of them being little helpers of low
complexity. And I am willing to work on their realization, but without
a
profound programming/informatics background I will need some answers
from time to time.
As you might have concluded the idea behind the module I asked this
question for is a speed-tagging interface, e.g. to tag peoples names on
subsequent images - press a for people|family|adam, r for
people|friends|rose, u for people|unknown etc. E.g., a wedding
photographer could use this to tag the bridal pair and their relatives
extremely fast. A portrait photographer could tag poses etc. For me it
is mainly intended for tagging friends and family in my private photos.
In the module, tags are defined and keyboard shortcuts are assigned and
if activated, these shortcuts temporarily overwrite the general ones. A
special shortcut is assigned for “use tags from last picture” and all
shortcuts work in toggle mode. Sets of tags can be stored with the
preset infrastructure (not yet available from Lua) or another mechanism
to save them for later use. The number of tags in the set can be set in
a wide range, e.g. from 1 to 26.
Such a modul will be really helpful for me too, therefore I responded to
your mail.
Currently I only have two lua scripts in use . With [0] I can copy tags
around by shortcuts. Maybe I should add UI elements for that.
The second one [1] copy over tags to IPTC or can remove metadata using
the exiftool on export. Both scripts make there job, but I don't know if
they are coded well.
Coming to your speed-tagging ideas:
1.) shortcuts
ATM I can't imagine how shortcuts can be assigned via moduls. I'm not
aware of any place in darktable expect the references dialog where
shortcuts can be defined. Of course with lua you can add shortcuts to
the preferences dialog. So maybe there is by design no lua UI element
for shortcuts? There is a config file "keyboardrc" and with the in- and
output facilities of lua someone could mess around. But I think this
will bring you in hell's kitchen.
2.) “use tags from last picture”
I usually tag several images at once. So what is the last picture if I
use "darktable.gui.action_images".
3.) shortcuts temporarily overwrite the general ones
A good question how shortcuts are handled now, because if you assign a
shortcut which is already in use this one will be removed from the old
position.
Generally I would not start with UI elements, because you can add them
later on. Instead I would add shortcuts first, make the number of them
flexible, (use io of lua to save "presets" in a file) and if possible
push them to github* [2].
Christian
*git - another dragon I'm fighting against ;-)
That's only one of some ideas I have that would be ideal for Lua
realization if the infrastructure is available. Especially, since my C
knowledge is below zero ;-) and the additions may not be for everybody.
Other ideas I had are a 2nd instance of the collect module that works
with predefined (user-defined) selection criteria which can be toggled
on and off by buttons and don't mess up the “recently used
collections”.
These would be effective only for the current collection. Things as
“all
processed but not yet exported images”, “all images with red or yellow
but not green labels” which means for me all unprocessed or partially
processed images. Another idea would be a statistics module which
counts
criteria as number of colour labelled images or images with certain
tags
in the current collection, e.g. 28 red, 7 yellow, 15 green, which would
mean for me that I have a lot of work ahead. As you can see, I have
some
ideas that make sense at least for me and now I want to work on their
realization, but I am not able to assess if this is already feasible.
Thanks for your answer and best regards
Chris
[0]
https://github.com/darktable-org/lua-scripts/blob/master/contrib/copy_attach_detach_tags.lua
[1]
https://github.com/chrik5/lua-scripts/blob/exiftool/contrib/exiftool_export.lua
[2] https://github.com/darktable-org/lua-scripts
___________________________________________________________________________
darktable developer mailing list
to unsubscribe send a mail to [email protected]
