Calligra 3.0 for Qt 5.1?

[Dmitry Kazakov]

> Yes, that's an important consideration. If we could get master release
> stable for Qt 5.1 in a month or two, I would argue that we should try that
> -- make the period of pain as short as possible. But given the amount of
> unmaintained and barely maintained code we have to drag along, I doubt that
> that's feasible.
>

Yep, that is true :(


>  Especially for the ones that use dbus. Currently, as far as I can tell,
> dbus offers the following functionality for Calligra:
>
> * check whether an autosave document belongs to another open instance of
> an application
>

Btw, do the File Layers in Krita check that the file is changed on disk? Do
they use some KIO thing for that?


> kio has another problem, besides dbus and the multi-process model, and
> that is it's tight coupling to QWidget -- if the functionality kio gives us
> that users are really using can be simply implemented with a few lines of
> code, then I would prefer that. D&D from firefox probably is easy to
> replace, and I really wonder how many users are loading documents using the
> ftp, fish or http kioslaves on a regular basis.
>

Well, the problem is that you needn't D&D a http-based URL for that. You
just drag an *image* and it is passed as an URL. Chromium works a bit
differently and it passes an image as a real image, which is handled
without KIO.

-- 
Dmitry Kazakov
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/calligra-devel/attachments/20130729/09d7b35d/attachment.htm>