That sounds more like a dedicated page on TechBase is needed. I can rephrase the part about Engine to something like "Calligra Engine is in the process of becoming ... check techbase.kde.org/... for more detailed info".
Markus On Mittwoch 07 Dezember 2011 21:46:11 Jaroslaw Staniek wrote: > I think we may want to work more on specifying what Calligra Engine > is, what it will be in one year and maybe later. In the current text > it looks like the Engine is formed by libs sitting above Qt and KDE > frameworks > and below Calligra Apps. But in fact only selected, incrementally more and > more libs would provided with a public API for the 3rd-party apps. For > now it's a > pilot effort for early adopters and naturally because it's all pilot > it has to be supported by > Calligra developers like devs from KO GmbH who support companies that > adopt Calligra technologies in their products. > In this light, I understand that we define what Calligra Engine is, > step by step, without declaring all the goodness as final frameworks > too early. > > We even had some discussions on the topic on the Sprint #1 where we > noticed the Engine can support more than one aspect related to Office > Suites. I think so far we could explain one or two aspects that can work > for certain cases; e.g. 1. > filters API for headless import/export, 2. (QWidget) GUI abstraction > for creating custom applications. Both things are already available. > There's a of course lot of progress in ODF documents > generation/modification framework for C++. I hope later it would be > extended by an equivalent for QtScript. > > Thank you for your contribution, Markus. _______________________________________________ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel
