On 19 February 2013 22:19, Friedrich W. H. Kossebau <kosse...@kde.org> wrote: > Am Dienstag, 19. Februar 2013, 22:07:46 schrieb Inge Wallin: >> Well... not really. Since Plasma Active is a viewer only only the import >> filters make sense. ...which suggests another build option: VIEWER. > > But isn't the plan to make it also an editor in the end? If not, where is the > difference to OkularActive or whatever other reader there is for PlasmaActive? > > Sure, for now ACTIVE_ONLY would limit to import filters, given the needs.
Our selling point is modularity, yet the deployment could be improved in some aspects. It would be great to get there also by providing (yes) kernel-like detailed build options, something not present in competing projects. Qt Project is also quite modular if we need examples. Enabling VIEWER profile is one of our advantages. Another one apart form single-app-only profiles is: a build without pigment (they are unusable for most Kexi users). For me TINY is somewhat close to what ultimately be called MINIMAL and as such it makes sense as generic template for people playing with their own GUIs. But here I am unsure since one day the extended Calligra Engine could provide 'modularized office application development frameworks'. PS: I am OK with all the proposals regarding making Author the full app in the hierarchy. -- regards / pozdrawiam, Jaroslaw Staniek Kexi & Calligra & KDE | http://calligra.org/kexi | http://kde.org Qt Certified Specialist | http://qt-project.org http://www.linkedin.com/in/jstaniek _______________________________________________ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel
