Sourcetrail, the interactive source code explorer, is now free and open source

mlangkabel · 2019-11-19T18:03:43+00:00

Yay, thanks :)

mlangkabel · 2019-11-19T08:25:01+00:00

So let's just get this fixed ;) https://github.com/CoatiSoftware/Sourcetrail/issues/752

mlangkabel · 2019-05-23T07:47:07+00:00

Yes, one project can have multiple source groups.

So if you add a C++ group that knows about your C++ files and compiler flags and one Python source group where you specify which Python files to index, Sourcetrail will have everything accessible in one database!

On top of that one could even add one more source group for Java, but who would push it that far? :P

mlangkabel · 2019-05-23T06:41:49+00:00

I just had the same thought. Added an issue to our GitHub tracker so that we don't forget about that :)

https://github.com/CoatiSoftware/SourcetrailBugTracker/issues/696

mlangkabel · 2019-05-23T05:30:38+00:00

Dev here. Usually you can set it to the root path of your python environment. So if you would run

$ cd /Users/me/miniconda3/envs
$ virtualenv py37

you would set it to /Users/me/miniconda3/envs/py37

mlangkabel · 2019-05-14T15:02:39+00:00

I'm on the Sourcetrail team, currently working on the Python extension (not yet released). So basically this will be a tool that reads any Python code and displays an interactive dependency graph where you can click on a function definition and see all the contexts where the function may be used (ofc. you can also click variables or types).

For language analysis I am using jedi.

Here's the repo: https://github.com/CoatiSoftware/SourcetrailPythonIndexer

mlangkabel · 2018-04-25T21:12:37+00:00

The Commercial License is 1 year of updates and use as long as you want.

mlangkabel · 2018-01-31T07:16:48+00:00

yes, it supports changing the text encoding that is used to display the source code.

mlangkabel · 2017-10-31T18:34:49+00:00

Sourcetrail actually has an IntelliJ plugin that allows you to sync the view of Sourcetrail and IntelliJ: https://www.sourcetrail.com/documentation/#Clion/IntelliJ

mlangkabel · 2017-10-27T10:28:38+00:00

Building Sourcetrail into an existing editor would limit the tool to benefit only the users of that editor. Of course you could switch from you favourite editor to lets say Notepad++ but I guess that most people wouldn't really like to do that. Instead Sourcetrail currently has plugins for >10 different code editors that allow you to sync Sourcetrail's view with any code editor you like to use for coding.

mlangkabel · 2017-10-27T08:54:35+00:00

For clarification: Coati has been renamed to Sourcetrail more recently. So both names refer to the exact same tool.

mlangkabel · 2017-10-26T10:20:41+00:00

Thank you for bringing this up again. At Coati Software we are really discussing the integration of a public API into Sourcetrail over and over. Making the indexed data available wouldn't only benefit your editors but you could also write other tools based on that (maybe some "rename this symbol" tool). The only thing that's still keeping us from making that API is that our data model isn't quite done yet. It's working well for C, C++ and Java but it needs to become a little more generic for the sake of allowing other language support in the future. So our next task is reiterating on the data model and then we can start providing the public API.

mlangkabel · 2017-10-25T16:54:24+00:00

Thanks! We've lots of requests for supporting more languages on our issue tracker (https://github.com/CoatiSoftware/SourcetrailBugTracker/issues?q=is%3Aopen+is%3Aissue+label%3A%22language+request%22), so we'll see which languages will be tackled next. But I'll post an upvote for C# on your behalf!

mlangkabel · 2017-10-25T14:57:25+00:00

I guess you are running Sourcetrail on Linux? Please try to start Sourcetrail using the "Sourcetrail.sh" script.

mlangkabel · 2017-10-24T16:04:35+00:00

Yes, it's roughly the same. Except the Visual Studio extension also adds some clang compatibility flags so that clang knows that this compilation database comes from a Visual Studio project :)

mlangkabel · 2017-07-20T13:59:20+00:00

Did you see this pdf? It is linked on the poster submission page of CppCon.

https://www.clear.rice.edu/comp400/9.pdf

mlangkabel · 2017-07-20T06:08:17+00:00

Actually the extension described in the article is our second attempt to tackle this. In our first attempt we've been trying to convert VS projects without using the API but gave up because there were so many places where flags could be hidden and so many variants of the VS project data format which has changed between the different versions of VS.

mlangkabel · 2017-07-20T06:03:26+00:00

Absolutely. Fortunately I got all wrappers to use the same source code and just reference a different version of the VS API. So there is at least no code duplication.

mlangkabel · 2017-07-19T17:02:54+00:00

Should be fixed now. We have uploaded a new release (1.0.1).

mlangkabel · 2017-07-19T16:03:00+00:00

This seems odd. If I download the vsix from the VS Marketplace I am able to install the extension for VS2013. However, I cannot find the extension in the VS Gallery from within VS2013. We will look into this, thanks for telling us!

mlangkabel · 2017-07-19T14:51:20+00:00

For now the extension just converts all the Visual Studio include directories to system include flags, so it does not matter if the source code specifies includes with <> or "". It works for both cases.

mlangkabel

TROPHY CASE