Here is the release post that describes the Python integration a bit more detailed: https://www.sourcetrail.com/blog/sourcetrail_supports_python...

So you have a "best before" date on your plastic bags?

Thank you again for your request. We now offer a plugin for VS code: https://github.com/CoatiSoftware/vsce-sourcetrail

Those are probably caused by an issue in your project setup, but I don't think that this is the right place to go into details. If you like to investigate, please send us an e-mail!

thanks for your quick reply, I'll send you a mail later after my investigation

A Compile Command is a JSON file entry that specifies what the C/C++ compiler should do when compiling a file. So it defines a file to compile and all the required flags (like include paths or preprocessor defines). These Compile Commands are used for all kind of Clang based tools. You can read more here: https://clang.llvm.org/docs/JSONCompilationDatabase.html

Yes, we support Compile Commands :)

Yes, Sourcetrail also shows class internal calls and accessed fields. Code Maps in VS has a different approach because they try to keep the graph small by making the user add symbols. So if you are trying to see every access of a symbol it is easy to miss something. Sourcetrail on the other hand keeps the graph small and comprehensible by showing only one level of dependencies. You don't need to add anything yourself. So you cannot miss any relation ;)

Thanks. Sounds more promising than I took from you landing page. I will give it a go on my c/c++ code bases. See if it can help me.

I now notice the free trial cannot be run on your own project. I have to say I won't buy anything that I didn't try on a real sample before. What made you decide to go for this option instead of regular limited functionality or time bound (my preference).

Oh, we have a time bound evaluation testing period available: https://www.sourcetrail.com/trial#test-license

How did I miss that? Will try tomorrow!

Happy to hear that you like it! Full support of Python won't be easy but maybe we could tackle this one in stages. Implement highly demanded features in a first Python release and improve on that later on.

That'd be great. How can we stay in the loop to hear about Python and other feature releases?

Oh, that's an easy question :) You can either follow us on Twitter (https://twitter.com/Sourcetrail) or just sign up for our mailing list (https://www.sourcetrail.com/#get-started). I promise that we won't spam you ;)

+1 for python.

Thank you for the kind words! We are always happy to hear from a satisfied customer :)

To be honest: We have not decided what language we will pick up next. Our first priority is to improve on our Java coverage. In a few months we should be ready to choose our next language. We are thinking about either tackling Python or implement support for a more recent language like Kotlin, Swift or Go.

I doubt there's very much legacy-ish Kotlin or Swift code out there to be a significant selling point for your product.

I spend a lot of time in clients' ios apps which were developed by other contractors long ago and then I'm asked to fix bugs and add new features. I think this would help me save a lot of time. Since it already supports C/C++ would objective-c support be relatively straightforward to add? Not sure if there are many others who would like to see it, but I know I would definitely appreciate it.

Seems to me there is probably a huge amount of legacy Python code around that people need to explore. In fact, I've spent the entire day so far creating some so that we have enough legacy Python code around in a couple more years. Wouldn't want to run short.

I might buy this for Go if it was available, this looks interesting!

Note that I'm mainly interested because my current editor of choice does not have the full suite of tools I'm used to for Go. I used to use Vim, and vim-go has such an excellent suite of tools I don't think I'd buy this. However, I've since switched to Kakoune, and the tool support is quite young and I've not had time to improve it myself. So this tool (at the $100 self employment pricing) is a nice fit for a tool I'm on the fence about. At $200 I don't think I would, but at $100 I think I would.

Anyway, just providing a bit of feedback. Looks really nice!

Thank you for sharing your opinion! This will be exactly what we will be interested in when deciding what language to tackle next :)

I know it's easier said than done, but a pluggable interface for community created language support would go a long way towards gaining traction.

A Lisp might be an easy language to target, because of its consistent syntax and "code is data" philosophy. With Clojure, you could both reuse some of your work on Java, and support Clojure's Java interop. Attempting to support Clojure would drive improvements in the Java support.

Seems to me like the obvious choices would be languages that have large, long standing legacy codebases. Swift code is going to be relatively tight just because it's so recent, whereas something like C# isn't.

Swift would be great. Perhaps you could leverage SourceKit.

Python, Scala and Go would be great additions (in that order).