| Summary: | add a Magma backend | ||
|---|---|---|---|
| Product: | [Applications] cantor | Reporter: | epanelelytha |
| Component: | general | Assignee: | Cantor Bugs <cantor-bugs> |
| Status: | RESOLVED LATER | ||
| Severity: | wishlist | CC: | filipe, warquark |
| Priority: | NOR | ||
| Version First Reported In: | 19.08 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
epanelelytha
2019-09-08 11:04:11 UTC
Can you provide more infos about this software? Currently Cantor has a lot of backends and too small developers for take care about all of them. There is already a Magma interface in Sage: http://doc.sagemath.org/html/en/reference/interfaces/sage/interfaces/magma.html Using this, maybe we only need syntax highlighting http://magma.maths.usyd.edu.au/magma/extra/ and autocompletion for Magma in the sage-backend. I have researched information about Magma, and I think, we won't add magma in near future, because of: 1) Magma, as I see, is a proprietary software and isn't too open for downloading, so even downloading magma executable is a problem. 2) Working with Magma via Sage, I think, not an option, because working with Sage is a difficult byself (different reasons) and adding magma to this situation , I think, will make MagmaSage backend actually the most difficult backend in Cantor 3) Cantor have a lot of backends, and have not a lot of developers. We have a troubles even with supporting of existed backends, and adding another complex backend not help us... 4) Magma is not very popular, as I see, and given 3), it is important, because of this, we targets widely used languages/packages, because of a lack of developers |