That's a good target, Karl, but another target could be the sage local/bin folder. I rewrote the "process" script in order to make it more similar to the sage-notebook syntax, both in usage and coding practice (https://drive.upm.es/index.php/s/DHh26fgL0RsFCv5). I think a
sage -exam -init option could also be useful, that would copy a template file, plus the required auxiliary files, like sagetex.sty, and then print a useful message. It would be followed by "sage -exam template.tex", without further ado.That would simplify the startup, requiring only that sage is installed. I don't see how this could be done if possibly-maybe-sageexam is distributed within the sagetex folder. Anyway, that's decision to be taken later, since I still need to polish the syntax, refactor, add a couple new features, etc. I also have a longer goal to keep a local database of exam questions. I'm using git locally and I think it would be a good idea at this moment to make a public repo and keep it as an independent project before it is ready to be included in sage, because: - This is a small project, that depends on sage and sagetex but not viceversa, and sage version agnostic, so it will be more agile to add small improvements without upgrading and testing sage regularly. - It will make it a lot easier to install to non-experts before the time when it is completely integrated into sage. - It would also make it simpler, if this small project grows, to submit it to the journal of open source education, for instance. Would love to hear your opinions on those. Regards -- You received this message because you are subscribed to the Google Groups "sage-edu" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/sage-edu/f4846c09-1570-4015-be7f-b916b08a25bdn%40googlegroups.com.
