Batch Queue Manager

classic Classic list List threaded Threaded
29 messages Options
12
Reply | Threaded
Open this post in threaded view
|

Re: Batch Queue Manager

Gilles Caulier-4
2013/11/17 Yuri Samoilenko <[hidden email]>:

> Hello.
>
> 2013/11/16 Gilles Caulier <[hidden email]>
>>
>> 1. ...This option must go in "External Tools" ...
>
>
> ok
>
>
>> 2. "External Tools" settings view is not the right name. Action
>>
>> performed by this view will be processed at end of queue. So for me
>> the term is not enough explicit for end users. I'm sure that nobody
>> will understand as well the purpose of this view. This is why it must
>> be renamed, and some tips must be written in a label in this view to
>> explain what's end users can do with it.
>
>
> I will glad to rename 'external tools', but I have a trouble with new
> name... If I undestood right you suggested to rename it to "External View"?
> When I selects the name I was inspired by Kate plugin "external tools", you
> can look at it in couple of first images:
> https://www.google.ru/search?q=kate+external+tools&newwindow=1&source=lnms&tbm=isch&sa=X&ei=hm2IUqWhIKaK4AS2mIDIAg&ved=0CAkQ_AUoAQ&biw=1866&bih=1038&dpr=0.9#facrc=_&imgdii=_&imgrc=vSs6YDHs_uZJQM%3A%3B7jElwIRntJX6AM%3Bhttp%253A%252F%252Fwww.tuxmachines.org%252Fimages%252Fgfkate%252Fkate2.png%3Bhttp%253A%252F%252Fwww.tuxmachines.org%252Fnode%252F13762%3B888%3B691

If you let "external Tools", user can ask why this option do not exist
for each item, as BQM tools...

BQM tools are DImg based to process image.
External tools are to process all files after queue processing.

So a new name must be found, as "Post-processing Tools" for example.


>
>
>> 3. ... The program, can be a binary or a script. In
>>
>> this view you force to use a script, by default as bash. And what's
>> about Windows where Batch shell script are used. In other words, you
>> need to write a GUI more universal where these information must be
>> show :
>>
>> - the path to the Program
>> - the name of the Program
>> - the description of the Program
>> - the arguments to pass to the Program.
>
>
> ok
>
>
>> ... Because, if i'm not to
>>
>> wrong, scripts will be hosted as external file in home directory.
>> Right ?...
>
>
> Some times it is too complex to host very simple script outside of 'usage
> point'. I think when I implement previous feature we will return to this :)
>
>
>  4. In your GUI, i recommend to propose a list of Programs available
>>
>> and ready to use. User will assign one Program to the queue, and that
>> all. The list can be stored in workflow XML file. Look how i do with
>> workflow list view (workflow name + description are displayed)...
>
>
> I can't understand... GUI already have a combobox to select a name from
> available items...

Perhaps i have not the last commit from you in dedicated branch.
Anyway, look my other mail about in this thread, especially about to
plug a new page in Setup dialog to host "external tools settings"

>
>>> What's the purpose of "Show in Context Menu" option ? Which menu is
>>> patched by your implementation ?
>
> The 'Edit' menu, near 'rename', and the DigikamImageView context menu, near
> 'rename'. I have done an ugly hack to get contexmenu updated from my GUI - I
> need help/explanation with right sollution.
> I think 'Show in Context Menu' is good feature - user can create custom
> postprocessing action and assign in to shortcut(Ctrl+Alt+A to archive all
> selected files).
>

Idem here. See my other mail about in this thread.

Gilles
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

Re: Batch Queue Manager

Gilles Caulier-4
Any progress here ?

Gilles Caulier

2013/11/17 Gilles Caulier <[hidden email]>:

