Difference between revisions of "Porting to TDE"
Jump to navigation
Jump to search
m (tqt: added link to api changes) |
m (→Widget styles: added bit about porting from readme) |
||
| Line 11: | Line 11: | ||
== Widget styles == |
== Widget styles == |
||
| − | The TQt Style API has [https://mirror.git.trinitydesktop.org/gitea/TDE/tqt3/src/branch/master/changes-3.5 undergone] [https://mirror.git.trinitydesktop.org/cgit/qt3/commit/?id=0008bc5bcd95694b38b0d0322aac2ea6fdb21298 important changes], so porting a widget style to TDE will entail more than just running scripts. |
+ | The TQt Style API has [https://mirror.git.trinitydesktop.org/gitea/TDE/tqt3/src/branch/master/changes-3.5 undergone] [https://mirror.git.trinitydesktop.org/cgit/qt3/commit/?id=0008bc5bcd95694b38b0d0322aac2ea6fdb21298 some important changes], so porting a widget style to TDE will entail a little more than just running scripts. |
| + | |||
| + | Porting an existing style to the new API is relatively straightforward; simply update the function definitions in the existing style with the new definition prototypes and cast the passed pointer to TQWidget or TQObject where appropriate. |
||
== Window decorations == |
== Window decorations == |
||
Revision as of 15:44, 16 February 2022
To-do
This section has not been written/completed yet. You can contribute to Trinity by writing or finalizing this section.This page is intended to provide generic instructions for porting old KDE3 software to the Trinity libraries.
Build system
Software
Widget styles
The TQt Style API has undergone some important changes, so porting a widget style to TDE will entail a little more than just running scripts.
Porting an existing style to the new API is relatively straightforward; simply update the function definitions in the existing style with the new definition prototypes and cast the passed pointer to TQWidget or TQObject where appropriate.