Am Mittwoch, 9. April 2014, 09:32:58 schrieb Kevin:
> On Tue, 8 Apr 2014 13:32:00 Tobias Ellinghaus wrote:
> > Am Dienstag, 8. April 2014, 14:38:21 schrieb Kevin:
> >
> > [..]
> >
> > I didn't have time to look at your patch, but if you want to have a chance
> > of seeing this included you have t
On Tue, 8 Apr 2014 13:32:00 Tobias Ellinghaus wrote:
> Am Dienstag, 8. April 2014, 14:38:21 schrieb Kevin:
>
> [..]
>
> I didn't have time to look at your patch, but if you want to have a chance
> of seeing this included you have to remove
>
> > -i|--input
> >
Am Dienstag, 8. April 2014, 14:38:21 schrieb Kevin:
[..]
I didn't have time to look at your patch, but if you want to have a chance of
seeing this included you have to remove
> -i|--input
> -o|--output
> [-x|--xmp ]
and go back
On 07/04/14 23:10, Tobias Ellinghaus wrote:
Hi!
[...]
>>> would go away, too. That is all just slow and bloat. That tool isn't
>>> meant to be a remote control of darktable (using --core --library
>>> ~/.config/darktable/library.db you could even import images from the
>>> command line without ha
On Thu, 3 Apr 2014 14:27:47 Torsten Bronger wrote:
> Hallöchen!
>
> Thank you! As a DT_CLI user, I appreciate this. How difficult is
> it to add all other options of DT's "export" module to the CLI?
> Since the "export" module parameters cannot be in the XMP file, this
> is highly practical I t
On Mon, 7 Apr 2014 23:10:03 Tobias Ellinghaus wrote:
> Am Montag, 7. April 2014, 20:48:35 schrieb Alexander Wagner:
> > On 07/04/14 14:55, Tobias Ellinghaus wrote:
> >
> > Hi!
> >
> > >> I can understand why it may be undesirable to have, perhaps multiple
> > >> instances of, the cli concurrently
Am Montag, 7. April 2014, 20:48:35 schrieb Alexander Wagner:
> On 07/04/14 14:55, Tobias Ellinghaus wrote:
>
> Hi!
>
> >> I can understand why it may be undesirable to have, perhaps multiple
> >> instances of, the cli concurrently accessing the database when the gui
> >> may
> >> be active - if t
On 07/04/14 14:55, Tobias Ellinghaus wrote:
Hi!
>> I can understand why it may be undesirable to have, perhaps multiple
>> instances of, the cli concurrently accessing the database when the gui may
>> be active - if the cli updates the database..
>>
>> Does the cli need update access to the db?
>
Am Freitag, 4. April 2014, 15:04:02 schrieb Kevin:
> I tried to do a "proof of concept" implementation of a "--style" option -
> but failed due to database issues.
>
> It appears that the cli does not use the dt database and so things like
> styles are not available.
>
> Can someone with more kno
On 7 April 2014 3:56:57 pm AEST, Torsten Bronger
wrote:
>Hallöchen!.
>
>Wow, that was quick. Thank you! If it is merged,
>http://darktable.org/redmine/issues/9881 can be closed.
If others are equally positive, I suggest waiting until I can include the
file-type options like, e.g., --jpg- qu
Hallöchen!
Kevin writes:
> On Thu, 3 Apr 2014 14:27:47 Torsten Bronger wrote:
>
>> Thank you! As a DT_CLI user, I appreciate this. How difficult
>> is it to add all other options of DT's "export" module to the
>> CLI? Since the "export" module parameters cannot be in the XMP
>> file, this is h
On Mon, 7 Apr 2014 06:49:48 Alexander Wagner wrote:
> Due to this it might be helpful to allow some --db parameter, which
> allows to specify a database to use.
This can be done, as was pointed out to me by Pedro, by
--core --library
Kevin
On 07/04/14 06:15, Kevin wrote:
Hi!
>> Thank you! As a DT_CLI user, I appreciate this. How difficult is
>> it to add all other options of DT's "export" module to the CLI?
>> Since the "export" module parameters cannot be in the XMP file, this
>> is highly practical I think.
>>
> I've done some
On Thu, 3 Apr 2014 14:27:47 Torsten Bronger wrote:
> Hallöchen!
>
> Thank you! As a DT_CLI user, I appreciate this. How difficult is
> it to add all other options of DT's "export" module to the CLI?
> Since the "export" module parameters cannot be in the XMP file, this
> is highly practical I th
Thanks, that's something I didn't think of.
But is this a "good idea"? Why doesn't cli use the database by default?
Kevin
-- Forwarded Message --
Subject: Re: [darktable-devel] darktable-cli - various fixes and extensions
Date: Fri, 4 Apr 2014, 10:44:
I tried to do a "proof of concept" implementation of a "--style" option - but
failed due to database issues.
It appears that the cli does not use the dt database and so things like styles
are not available.
Can someone with more knowledge of the system confirm this?
I can understand why it may
On Thu, 3 Apr 2014 10:45:44 johannes hanika wrote:
> nice, thanks for looking into that x server issue.
Your welcome, but self interest played a major part in my motivation.
> a couple of comments:
>
> this hunk looks like it doesn't change anything to me:
>
> - disk_t *g = (disk_t *)self->gui
Hallöchen!
Kevin writes:
> [...]
>
> 2) cli_overwrite - This branch extends the cli_fix branch by
> adding a "-- overwrite" option. The current version from the
> "master" branch renames the output file, if necessary. If this
> option is specified, it is the same as checking the corresponding
> c
nice, thanks for looking into that x server issue. a couple of comments:
this hunk looks like it doesn't change anything to me:
- disk_t *g = (disk_t *)self->gui_data;
+ disk_t *g = NULL;
+ // dirty hack to make the cli work
+ if (self->gui_data)
+g = (disk_t *)self->gui_data;
and your s
Attached is a tar file containing two "git diff" files. They have been
generated
from two local branches each of which address issues with the cli facility.
1) cli_fix - This branch addresses the following issues:
* Bug 9473: http://darktable.org/redmine/issues/9473
* Unreported bugs where
20 matches
Mail list logo
