Dear Marcin,
I have been meaning to reply to your earlier post about inserting code
blocks. The short answer is that if you put
\begin{sageverbatim}
\end{sageverbatim}
in your latex source, you should get an empty compute cell in the
resulting worksheet created by tex2sws.
Long answer is that I am doing a lot of work on tex2sws this month and
so I am uncertain what is working with the current BitBucket version
and what I have hacked up locally (including the "advice" just
above). I have a temporary patch that I could share off-list, which
will support the sageexample environment, plus I have rewritten that
to work properly (not sure if it ready to commit or not). The
temporary should be enough to get doctesting too, I think.
I have also been working on a "Author's Guide" with lots of
explanation and advice about the workflow, but it too is evolving. I
have hacked SageTeX brutally to get PDF output that I like (which does
not affect worksheet generation) - that is less ready-to-go. I am
going to wrap up my work on Judson's abstract algebra text in the next
few workdays, then will work to polish up tex2sws and associated
documentation, which is all working quite well since my two big
textbook projects exposed some areas for improvement. So let me know:
I want it now, send me some hacked patches off-list,
or
I can wait a couple weeks for something easier and polished,
and we can go from there.
Thanks for your interest,
Rob
On Aug 5, 4:54 am, Marcin Kostur <marcinofu...@gmail.com> wrote:
> Dear Rob,
>
> How did you generate the sageblocks in your sws version of the book?
> I assume sageexample in sagetex + tex2sws.
>
> I need a reasonable workflow for authoring materials, which should
> generate sage worksheets and pdf.
> Sageexample with doctesting would be ideal....
>
> The best
>
> Marcin
>
> On Aug 4, 12:59 am, Rob Beezer <goo...@beezer.cotse.net> wrote:
>
> > (Cross posted - just to intensify the "list condensation" discussion
> > on sage-devel.)
>
> > I may sound like a broken record, but my "add Sage to my linear
> > algebra textbook" project is now really in a final cleaned-up form.
> > I've moved distribution to the book web site, and will add the
> > material to my production script in the next couple weeks. Right now
> > there is a PDF of just new content (for the idly curious, or for
> > bedtime reading), plus a zip file of the entire book as Sage
> > worksheets with the new material present as code cells. Be sure to
> > read about a few caveats if you pick up the worksheet version.
>
> >http://linear.ups.edu/sage-fcla.html
>
> > By the Numbers:
>
> > ~45 Sage patches
> > 95 new subsections
> > 279 "sageexample" environments
> > 1330 outputs doctested
> > 12.6 seconds for full doctesting
>
> > As any developer knows already, being able to doctest your work saves
> > you from many silly little misteaks.
>
> > A handful of patches remain to be reviewed and merged,
> > seehttp://wiki.sagemath.org/devel/LatexToWorksheetifyou can help.
>
> > Similar project for Judson's abstract algebra textbook should be done
> > in a week or two.
>
> > After these associated stress-tests, I'll clean-up and document the
> > tool chain I've used to do this.
>
> > Rob
>
>
--
You received this message because you are subscribed to the Google Groups
"sage-edu" group.
To post to this group, send email to sage-edu@googlegroups.com.
To unsubscribe from this group, send email to
sage-edu+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/sage-edu?hl=en.
