Roadmap to Calligra Mini

[Jaroslaw Staniek]

On 17 June 2013 21:11, Sebastian Sauer <mail at dipe.org> wrote:

> Yep, Calligra Active was even the starting point when I begun that. I
> switched away when going full threaded cause that was requiring a complete
> different architecture and design. In Coffice all of Calligra runs in
> another thread then the UI/QML. That means all operations are asynchronous
> in Coffice unlike in Active and Calligra will never be able to block the UI.
> Also I bundle all plugins into one plugin, all filters into one filter and
> delay loading in Coffice plus don't use KDE plugin-lookup (aka sycoca) cause
> sycoca isn't present, I rewrote the kde factory/plugin/kpart stuff, etc. pp.

Please correct me, arent all these features are not irrelevant to
whether the app's UI is QWidget-based or QML-based?

> Since all that happened Qt5 progressed and meanwhile (means not so long ago)
> work on scenegraph-based QTextDocument/QTextEdit landed. So, for Qt5 there
> may an option (with very likely lots of additional work needed for our
> use-cases) to solve the no-go all-in-one-thread problem at another level. On
> the other hand there would still be work needed to get potential
> long-blocking operations like loading threaded which is all solved in
> Coffice as of today already.... Well, we will see.

All the features are beneficial for Active and would land there too
eventually, right?

Thanks for all this effort, Shantanu and Sebastian!

-- 
regards / pozdrawiam, Jaroslaw Staniek
 Kexi & Calligra & KDE | http://calligra.org/kexi | http://kde.org
 Qt for Tizen | http://qt-project.org/wiki/Tizen
 Qt Certified Specialist | http://www.linkedin.com/in/jstaniek