> 2013/11/17 Yuri Samoilenko <[hidden email]>:
>> Hello.
>>
>> 2013/11/16 Gilles Caulier <[hidden email]>
>>>
>>> 1. ...This option must go in "External Tools" ...
>>
>>
>> ok
>>
>>
>>> 2. "External Tools" settings view is not the right name. Action
>>>
>>> performed by this view will be processed at end of queue. So for me
>>> the term is not enough explicit for end users. I'm sure that nobody
>>> will understand as well the purpose of this view. This is why it must
>>> be renamed, and some tips must be written in a label in this view to
>>> explain what's end users can do with it.
>>
>>
>> I will glad to rename 'external tools', but I have a trouble with new
>> name... If I undestood right you suggested to rename it to "External View"?
>> When I selects the name I was inspired by Kate plugin "external tools", you
>> can look at it in couple of first images:
>> https://www.google.ru/search?q=kate+external+tools&newwindow=1&source=lnms&tbm=isch&sa=X&ei=hm2IUqWhIKaK4AS2mIDIAg&ved=0CAkQ_AUoAQ&biw=1866&bih=1038&dpr=0.9#facrc=_&imgdii=_&imgrc=vSs6YDHs_uZJQM%3A%3B7jElwIRntJX6AM%3Bhttp%253A%252F%252Fwww.tuxmachines.org%252Fimages%252Fgfkate%252Fkate2.png%3Bhttp%253A%252F%252Fwww.tuxmachines.org%252Fnode%252F13762%3B888%3B691
>
> If you let "external Tools", user can ask why this option do not exist
> for each item, as BQM tools...
>
> BQM tools are DImg based to process image.
> External tools are to process all files after queue processing.
>
> So a new name must be found, as "Post-processing Tools" for example.
>
>
>>
>>
>>> 3. ... The program, can be a binary or a script. In
>>>
>>> this view you force to use a script, by default as bash. And what's
>>> about Windows where Batch shell script are used. In other words, you
>>> need to write a GUI more universal where these information must be
>>> show :
>>>
>>> - the path to the Program
>>> - the name of the Program
>>> - the description of the Program
>>> - the arguments to pass to the Program.
>>
>>
>> ok
>>
>>
>>> ... Because, if i'm not to
>>>
>>> wrong, scripts will be hosted as external file in home directory.
>>> Right ?...
>>
>>
>> Some times it is too complex to host very simple script outside of 'usage
>> point'. I think when I implement previous feature we will return to this :)
>>
>>
>>  4. In your GUI, i recommend to propose a list of Programs available
>>>
>>> and ready to use. User will assign one Program to the queue, and that
>>> all. The list can be stored in workflow XML file. Look how i do with
>>> workflow list view (workflow name + description are displayed)...
>>
>>
>> I can't understand... GUI already have a combobox to select a name from
>> available items...
>
> Perhaps i have not the last commit from you in dedicated branch.
> Anyway, look my other mail about in this thread, especially about to
> plug a new page in Setup dialog to host "external tools settings"
>
>>
>>>> What's the purpose of "Show in Context Menu" option ? Which menu is
>>>> patched by your implementation ?
>>
>> The 'Edit' menu, near 'rename', and the DigikamImageView context menu, near
>> 'rename'. I have done an ugly hack to get contexmenu updated from my GUI - I
>> need help/explanation with right sollution.
>> I think 'Show in Context Menu' is good feature - user can create custom
>> postprocessing action and assign in to shortcut(Ctrl+Alt+A to archive all
>> selected files).
>>
>
> Idem here. See my other mail about in this thread.
>
> Gilles
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

Re: Batch Queue Manager

kinnalru@gmail.com
I have made some work to hadle with diffrent types of external tools(like executable, script etc), but now I'am very limited in time(untill holiday) and can't make code working.  I hope to accomplish this part of work friday evening.


2013/11/20 Gilles Caulier <[hidden email]>
Any progress here ?

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

Re: Batch Queue Manager

Gilles Caulier-4
Ok, fine...

Gilles Caulier

2013/11/20 Yuri Samoilenko <[hidden email]>:

> I have made some work to hadle with diffrent types of external tools(like
> executable, script etc), but now I'am very limited in time(untill holiday)
> and can't make code working.  I hope to accomplish this part of work friday
> evening.
>
>
> 2013/11/20 Gilles Caulier <[hidden email]>
>>
>> Any progress here ?
>
>
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel
>
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

Re: Batch Queue Manager

kinnalru@gmail.com
In reply to this post by Gilles Caulier-4
Hello.
I have made some improvements in External Tools(not renamed yet), and I have some ideas to discuss.

1. I have made an ugly hack to allow shortcut management of ET from ET settings, and I don't know how to deal with it. Can anybody help me or give explanation in this task?

2. ET settings moved to own tab in BMQ settings, and when we think about ET as of process made after all other filters, than renaming tab to "Post processing" is good idea. But We can think about ET as possibility to "put processed images to somewhere after processing" and than we can call it as "Destination" or "Target". For example Target of proccessed images is new album(as by now), or/and Target of proccessed items is remote drive/archive, or/and Target is External Tool. What you think about it? 

