On Saturday 04 January 2014 19:40:46 Christoph Cullmann wrote: > > On Saturday 04 January 2014 19:18:56 Christoph Cullmann wrote: > > > Hi, > > > > > > I cleanup the frameworks branch in kate.git to only have libktexteditor > > > lib > > > and the KTextEditor/ktexteditor includes to be installed as public API. > > > > > > Now, for 5.x, if others port over, like KDevelop, is it a good idea to > > > keep > > > the ktexteditor parts in kate.git, together with the applications, or > > > shall > > > that be split again into a khtml like framework? > > > > We want to make separate releases of the 3 major products: > > frameworks, apps and workspace. > > > > So libs that are used by workspace and apps, should be in frameworks. > > For libs that are only used by apps .... I guess they can either be in > > apps > > or > > in frameworks. > > > > So IMHO the question is: is there a chance the KDE workspace will need it? > > > > Of course the other question is: do you want to make it available as a > > framework for non-KDE developers to use in Qt applications? > > > > If the answer is yes to either of these questions, then you need to split > > it out into a framework. > > I am not sure if workspace apps will require it, but I doubt it, given an > plain text editor is nothing the average application needs, guess only > stuff like KDevelop/Kile/... will depend on it. I think it gets used in workspace. Try KRunner and enter "desktop console". Though I don't know what it uses in the implementation and that code is not yet ported.
Cheers Martin
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Kde-frameworks-devel mailing list Kde-frameworks-devel@kde.org https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
