Difference between revisions of "Qt Interface"

From Lazarus wiki
Jump to navigationJump to search
Line 5: Line 5:
 
The Qt 4 widgetset is in an early stage of development.
 
The Qt 4 widgetset is in an early stage of development.
  
This interface is based on Qt 4.2 and it's corresponding documentation [http://doc.trolltech.com/4.2/ here].
+
This interface is based on Qt 4 and it's corresponding documentation [http://doc.trolltech.com/4.2/ here].
  
 
=== Quick start guide for Linux ===
 
=== Quick start guide for Linux ===

Revision as of 16:33, 14 September 2006

English (en) español (es) 日本語 (ja)

Introduction

The Qt 4 widgetset is in an early stage of development.

This interface is based on Qt 4 and it's corresponding documentation here.

Quick start guide for Linux

The first thing to do is go to the official website of the bindings and download the binary Qt bindings. Copy the file libqt4intf.so to the directory /usr/lib/

Now compile the LCL for Qt. First open your normal gtk compiled Lazarus. Then go on the menu "Tools" --> "Configure Build Lazarus". Set LCL to "clean+build" and everything else to "None". Now select "Qt" and click on the "Ok" button. Next go to the menu "Tools" --> "Build Lazarus". Now the LCL is compiled for Qt.

To compile a project for Qt just select it as the target widgetset on the Compiler Options dialog.

At this moment the Lazarus IDE cannot be compiled for Qt because it uses features missing on this widgetset.

Installing Qt 4

Qt 4 is very new, so many distributions don´t come with it by default. If your distribution is RPM-based you can search for a qt4 package here: http://rpm.pbone.net/index.php3/stat/2/simple/2

Quick start guide for Mac OS X

Instructions on the Qt Interface Mac wiki page.

Quick start guide for PDAs and Smartphones

please write me

Quick start guide for Windows

please write me

Qt 4 Bindings

This interface utilizes Qt 4 bindings created by Den Jean. The bindings are a c++ library which exports the methods of the Qt objects as procedures. The library has 800kb in linux, consists of a single .so file that needs to be distributed with your LCL program.

You can find more information about those bindings on the official website and on fpc:Qt4 binding.

Is is being reported that it may be possible to link to Qt 4 directly, using some tricks. Many think it is not. This is yet to be tested. It is expected that any such binding will be compatible with the currently utilized one, so the interface code won´t have to be changed.

Compiling the bindings

It is not necessary to compile the bindings yourself if you plan to release a GPL software. GPL Binaries are available on Den Jean website. If you want to release non-GPL code, then you must compile the bindings yourself using the Commercial Edition of Qt.

Step 1 - To start with download all the files needed to compile the bindings.

  • Download the source code of the bindings. Go to the offical website of the bindings. Link above.
  • Also Download Qt 4.1.1 source code for the desired platform. This is the download page: [1]

Step 2 - Unpack all the files you downloaded. Enter the directory where you downloaded Qt 4.1.1 source code and use this command:

./configure

Step 3 - Go to the directory where you downloaded and extracted qt4pas sources and edit the file compile_lib.bash. Change the path for the Qt 4.1.1 source code.

Step 4 - Run the script called compile_lib.bash. Now you should have a file called libqt4intf.so

Road map for the Qt 4 interface

currently implemented components with their status

Moved here: Roadmap#Widgetset_dependent_components

components scheduled to be implemented

  • TPopUpMenu
  • TBitmap - Needs a description of the internal format used by Qt
  • TPixmap
  • TIcon

currently implemented Windows API functions by group and with status

Mouse functions

SetCursorPos, GetCursorPos for TMouse - Fully working

GDI functions

BeginPaint, GetDC, EndPaint, ReleaseDC, Rectangle, MoveToEx, LineTo, Ellipse for TCanvas and OnPaint event- Fully working

Screen functions

GetSystemMetrics for Screen.Width and Screen.Height - Fully working

Coments

It's really interesting.

Buy if will works also on Win32 OS?

It will work for win32. It's just a question of recompiling the bindings. The code on the widgetset is completely platform independent, so the limiting factors are the bindings and Qt. However, there is little use for this on win32. There already exists a win32 native widgetset, you should use that one on Windows. The same code can be recompiled with any of the existing widgetsets on Lazarus. A more interresting place where this will work is: Linux powered PDAs.

When do you think to can see the Lazarus IDE run full on QT4 Lib?

No idea. If only I work on this, maybe 6 months. If others help, sooner.

When do you think will be possible create full GUI applications using QT4?

No idea. If only I work on this, maybe 6 months. If others help, sooner.

Contributing

How to add a new control

For example TButton.

TButton is defined in lcl/buttons.pp. This is the platform independent part of the LCL, which is used by the normal LCL programmer.

Its widgetset class is in lcl/widgetset/wsbuttons.pp. This is the platform independent base for all widgetsets (qt, carbon, gtk, win32, ...).

Its qt interface class is in lcl/interfaces/qt/qtwsbuttons.pp:

 TQtWSButton = class(TWSButton)
 private
 protected
 public
   class function  CreateHandle(const AWinControl: TWinControl; const AParams: TCreateParams): TLCLIntfHandle; override;
 end;

Every WS class, that actually implements something must be registered. See the initialization section at the end of the qtwsXXX.pp unit:

 RegisterWSComponent(TQtButton, TQtWSButton);

TQtWSButton overrides CreateHandle to create a qt QPushButton. The code is short and should be easily adaptable for other controls like TCheckBox. Remember that all controls on the Qt widgetset have a helper class on qtprivate.pp, and it is also necessary to add a class for the new control. This isn´t difficult.

Also notice that DestroyHandle should be implemented to clean up memory utilized by the control.