3. ET from BMQ(maybe Post Processing through External Tool) is differs(by meaning) from ET calling from main application window, when I can select multimple images and process them through script to make archive or somthing else. And I think that "External Tools" is most appropriate name of this action, especially when I can designate hot key for quick processing. 

4. Theoretically ET can have special mode(enabled through checkbox) when executing tool can print to stdout names of converted/newly created items. This output can be captured by Digikam(ETRunner) and placed to album, through "Target" settings for example. What you think about it?





_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

Re: Batch Queue Manager

kinnalru@gmail.com

Hello?


_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

Re: Batch Queue Manager

Gilles Caulier-4
Yes Yuri, i seen your message.

I will respond today. (i have been very busy until now...sorry...)

Gilles Caulier

2013/11/28 Yuri Samoilenko <[hidden email]>:
> Hello?
>
>
> _______________________________________________
> Digikam-devel mailing list
> [hidden email]
> https://mail.kde.org/mailman/listinfo/digikam-devel
>
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

Re: Batch Queue Manager

Gilles Caulier-4
In reply to this post by kinnalru@gmail.com
2013/11/22 Yuri Samoilenko <[hidden email]>:
> Hello.
> I have made some improvements in External Tools(not renamed yet), and I have
> some ideas to discuss.
>
> 1. I have made an ugly hack to allow shortcut management of ET from ET
> settings, and I don't know how to deal with it. Can anybody help me or give
> explanation in this task?

What do you want to perform with shortcuts management ?

I recommend to hack BQM code first, you will see extra feature later.

>
> 2. ET settings moved to own tab in BMQ settings, and when we think about ET
> as of process made after all other filters, than renaming tab to "Post
> processing" is good idea. But We can think about ET as possibility to "put
> processed images to somewhere after processing" and than we can call it as
> "Destination" or "Target". For example Target of proccessed images is new
> album(as by now), or/and Target of proccessed items is remote drive/archive,
> or/and Target is External Tool. What you think about it?

well, the settings to put processed items in queue _and_ by ET must be
hosted in target set by end user in existing settings. Do not add more
target settings, it will be difficult to understand by end users.

>
> 3. ET from BMQ(maybe Post Processing through External Tool) is differs(by
> meaning) from ET calling from main application window, when I can select
> multimple images and process them through script to make archive or somthing
> else. And I think that "External Tools" is most appropriate name of this
> action, especially when I can designate hot key for quick processing.

But we talk about BQM her, not album GUI (:=)))... Why do you want to
mix both. Just concentrate your effort on BQM for the moment...

>
> 4. Theoretically ET can have special mode(enabled through checkbox) when
> executing tool can print to stdout names of converted/newly created items.
> This output can be captured by Digikam(ETRunner) and placed to album,
> through "Target" settings for example. What you think about it?
>
>

In this case you will not follow renaming rules from BQM settings... I think.

Gilles Caulier
_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
Reply | Threaded
Open this post in threaded view
|

Re: Batch Queue Manager

kinnalru@gmail.com
Good evening.

What do you want to perform with shortcuts management ?
 
Designate/clear shortcut from ET config widget and this shortcut must be instantly enabled/disabled and added/removed from menu.

I recommend to hack BQM code first, you will see extra feature later.

Ok. Later.
 
> 2. ET settings moved to own tab in BMQ settings, and when we think about ET
> as of process made after all other filters, than renaming tab to "Post
> processing" is good idea. But We can think about ET as possibility to "put
> processed images to somewhere after processing" and than we can call it as
> "Destination" or "Target". For example Target of proccessed images is new
> album(as by now), or/and Target of proccessed items is remote drive/archive,
> or/and Target is External Tool. What you think about it?

well, the settings to put processed items in queue _and_ by ET must be
hosted in target set by end user in existing settings. Do not add more
target settings, it will be difficult to understand by end users.

I can't understand because I can't translate this sentence sorry. 
 
> 3. ET from BMQ(maybe Post Processing through External Tool) is differs(by
> meaning) from ET calling from main application window, when I can select
> multimple images and process them through script to make archive or somthing
> else. And I think that "External Tools" is most appropriate name of this
> action, especially when I can designate hot key for quick processing.

But we talk about BQM her, not album GUI (:=)))... Why do you want to
mix both. Just concentrate your effort on BQM for the moment...

Ok. I will not mix. 
 

_______________________________________________
Digikam-devel mailing list
[hidden email]
https://mail.kde.org/mailman/listinfo/digikam-devel
12