Thanks, Karl-Dieter.
I've made a little more progress:
1. Supports solutions now, including different instances of same problem.
2. No more \begin{sageprocesstext}{Problem}, just \begin{sagetext} now;
less clutter.
3. It's a single \include that you put right after \begin{document}, but
you sti
Very impressive, Nathan.
> So, here's some types of advice I'd love to receive on this:
>
> 1. Should I actually be suggesting changes to sagetex.sty? Or is there a
> way to do that in my own .sty file? I couldn't call Dan's ST@stuff
> commands from my own document, because I think TeX @ thi
PROGRESS!!
I've actually got a baby version of this working. I'm eager for advice
about how best to polish this and integrate it in a way that isn't as hacky
as this current first attempt is. Here's what I did.
1. The easy part:
In a test document, I run a sagesilent to define a Problem clas
Yeah, you're right, but I'm still going to argue. :)
Indeed, the whole thing would work in Sage exclusively, or a combination of
Sage and TeX (beyond SageTeX). Here are the priorities I was operating
under; all are priorities for the end user of the package, not for the
author of the package.
On Thu, 28 Feb 2013 at 06:46PM -0800, Nathan Carter wrote:
> Sure. The goal is to create a LaTeX package for randomly generated exams.
> It should let you do something like this:
[snip]
You know, it looks like what you _really_ want is a WebWorK server. :)
Looking briefly over your TeX stuff,
Actually, one tiny clarification:
% What each \createproblem{}{}{} command does is run a \sagesilent that
> does is the following:
> % 1. Ensures that a global problem dictionary is defined; if allProblems
> isn't defined globally, do allProblems = {}
> % 2. Constructs and stores a new problem
Sure. The goal is to create a LaTeX package for randomly generated exams.
It should let you do something like this:
\documentclass{whatever}
% Create a whole bunch of exam problem construction methods, with this tool:
% \createproblem{name}{Sage setup code}{problem text with \sage calls in it}
On Tue, 26 Feb 2013 at 04:50AM -0800, Nathan Carter wrote:
> The error is this:
> Runaway argument?
> \end {document}
> ! File ended while scanning use of \next.
>
> \par
>
> The same error occurs if I use \newcommand instead of \def. Any tips on
> how I can get past the fact th
On Tue, 26 Feb 2013 at 04:50AM -0800, Nathan Carter wrote:
> The same error occurs if I use \newcommand instead of \def. Any tips on
> how I can get past the fact that I can't make commands that use
> SageTeX?
There's nothing special about SageTeX here; the problem is that you have
an environme
