Hi,
I started to port an KDE 3.5 app (Kooldock) to TDE R14.0.1. I did it years ago for TDE 3.5.13 with minimal trouble and used it since then with no trouble at all. Kooldock is automake and configure based and was developed as a kdevelop project. I have now a new machine (Ubuntu 14.04 64 bits) on which I installed TDE 14.0.1 with the live TDE ISO. I installed all required Trinity development packages. I can run the automake and configure tools inside TDevelop (TDE-C++) successfully so I am ready to build the Kooldock project.
The build fails immediately because of the name of include files i.e. kpopupmenu.h -> tqpopupmenu.h and names of classes i.e QString -> TQString.
Is there a way (script or utility) to convert existing KDE 3.5 or TDE 3.5.x code to TDE 14.0.1? Or at least, a documented path to port apps to TDE 14.x.?
I am a developer, familiar with sed ands awk so I can manage converting the original sources if only I can get a guidance about what becomes what with TDE 14.x.
After trying some manual modifications to the sources I feel some changes in include files are not this straightforward. For example some kxxxxxx.h files are now txxxxxx.h, others are now tdexxxxxx.h so porting my favorite application would become a nightmare with no how-to or minimal help.
I would like to port the Baghira theme too (I did it for TDE 3.5.13 easily) but I am a bit reluctant to compile one line of code at a time, searching each include file/class name change.
I love TDE and will stick to it anyway but I ask for some help here - if possible -
Thanks for keeping TDE alive. It is the best DE I ever used (and I tried many, believe me!) And thanks for any feedback too.
midi-pascal
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On 2015/09/18 08:12 AM, midi-pascal wrote:
Hi,
I started to port an KDE 3.5 app (Kooldock) to TDE R14.0.1. I did it years ago for TDE 3.5.13 with minimal trouble and used it since then with no trouble at all. Kooldock is automake and configure based and was developed as a kdevelop project. I have now a new machine (Ubuntu 14.04 64 bits) on which I installed TDE 14.0.1 with the live TDE ISO. I installed all required Trinity development packages. I can run the automake and configure tools inside TDevelop (TDE-C++) successfully so I am ready to build the Kooldock project.
The build fails immediately because of the name of include files i.e. kpopupmenu.h -> tqpopupmenu.h and names of classes i.e QString -> TQString.
Is there a way (script or utility) to convert existing KDE 3.5 or TDE 3.5.x code to TDE 14.0.1? Or at least, a documented path to port apps to TDE 14.x.?
I am a developer, familiar with sed ands awk so I can manage converting the original sources if only I can get a guidance about what becomes what with TDE 14.x.
After trying some manual modifications to the sources I feel some changes in include files are not this straightforward. For example some kxxxxxx.h files are now txxxxxx.h, others are now tdexxxxxx.h so porting my favorite application would become a nightmare with no how-to or minimal help.
I would like to port the Baghira theme too (I did it for TDE 3.5.13 easily) but I am a bit reluctant to compile one line of code at a time, searching each include file/class name change.
I love TDE and will stick to it anyway but I ask for some help here - if possible -
Thanks for keeping TDE alive. It is the best DE I ever used (and I tried many, believe me!) And thanks for any feedback too.
midi-pascal
Hi, have a look here: http://trinity-devel.pearsoncomputing.net/?0::14570 If you still have problem, let us know. BTW, once you convert some apps please let us know. Any improvement to TDE helps :-) And if you want to join the dev team, doors are always open!
Cheers Michele
On 15-09-18 11:46 AM, Michele Calgaro wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On 2015/09/18 08:12 AM, midi-pascal wrote:
Hi,
I started to port an KDE 3.5 app (Kooldock) to TDE R14.0.1. I did it years ago for TDE 3.5.13 with minimal trouble and used it since then with no trouble at all. Kooldock is automake and configure based and was developed as a kdevelop project. I have now a new machine (Ubuntu 14.04 64 bits) on which I installed TDE 14.0.1 with the live TDE ISO. I installed all required Trinity development packages. I can run the automake and configure tools inside TDevelop (TDE-C++) successfully so I am ready to build the Kooldock project.
The build fails immediately because of the name of include files i.e. kpopupmenu.h -> tqpopupmenu.h and names of classes i.e QString -> TQString.
Is there a way (script or utility) to convert existing KDE 3.5 or TDE 3.5.x code to TDE 14.0.1? Or at least, a documented path to port apps to TDE 14.x.?
I am a developer, familiar with sed ands awk so I can manage converting the original sources if only I can get a guidance about what becomes what with TDE 14.x.
After trying some manual modifications to the sources I feel some changes in include files are not this straightforward. For example some kxxxxxx.h files are now txxxxxx.h, others are now tdexxxxxx.h so porting my favorite application would become a nightmare with no how-to or minimal help.
I would like to port the Baghira theme too (I did it for TDE 3.5.13 easily) but I am a bit reluctant to compile one line of code at a time, searching each include file/class name change.
I love TDE and will stick to it anyway but I ask for some help here - if possible -
Thanks for keeping TDE alive. It is the best DE I ever used (and I tried many, believe me!) And thanks for any feedback too.
midi-pascal
Hi, have a look here: http://trinity-devel.pearsoncomputing.net/?0::14570 If you still have problem, let us know. BTW, once you convert some apps please let us know. Any improvement to TDE helps :-) And if you want to join the dev team, doors are always open!
Cheers Michele
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2
iQIcBAEBCgAGBQJV/DG8AAoJECp1t8qK3tXPOGgP/jp6AZ003lDisCvvAQBirIfH cDBH93pHtq2v8qMhnSj1ErJVHrGP4I0zVff5KglkhPbLFEoGRDokhG32Fok3TdfU W+sEAonyJfdh8OZrGvGJCDF030zV+RAkMiHuI5DQk7xqAZBkEoX9UKwEInFKpa7t sTNoMcP+yIevdgTNR+9yUTL56/E2+crHw18FvODKjG+pUGtvbagn2Dxt13DDkd+j OFC+O99DubJ/KAJQ/mx3TzTlCAQzbrXXY7vwcR6yLWwwJMfyj6ULJi97z2pwco1k GYLTeswhlTAtU4YI1mdPnzneH9+V9Shx+dYOBAKev/QHgwt9uXcss+JEE09lo1cU tyb6+e4hXkLLWYNg0tTpHBY7CnGJZ94VbQ/mK5CmpOX3Y6w3p3EoDK/P/P4+zXHt u7A9QR4o5Ua5duLeHNjqaJCm/8rt6j7SYXj8f6xjFIzvTdnM3qDRgTefI9+rBT7I 47hVySORDvxMVfwAmkZESAsMKNWWXTcqWvQw3Xnr61ZvsiolCLzeK5gBP2e8KqOO 1sZDfDHOeW3zIaLbt5+f6A1lLLhccJGeTRnhS+YBIUhj0hFJhC9gkV/6wM9ntAS2 pG7FNbuAyHj7YlxSrrbEoFRmOx7DW5IlNCzyjeDA87zObsmXYS0JupNVj/MKg+1R wplua59tShLZ7J7jGCw1 =HtPE -----END PGP SIGNATURE-----
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Hi Michele,
Thanks a lot! This is exactly what I was looking for. However, is there a way I can download the "experimental" directory locally to my box? I can look at the scripts but did not find how to get them except by a copy/paste of each individual file. The must be a better way to do it. May I kindly ask for one more hint? :-)
Thanks, midi-pascal
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Hi, have a look here: http://trinity-devel.pearsoncomputing.net/?0::14570 If you still have problem, let us know. BTW, once you convert some apps please let us know. Any improvement to TDE helps :-) And if you want to join the dev team, doors are always open!
Cheers Michele
--------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Hi Michele,
Thanks a lot! This is exactly what I was looking for. However, is there a way I can download the "experimental" directory locally to my box? I can look at the scripts but did not find how to get them except by a copy/paste of each individual file. The must be a better way to do it. May I kindly ask for one more hint? :-)
Thanks, midi-pascal
--------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Easiest way is to clone the GIT repo, although it could take some time ;-) Remember the main trunk is on R14.1.x and if you need to switch to R14.0.1 if you want to build for that. Otherwise if you just want the experimental scripts, go here https://git.trinitydesktop.org/cgit/experimental/tree/ and then you can save each file one by one from your browser.
Cheers Michele
On 15-09-19 11:31 AM, Michele Calgaro wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
Hi, have a look here: http://trinity-devel.pearsoncomputing.net/?0::14570 If you still have problem, let us know. BTW, once you convert some apps please let us know. Any improvement to TDE helps :-) And if you want to join the dev team, doors are always open!
Cheers Michele
--------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Hi Michele,
Thanks a lot! This is exactly what I was looking for. However, is there a way I can download the "experimental" directory locally to my box? I can look at the scripts but did not find how to get them except by a copy/paste of each individual file. The must be a better way to do it. May I kindly ask for one more hint? :-)
Thanks, midi-pascal
--------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Easiest way is to clone the GIT repo, although it could take some time ;-) Remember the main trunk is on R14.1.x and if you need to switch to R14.0.1 if you want to build for that. Otherwise if you just want the experimental scripts, go here https://git.trinitydesktop.org/cgit/experimental/tree/ and then you can save each file one by one from your browser.
Cheers Michele
Hi,
The "experimental" scripts did the magic to the kooldock sources! I had to do some changes manually but these were not related to TDE or tqt. All sources compiled easily but the link step failed because the command was missing -lDCOP and -ltdefx.
My beloved kooldock works well but there are still many compilation warnings - not TDE related - which I will fix and find my way to add the missing libraries to the link step (in configure.in?)
Then I will be pleased to give the result to the TDE team if it is of some interest. kooldock is a very kool app!
Thanks for your great help, it saved me many hours of tedious work.
midi-pascal
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On 2015/09/24 11:03 PM, midi-pascal wrote:
Hi,
The "experimental" scripts did the magic to the kooldock sources! I had to do some changes manually but these were not related to TDE or tqt. All sources compiled easily but the link step failed because the command was missing -lDCOP and -ltdefx.
My beloved kooldock works well but there are still many compilation warnings - not TDE related - which I will fix and find my way to add the missing libraries to the link step (in configure.in?)
Then I will be pleased to give the result to the TDE team if it is of some interest. kooldock is a very kool app!
Thanks for your great help, it saved me many hours of tedious work.
Yes please, once you complete the building of kooldock correctly, please let us know. Even better create a bug report on bugszilla and upload the original source tarball and any instruction required for building it correctly. A final version package would also be useful.
Thanks Michele
On 15-09-25 08:22 AM, Michele Calgaro wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On 2015/09/24 11:03 PM, midi-pascal wrote:
Hi,
The "experimental" scripts did the magic to the kooldock sources! I had to do some changes manually but these were not related to TDE or tqt. All sources compiled easily but the link step failed because the command was missing -lDCOP and -ltdefx.
My beloved kooldock works well but there are still many compilation warnings - not TDE related - which I will fix and find my way to add the missing libraries to the link step (in configure.in?)
Then I will be pleased to give the result to the TDE team if it is of some interest. kooldock is a very kool app!
Thanks for your great help, it saved me many hours of tedious work.
Yes please, once you complete the building of kooldock correctly, please let us know. Even better create a bug report on bugszilla and upload the original source tarball and any instruction required for building it correctly. A final version package would also be useful.
Thanks Michele
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2
iQIcBAEBCgAGBQJWBTxxAAoJECp1t8qK3tXPjz0P/ApqLhXiLg/fXKXPuMPkbEbd 9VPHxr+5xHhLDly4RMiQbwaWaoxd8da1xoiUqN6+fVGKaXqQU56NSltcneLyhV4l 6x3kFoduoxzGhO6ZFm/LyA6lmhoVPPH1rk0kYbPZo6+ZP6c3BEoSO9iUnZg/bYL4 W9wSqy/FBkwVoPB8KD7xS0eVzVExMeGmi7dF4fsKRRMcFwDjhMtBTmAMLITdrpo9 SF7igc204qq+lF5ED5lCHLmxc8KwkTuOQgebUSFSuNB4WUEwOhBY80tS7GPIRn8J kKgmVfZP4gUQxdiLADi/bWK69KSCy3cvkLZ3WEZKFVq0Yty6NHMRzgmE/Nnr23Wg D6cwpoStYO41DV28siKnqkVpYz1ZJWrQN5eC05uq1OG3LFVLHbA5ETdxGPk51/yx KWs56T5Vg163f2h7x7V4Ed9qaA8K5AopxOWW2yrGwa3nir4C+lgBBWiTpWkIUyyr NpoQbgi79PkH0JXmAAQC35c5jokV5LxX2v8bzrSZUiU5MXQviaNaHWuy6d3bWkNh y+LjfN4W2/bGLTgt6DY+v3pFOwH30Q3ObyfuP8ozF0lh/Iy6tAOKSwNv1zZe8KXc ILtRAcfbu3Whsaafw3Sd7XFto6GaA8bNvxeHLRaxwSnOu1D3CMuWOusz3BEn3/Yr 4vWhhYp7gDj5AncaVsA3 =U91r -----END PGP SIGNATURE-----
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Hi Michele, I created a bug report on Bugzilla for this ( http://bugs.pearsoncomputing.net/show_bug.cgi?id=2535) but I cannot attach the kooldock tarball to it. I can choose the file but it does not get uploaded. So I attach the tarball to this mail so the dev team can get it.
Thanks, midi-pascal
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
On 15-09-25 08:22 AM, Michele Calgaro wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On 2015/09/24 11:03 PM, midi-pascal wrote:
Hi,
The "experimental" scripts did the magic to the kooldock sources! I had to do some changes manually but these were not related to TDE or tqt. All sources compiled easily but the link step failed because the command was missing -lDCOP and -ltdefx.
My beloved kooldock works well but there are still many compilation warnings - not TDE related - which I will fix and find my way to add the missing libraries to the link step (in configure.in?)
Then I will be pleased to give the result to the TDE team if it is of some interest. kooldock is a very kool app!
Thanks for your great help, it saved me many hours of tedious work.
Yes please, once you complete the building of kooldock correctly, please let us know. Even better create a bug report on bugszilla and upload the original source tarball and any instruction required for building it correctly. A final version package would also be useful.
Thanks Michele
-----BEGIN PGP SIGNATURE----- Version: GnuPG v2
iQIcBAEBCgAGBQJWBTxxAAoJECp1t8qK3tXPjz0P/ApqLhXiLg/fXKXPuMPkbEbd 9VPHxr+5xHhLDly4RMiQbwaWaoxd8da1xoiUqN6+fVGKaXqQU56NSltcneLyhV4l 6x3kFoduoxzGhO6ZFm/LyA6lmhoVPPH1rk0kYbPZo6+ZP6c3BEoSO9iUnZg/bYL4 W9wSqy/FBkwVoPB8KD7xS0eVzVExMeGmi7dF4fsKRRMcFwDjhMtBTmAMLITdrpo9 SF7igc204qq+lF5ED5lCHLmxc8KwkTuOQgebUSFSuNB4WUEwOhBY80tS7GPIRn8J kKgmVfZP4gUQxdiLADi/bWK69KSCy3cvkLZ3WEZKFVq0Yty6NHMRzgmE/Nnr23Wg D6cwpoStYO41DV28siKnqkVpYz1ZJWrQN5eC05uq1OG3LFVLHbA5ETdxGPk51/yx KWs56T5Vg163f2h7x7V4Ed9qaA8K5AopxOWW2yrGwa3nir4C+lgBBWiTpWkIUyyr NpoQbgi79PkH0JXmAAQC35c5jokV5LxX2v8bzrSZUiU5MXQviaNaHWuy6d3bWkNh y+LjfN4W2/bGLTgt6DY+v3pFOwH30Q3ObyfuP8ozF0lh/Iy6tAOKSwNv1zZe8KXc ILtRAcfbu3Whsaafw3Sd7XFto6GaA8bNvxeHLRaxwSnOu1D3CMuWOusz3BEn3/Yr 4vWhhYp7gDj5AncaVsA3 =U91r -----END PGP SIGNATURE-----
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Hi Michele, I created a bug report on Bugzilla for this ( http://bugs.pearsoncomputing.net/show_bug.cgi?id=2535) but I cannot attach the kooldock tarball to it. I can choose the file but it does not get uploaded. So I attach the tarball to this mail so the dev team can get it.
Thanks, midi-pascal
Slavek, do you want to handle upload? The empty GIT repository 'kooldock' is available to accept sources when they are ready.
Thanks!
Tim
On Thursday 01 of October 2015 05:17:45 Timothy Pearson wrote:
On 15-09-25 08:22 AM, Michele Calgaro wrote:
On 2015/09/24 11:03 PM, midi-pascal wrote:
Hi,
The "experimental" scripts did the magic to the kooldock sources! I had to do some changes manually but these were not related to TDE or tqt. All sources compiled easily but the link step failed because the command was missing -lDCOP and -ltdefx.
My beloved kooldock works well but there are still many compilation warnings - not TDE related - which I will fix and find my way to add the missing libraries to the link step (in configure.in?)
Then I will be pleased to give the result to the TDE team if it is of some interest. kooldock is a very kool app!
Thanks for your great help, it saved me many hours of tedious work.
Yes please, once you complete the building of kooldock correctly, please let us know. Even better create a bug report on bugszilla and upload the original source tarball and any instruction required for building it correctly. A final version package would also be useful.
Thanks Michele
Hi Michele, I created a bug report on Bugzilla for this ( http://bugs.pearsoncomputing.net/show_bug.cgi?id=2535) but I cannot attach the kooldock tarball to it. I can choose the file but it does not get uploaded. So I attach the tarball to this mail so the dev team can get it.
Thanks, midi-pascal
Slavek, do you want to handle upload? The empty GIT repository 'kooldock' is available to accept sources when they are ready.
Thanks!
Tim
Yes, I'll take care of it :)
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On 2015/10/01 09:07 AM, midi-pascal wrote:
Hi Michele, I created a bug report on Bugzilla for this ( http://bugs.pearsoncomputing.net/show_bug.cgi?id=2535) but I cannot attach the kooldock tarball to it. I can choose the file but it does not get uploaded. So I attach the tarball to this mail so the dev team can get it.
Thanks, midi-pascal
tarball uploaded. Thanks for contributing to TDE, good work. Keep it up if you can, you are welcome ;-) kooldoc will not go in any of the r14.0.x releases, but it would be a valuable addition for R14.1.0, IMO. Cheers Michele
On 15-10-01 12:16 PM, Michele Calgaro wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On 2015/10/01 09:07 AM, midi-pascal wrote:
Hi Michele, I created a bug report on Bugzilla for this ( http://bugs.pearsoncomputing.net/show_bug.cgi?id=2535) but I cannot attach the kooldock tarball to it. I can choose the file but it does not get uploaded. So I attach the tarball to this mail so the dev team can get it.
Thanks, midi-pascal
tarball uploaded. Thanks for contributing to TDE, good work. Keep it up if you can, you are welcome ;-) kooldoc will not go in any of the r14.0.x releases, but it would be a valuable addition for R14.1.0, IMO. Cheers Michele
Thank you very much for your help Michele!
I am currently working hard to port my favorite style - Baghira - to TDE R14 with mitigated success for now. Only the window decorations work well but the style itself gives an ugly - really ugly - look to TDE.
I succeeded to port it to the previous TDE version with some effort (the source code is very bad) but this time it is really difficult!
Anyway I will let you know if I succeed and in this case for sure I be pleased to give the result to TDE.
midi-pascal
midi-pascal wrote:
The "experimental" scripts did the magic to the kooldock sources! I had to do some changes manually but these were not related to TDE or tqt. All sources compiled easily but the link step failed because the command was missing -lDCOP and -ltdefx.
+1 for the DCOP linkage - fixed in admin/acinclude.m4.in