[Kde-pim] Review Request 112636: Migration agent that schedules various migrators and exposes an interface for status and control.

[Christian Mollekopf]

> On Sept. 10, 2013, 5:22 p.m., Kevin Krammer wrote:
> > I generally like the idea a lot. I had originally started with an agent for mail import to replace the old migrator but then Laurent created an importer tool way faster :)
> > 
> > One thing I had considered was to do the pause/resume/progress UI through jobs, e.g. like KIO jobs.
> > Has the advantage of also working in a Plasma Active scenario.
> > 
> > Import is a slightly different scenario though because it is initiated by the user (much like file copying), so starting the import and seeing the progress appear for a short time allows to make the mental connection between the two things.
> >

Can you elaborate a bit on the jobs <=> UI relation. I'm kinda KIO agnostic ;-)
I thought about simply exposing a dbus interface from the agent to allow applications (e.g. a plasmoid) to show progress information and possibly trigger the pause/resume actions. I suppose some kind of tray icon would be useful (there was an akonaditry at some point, wasn't there?). Although it would be kinda cool to merge it with the one from nepomuk (background services).


- Christian


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/112636/#review39744
-----------------------------------------------------------


On Sept. 10, 2013, 1:17 p.m., Christian Mollekopf wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> http://git.reviewboard.kde.org/r/112636/
> -----------------------------------------------------------
> 
> (Updated Sept. 10, 2013, 1:17 p.m.)
> 
> 
> Review request for KDEPIM.
> 
> 
> Description
> -------
> 
> Migration agent that schedules various migrators and exposes an interface for status and control.
> 
> This does not yet include a plugin interface for making plugging in new migrators plugin based. That would be easy enough to add but only makes sense if we push the MigratorBase interface to kdepimlibs along with a dbus control interface, so i.e. applications such as kmail can install new migration plugins and control them via the dbus interface.
> 
> The agent automatically starts migration jobs that have shouldAutostart() enabled and exposes an interface in it's configuration dialog to start/stop migrators. The interface is yet very basic and is also no necessarily in the most convenient place. We should likely have some central place for controlling background processes or simply ensure the automatic processing is handled well enough.
> 
> Ideas how to do that best are appreciated.
> 
> 
> Diffs
> -----
> 
>   agents/CMakeLists.txt 22b6db73687f82c9d05a19c63708be32b6508513 
>   agents/migration/CMakeLists.txt PRE-CREATION 
>   agents/migration/migrationagent.cpp PRE-CREATION 
>   agents/migration/migrationagent.desktop PRE-CREATION 
>   agents/migration/migrationagent.h PRE-CREATION 
>   agents/migration/migrationscheduler.h PRE-CREATION 
>   agents/migration/migrationscheduler.cpp PRE-CREATION 
>   agents/migration/migrationstatuswidget.h PRE-CREATION 
>   agents/migration/migrationstatuswidget.cpp PRE-CREATION 
>   agents/migration/tests/CMakeLists.txt PRE-CREATION 
>   agents/migration/tests/schedulertest.cpp PRE-CREATION 
> 
> Diff: http://git.reviewboard.kde.org/r/112636/diff/
> 
> 
> Testing
> -------
> 
> I tried the GID migration for contacts, which worked fine for me.
> 
> 
> Thanks,
> 
> Christian Mollekopf
> 
>

_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/