[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:52 p.m., Dan Vrátil wrote:
> > agents/migration/migrationscheduler.cpp, line 263
> > <http://git.reviewboard.kde.org/r/112636/diff/1/?file=188603#file188603line263>
> >
> >     You should make sure the migrator is not already to prevent accidentally starting it twice.
> 
> Dan Vrátil wrote:
>     *not already running

That's already ensured by ensuring the same migrator cannot be added twice to the model and by having MigratorBase ensuring that the migrator cannot be started twice. Right?


> On Sept. 10, 2013, 5:52 p.m., Dan Vrátil wrote:
> > agents/migration/migrationstatuswidget.cpp, line 97
> > <http://git.reviewboard.kde.org/r/112636/diff/1/?file=188605#file188605line97>
> >
> >     Wouldn't just KTextView (or smthing like that) better than a listview? In case of a bug we will want users to copy content of the log to bugzilla, and it's hard to copy stuff from a listview :)

It's definitely a good point =) I'll see that it's somehow copyable.
Note that we also have a logfile from Migratorbase though.


- Christian


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


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/