On Monday, October 22, 2012 09:57:51 Jaroslaw Staniek wrote: ...
> That's good approach, especially the separation of painting routines > from the headless part. No, I don't advocate separation of painting from the headless part. Paiting should be in the core. > Regarding the above hierarchy with ui/* dirs -- where would be the > place for app-specific code that's not ui-related? in core/<app>, of course. > Moreover, > > In mid term (3.0), following the approach of Qt 5, I wonder if we > couldn't have the libs: > - moved to separate repo(s) > - changed to Qt-only (most easy for filters - gives hope of getting > more contributors from Qt-only ecosystem). > > (I've been dreaming about this during the 1st Calligra sprint) I wouldn't mind this very much if we could just get a stable API. That means that probably not all libs would apply. But I think that for instance libs/odf was always meant to be stand-alone. What type of non-Qt dependency do we have now that would be done away with? _______________________________________________ calligra-devel mailing list calligra-devel@kde.org https://mail.kde.org/mailman/listinfo/calligra-devel
