Andre Poenitz wrote:
On Tue, Sep 05, 2006 at 10:37:27AM +0200, 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/.
Doesn't that contradict each other?
Shouldn't there be a lyxkernel.dll and the frontend using this?
The frontend virtual interface yes. The qt4 frontend will just be an
implementation of this interface and could entirely be in a single dll.
This way the lyx-executable would not even have to link to Qt4, only the
qt4 frontend dll.
The controller will need some cleanup before it could be split up.
I still think merging the controller into the frontend specific code
would make things a grest deal simpler, more flexible _and_ smaller,
even when using two frontends...
I agree this should be done on a case by case basis. Each dialog
controller should be reviewed for correctness. A controller should not
open a dialog for example. The spellchecher controller is an example of
such bad design.
Abdel.
