KDE vclplug2003-12-11 (outdated, sorry for that) Contents
IntroductionThe second step in my KDE integration plans was to replace the OOo's VCL layer (GUI toolkit) with its Qt implementation. So far I ported just part of VCL's SAL, which basically means that you should get the same look'n'feel as before, but the drawing is done using the Qt methods and controlled by the Qt events. Maybe you ask "Why to do it at all, if it still looks the same?" Originally, I wanted to continue with replacing the widgets one-by-one when the Qt SAL is mature enough. But VCL is going to be replaced with a brand new toolkit anyway, so it would be a waste of effort. But having Qt events working is still needed—it is important for incorporation of the standard Qt/KDE dialogs, menus, etc. Read this for more. And we still can get closer to the KDE look (not feel), read the document attached to this mail. Some screenshots:
Current statusWARNING: This stuff is experimental. It is evolving, but still it is closer to unfunctionality than to functionality. Browse the source code for TODOs and FIXMEs. Some parts are quite ugly hacks for various reasons; mostly because I wanted to see something, and wanted it quickly. Additionally the VCL code was not documented much, so I had just to guess from sources of others what should this piece of code really do. Luckily, it got better with the introduction of vclplug, thanks! :)
How to get it
If everything went fine, you should be running the Qt OOo now. Should you have any troubles with the installation instructions, please let me know; I did not have time to test all the steps.
What has changed in the codeFirst of all, I took unx VCL implementation and cut it to the bones. Then I started to add the functionality again. Then vclplug was introduced and I remade it once more:-) The most important changes are:
The different naming conventions in OOo and in Qt are little confusing the code, but I am trying my best to be as consistent as possible.
ContributingPlease see the general participation info on the main page. You should have signed Sun's JCA and release your patches both under LGPL and SISSL (see Contributing To OpenOffice.org) so that they could be possibly included in the official OOo tree. Jan Holesovsky /kendy at openoffice org/ |

