Dear Simon, dear thematic tutorials lovers

On Sat, Jun 11, 2011 at 12:19:59PM -0700, Simon King wrote:
> At http://www.sagenb.org/home/pub/2813, I have published a worksheet
> that aims at explaining how one can implement a new parent and take
> advantage of both the category framework and the coercion model
> (including construction functors).

Thanks!!!

> In another thread, I suggested to proceed with documentation similar
> than with spkgs: I believe that it is better to make preliminary
> versions of tutorials available to the public (explicitly marking them
> as preliminary or draft) than to wait a couple of months until someone
> has provided a full review. In the best case, there is feed-back from
> the public, so that one has a cumulative review.
> 
> In particular, I think that the tutorials from the combinat branch
> should be published soon as well.

Yes, they should!

Up to recently, there had been two obstacles:

 - Some sphinx technicalities (cross documentation links, ...) which
   Florent et al. now solved, and should be in Sage now or soon.

   In particular, I wanted to thematic tutorials in the reference
   manual whenever meaningful. E.g. put the main combinatorics
   tutorial in sage.combinat.tutorial.

   Benefits:
    - One can do ``sage.combinat.tutorial?``
    - It's close to the relevant code!!!
      In particular it get tested when one does sage -t sage/combinat/
    - This avoids a few little technical discrepancy between
      doctests in rst and in .py files

 - They were far too immature; the way we wrote them was to present
   baby versions of them live during Sage days, then see how the
   participants reacted, and iterate. Now most of them have been
   through this cycle at least 3-4 times, and in the last Sage days in
   Wolfville we were mostly just saying "go to that web page, choose
   your tutorial, and ask for help" (except for the very first tutorials).

So now, many of our tutorial should indeed just go into Sage. There is
a tiny bit of work to:

(1) Decide which tutorials are ready to go
(2) Unfold the tutorials in separate patches (they currently are all
    in the sage-demos-and-tutorials-nt.patch in the Sage-Combinat
    queue)
(3) Check each of them, and see that there are no non trivial
    dependencies with other things in the queue
(4) Proofread and review.

I won't have time to work on this in the next weeks. Volunteers are
most welcome to take over the patch and start working on the above.

> Namely, it seems to me that the pedagogical approaches behind these
> texts and my text are orthogonal.  Having both available would give
> the user the opportunity to benefit from what fits better to his or
> her respective learning type.

As long as we have the manpower to maintain both, that's fine with me!

Cheers,
                                Nicolas
--
Nicolas M. ThiƩry "Isil" <nthi...@users.sf.net>
http://Nicolas.Thiery.name/

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Reply via email to