a new library

[C. Boemann]

On Wednesday 19 December 2012 10:03:24 Boudewijn Rempt wrote:
> On Wednesday 19 December 2012 Dec, C. Boemann wrote:
> > Hi
> > 
> > In an attempt to to rework the ui, we have run into a problem:
> > 
> > KoCreatePathTool in libs/flake needs some widgets from libs/widgets
> > 
> > however the dependency is in the opposite direction
> > 
> > So unless we want to move the tools into libs/widgets we need to move the
> > tool to somewhere else.
> > 
> > It can't be moved to a plugin as krita has some tools that inherit from
> > KoCreatePathTool.
> > 
> > My suggestion is thus that we make a new library, which I call alpine as
> > it's a superstructure to flake. This alpine library will depend on
> > libs/widgets and contain basically tools, shapes and dockers that are
> > too important or generic enough that we can't have them in plugins but
> > need to be sure is available.
> > 
> > For now it would only contain the KoCreatePathTool but in the past I've
> > thought that maybe the textshape needs to be in a library instead of a
> > plugin.
> > 
> > So what do you say?
> 
> I'm fine with that -- in fact, I'm tempted to look back at the library
> split I did in the KOffice days to see whether we didn't already have
> something like that which got merged up again.
> 
> On the other hand, I'm wondering whether we couldn't split up the widgets
> library between flake and kotext and remove one library altogether.
But do we really want to pull widget into flake. i though our long term goal 
might be to not have it depend on widgets.

Also widgets contain several basic widgets like unit-numerical-input and the 
aspect lock you know the (un)broken chain.

Not saying we can't do it like this