Integrated Path Planning Object (T0)

Welcome to our brand new Clickteam Community Hub! We hope you will enjoy using the new features, which we will be further expanding in the coming months.

A few features including Passport are unavailable initially whilst we monitor stability of the new platform, we hope to bring these online very soon. Small issues will crop up following the import from our old system, including some message formatting, translation accuracy and other things.

Thank you for your patience whilst we've worked on this and we look forward to more exciting community developments soon!

  • I just had a quick look through out of interest, and I couldn't help noticing that a lot of the files are from some "HOG" project, which is GPL licensed:

    I might be wrong, but I thought the GPL license meant that if you use the code in a project, you have to release the project as free/open source too?

  • This is a very sticky issue for libraries that proprietary code interfaces with; some people argue that just using a GPL library makes the interfacing code GPL too; others say that if you dynamically link and can use a non-GPL library in its place then it's OK. If it was LGPL it would be fine...

  • My understanding of the license is that the open source part that was used should be made available upon request (or included right away in the package) and that it has to be credited to its author (which is done in the help file's credits section).

    The main reason HOG code is used in my extension is because mostly it's beneficial to HOG not the extension itself as its author is my research supervisor and wants my research work (which a lot of is going into this extension's future updates) be HOG-compatible.

    I can link to things dynamically of course if there is a good reason for it. But I think just sending the open source code to those that need it should be sufficient.

    -Mokhtar M. Khorshid

Participate now!

Don’t have an account yet? Register yourself now and be a part of our community!