Richard Eckart de Castilho

The idea with the initializer is a bit more than just `load type system X`. The idea is that the initializer patches the CAS instance with additional methods, e.g. ```...

The "best" solution for this would probably be to use DKPro Meta :)

Well, basically what you do is create a Maven Project which has a dependency on all `dkpro-core-api-**` modules and then call ``` TypeSystemDescription dkproCoreTS = TypeSystemDescriptionFactory .createTypeSystemDescription(); try (FileOutputStream out...

But then we'd end up having to import CAS from different libraries...

For the moment, I don't feel very comfortable with this. I don't like the idea of the CAS **becoming** something new just because it contains certain types. The idea of...

I understand that IDEs may not support auto-complete for such extensions. But I wonder if IDEs like PyCharm really **only** do static code analysis or also consider whether a method...

The idea of involving cassis came to me because I though we should/could pass the type system "strategy" to the constructor - i.e. cassis would somehow have to understand the...

So the IDE dynamically evaluates the DKProAccessor to discover the fields?

How does the IDE know that e.g. Token has the field `form`? I don't see anything in your code that would do that?

Generating classes from the type system description - so a "pycasgen" - an equivalent of the "jcasgen" we have in Java which generates Java classes from the type system. Why...