Peter Kümmel wrote:
Abdelrazak Younes wrote:
That's exactly the problem indeed. My earlier cleanup work is heading
toward "the frontend use the kernel as a library" design. Once this is
achieved, splitting out the toolkit specific frontend should be easy. So
clearly the first candidate for a new dll is the code in frontend/qt4/.
I have started with frontend/qt4/ but give up because qt4 needs several
functions from the other libs.
Yes, that's what I meant by "cleanup frontend/qt4". If a code needs a
function from the other libs, this code must be general enough that it
could be moved to frontend/. There might be exception though...
We must start at the bottom not at the top, and qt4 is at the top.
Yes qt4 is at the top but if you separate out the model from the view in
each of the dialog (as we did for the TOC and Citation dialogs) then all
the Qt specific code could go in a separate library.
Abdel.
