-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA224
Hi1) it looks like the package I am talking about needs porting from the old kde3 to the newer tde ... where to start?2) Also thinking about a way of syncing phone data with tde (missing already since years) - ideas?One option would be to bind the syncevolution engine to the kde3 pim - feasibility?I was updating opensync-akonadi once ... but opensync does not cope with syncML.Big issue ... I should have bought 100 cheap nokia or siemens phone, who were syncing perfectly with KDE3 ... 3) what does the bandwidth and hosting for the TDE cost per year?
thanks in advance regards
There are two scripts in the TDE source archive (experimental/qt3-tqt3/convert_existing_qt3_app_to_tqt3 and experimental/kde-tde/convert_existing_kde3_app_to_tde). Look at those scripts, make any modifications needed for your system, and run them from within the original source archive.
If you want to help by adding a new application to TDE, you could first import the original sources to a new GIT repository, then clean up the old Makefile.in and configure files and commit that as a cleanup commit. After that run the conversion scripts, verify buildability, and commit the converted sources before pushing the entire repository up to GitHub or similar.
Note that you will probably want to delete the old admin module and replace it with the current TDE admin submodule. You can do that from within your converted source directory as follows: rm -rf admin git submodule add http://system@scm.trinitydesktop.org/scm/git/tde-common-admin admin git submodule add http://system@scm.trinitydesktop.org/scm/git/tde-common-cmake cmake git submodule update --init git commit -a -m "Added common directories" git push origin master
Hope this helps!
Tim