Talking about New tools to export contents to web service.

[Gilles Caulier-4]

Hi all,

I'm back in this room (now free of bugzilla notifications (:=))), to
talk about the plan to create new tools in digiKam core (not as
kipi-plugins), about to export and also import files from web service.

As i can see in bugzilla, step by step, all remote web service will
use Oauth2 authentification method. All kipi tools will be broken in
the future.

It's time now to prepare the future. As you must know, i want to port
digiKam as a pure Qt5 application for the long time. This want mean :

1/ remove the plugins interface :

- startup more fast.
- less run time dependencies (as for ex plugins not found).
- better portability.
- less KF5 dependencies again (as a goal to drop KXMLGUI and KConfig everywhere.
- Tools available everywhere : Album View, Image Editor, Light Table,
and Showfoto.

2/ Create new API to declare export tools with these features :

- Copy from local to remote computer.
- List remote tree-view and select destination.
- Be able to change file properties as size, format, metadata, etc.
- Be authenticated automatically, without to use an external web
browser instance.
- Store account locally to prevent re-authentication.

3/ Create new API to declare import tools with these features :

- Copy from remote computer to local.
- List locale tree-view and select destination.
- Be able to change file properties as size, format, metadata, etc.
- Be authenticated automatically, without to use an external web
browser instance.
- Store account locally to prevent re-authentication.

Note: not all import and export web service has the same features.
This must be configurable in implementations.

4/ Create a GUI to dialog with end users. 2 possibilities :

- make a single GUI (as image editor, LT, BQM) to host tools.The web
service selection can be done through a combobox and the rest of GUI
will be adjusted accordingly with declared features.

- make an generic assistant which will ask task to achieve and provide
the relevant options step by step.

There is not yet a mock-up, i'm waiting more feedback before.

Voilà. I'm waiting your constructive messages.

Best

Gilles Caulier

[Maik Qualmann]

I agree with all the ideas. All web services should be combined in one GUI.

Maik

Am Dienstag, 8. August 2017, 11:00:32 CEST schrieb Gilles Caulier:

> Hi all,
>
> I'm back in this room (now free of bugzilla notifications (:=))), to
> talk about the plan to create new tools in digiKam core (not as
> kipi-plugins), about to export and also import files from web service.
>
> As i can see in bugzilla, step by step, all remote web service will
> use Oauth2 authentification method. All kipi tools will be broken in
> the future.
>
> It's time now to prepare the future. As you must know, i want to port
> digiKam as a pure Qt5 application for the long time. This want mean :
>
> 1/ remove the plugins interface :
>
> - startup more fast.
> - less run time dependencies (as for ex plugins not found).
> - better portability.
> - less KF5 dependencies again (as a goal to drop KXMLGUI and KConfig
> everywhere. - Tools available everywhere : Album View, Image Editor, Light
> Table, and Showfoto.
>
> 2/ Create new API to declare export tools with these features :
>
> - Copy from local to remote computer.
> - List remote tree-view and select destination.
> - Be able to change file properties as size, format, metadata, etc.
> - Be authenticated automatically, without to use an external web
> browser instance.
> - Store account locally to prevent re-authentication.
>
> 3/ Create new API to declare import tools with these features :
>
> - Copy from remote computer to local.
> - List locale tree-view and select destination.
> - Be able to change file properties as size, format, metadata, etc.
> - Be authenticated automatically, without to use an external web
> browser instance.
> - Store account locally to prevent re-authentication.
>
> Note: not all import and export web service has the same features.
> This must be configurable in implementations.
>
> 4/ Create a GUI to dialog with end users. 2 possibilities :
>
> - make a single GUI (as image editor, LT, BQM) to host tools.The web
> service selection can be done through a combobox and the rest of GUI
> will be adjusted accordingly with declared features.
>
> - make an generic assistant which will ask task to achieve and provide
> the relevant options step by step.
>
> There is not yet a mock-up, i'm waiting more feedback before.
>
> Voilà. I'm waiting your constructive messages.
>
> Best
>
> Gilles Caulier

--
Gruß Maik