[IPython-dev] Togglable input cells?

[Benjamin Root]

Hmm, I rather like this idea. It lets me keep the solutions packaged with
the tutorials (which helps students who aren't taking the class), but keeps
them "out-of-sight, out-of-mind". For the %load, can I do relative paths?

Cheers!
Ben Root


On Sun, Jun 22, 2014 at 9:31 AM, Matthias Bussonnier <
bussonniermatthias at gmail.com> wrote:

> What about just having solution in a separate folder and just %load them ?
>
> You can then just "publish" the folder at the end of tutorial, or even at
> beginning.
>
> --
> M
>
>
> Le 22 juin 2014 à 01:29, Aaron Meurer a écrit :
>
> > My advice is to stay low tech. I tried a fancy thing
> > (ipython_doctester) at my scipy tutorial last year, and it was more
> > trouble than it was worth.
> >
> > In this case, just make a separate notebook with solutions. The way I
> > do it is I make the solutions notebook and then when I am done I copy
> > it and clear out the answers.
> >
> > Aaron Meurer
> >
> >> On Jun 21, 2014, at 6:11 PM, Mark Voorhies <mark.voorhies at ucsf.edu>
> wrote:
> >>
> >>> On 06/21/2014 03:46 PM, Benjamin Root wrote:
> >>> I am preparing for my tutorial for SciPy, and I want to avoid making a
> >>> particular mistake I made last year, which was to have an exercise in
> the
> >>> notebook for students to complete, but no "solution" available. I
> thought I
> >>> would just type up the solution live, on-the-spot, but ended up making
> a
> >>> complete fool of myself (it is all on YouTube, too...)
> >>>
> >>> So, I was thinking of some sort of way to toggle an input cell that can
> >>> reveal itself when I want to. I have seen some previous discussions on
> this
> >>> topic, but I am not quite sure if they are what I am looking for.
> Note, I
> >>> am completely clueless on how to add additional features, plugins, etc
>  to
> >>> a notebook, and really am very bad at javascript. Of couse, I am open
> to
> >>> other suggestions that others have done for their tutorials,
> >>
> >> Low tech solution:
> >>  Stage the "hidden" cell content elsewhere (e.g., an emacs buffer) and
> >> paste it in when you need it =)
> >>
> >> --Mark
> >>
> >> P.S. My experience is that if solutions to exercises are available (as
> >> part of a distributed notebook, in slides, on the course website) at
> >> least a few students will jump ahead rather than trying the exercise.
> >> Not necessarily the end of the world, but it gets in the way of seeing
> >> alternate solutions/etc...
> >>
> >>
> >> so long as
> >>> they are documented well, and is easy to distribute to students taking
> an
> >>> introductory course.
> >>>
> >>> Cheers!
> >>> Ben Root
> >>>
> >>>
> >>>
> >>> _______________________________________________
> >>> IPython-dev mailing list
> >>> IPython-dev at scipy.org
> >>> http://mail.scipy.org/mailman/listinfo/ipython-dev
> >>
> >>
> >> _______________________________________________
> >> IPython-dev mailing list
> >> IPython-dev at scipy.org
> >> http://mail.scipy.org/mailman/listinfo/ipython-dev
> > _______________________________________________
> > IPython-dev mailing list
> > IPython-dev at scipy.org
> > http://mail.scipy.org/mailman/listinfo/ipython-dev
>
> _______________________________________________
> IPython-dev mailing list
> IPython-dev at scipy.org
> http://mail.scipy.org/mailman/listinfo/ipython-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.python.org/pipermail/ipython-dev/attachments/20140622/ab3373cc/attachment.html>