Open jurgenvinju opened 1 year ago
We should start printing a deprecation warning in the repl of eclipse? (with some link to a blogpost describing it)
TODO for this to work out fine:
util::IDE
to util::LanguageServer
salix-core
and salix-contrib
as well as the vis::Figure
libraryThere is an opportunity to factor vis::Figure
into a separate maintainable project, where SWT is used or SVG output is created based on an SWT graphics environment that can output SVG. However, there are also ports of vis::Figure
out there already that generate JS/HTML/SVG, and a salix enabled port as well. So before we delete rascal-eclipse, we also have to think about the future of vis::Figure
.
This is to register the intent to mark "rascal-eclipse" for deprecation and eventual removal. This includes the nested project for the update site, the feature, the actual plugin, and the developers-feature that would link Rascal JUnit tests to their source locations.
util::IDE
can not literally be used to callutil::LanguageServer
from the rascal-language-servers project, the concepts are exactly the same and only some minor rewiring is requested.vis::Figure
was not used by many students anymore, but still we have to bring the documentation ofvis/*
andsalix-*
up to the level of the Figure libraryPlease sign here for the consent of the idea:
In the meantime we will make only small bugfix releases of rascal-eclipse, to help straggling users while they prepare to migrate. I will add a documentation issue about documenting the migration from rascal-eclipse DSL implementations to VScode DSL implementations