TOPIC:

I foresee that I will need to work with both Lazarus and CodeTyphon in the future, and so it is in my interest that both the CodeTyphon and the original (Lazarus/Delphi) packages are well maintained.

I understand that PilotLogic often fixes bugs in the packages that it integrates into CodeTyphon, may I ask what procedure you follow to do this? for example, when the authors of a Lazarus or Delphi package release a new version, how do you combine the authors' changes with your own?

Could I contribute to this work (since it is in my own interest) ?

Thanks Sir
the answer is very simple:

with a lot of work

Every day 2-3 of our programmers work to Update and Fix about 250 "tracking" libraries
Then we must test these libraries on ALL CT supported Host OSes,
again and again.

That is indeed quite a lot of work!

But what I principally meant is: are you re-applying your changes to every new release of the original package, or do your fixes and improvements flow back to the original sources?

Sir
most of CT libraries are fork of original sources
so, we put in our libraries only the changes that work with CT.

For sample
look at pl_VirtualTrees library, it's a Multi OS-CPU-Platform fork of original VirtualTrees library

pl_VirtualTrees can run on Solaris-64-GTK2 or on FreeBSD64-QT5 etc...
the original source it's for Windows Only...

Please, don't forget CodeTyphon it's 10 year old...

Thank you for your answer. So, it's in fact the other way around: you collect improvements from the original authors/maintainers and incorporate them into your own forks.

Is there a way to trace the changes PilotLogic has made to the packages all the way back to the moment when they were forked?

Yes
we put "ct9999" identification text on every change we make

PS: but, we will stop this methodology very soon...

Matis A. wrote: Yes
we put "ct9999" identification text on every change we make

Thank you Matis!

I might be interested in maintaining a Typhon version of the Castle 3D engine. Do you think you could make your latest release of that package available to me, so that your changes won't be lost ?

PS: but, we will stop this methodology very soon...

May I ask why ?

1) We will try to port again Castle 3D to CT
but no promise

2) We thinking for a modifications tracking system,
in our lab we working and explore this CT ability