On Mon, Jun 21, 2021 at 10:08 AM john_perry_usm <john.pe...@usm.edu
<mailto:john.pe...@usm.edu>> wrote:
Hello!
> Is this also published on CoCalc?
Not at the present time. I do mean to talk to someone about it.
Just make a PR to
https://github.com/sagemathinc/cocalc-examples
<https://github.com/sagemathinc/cocalc-examples>
and we'll happily host a copy. This makes it so with a click, people
can quickly get a copy of the document...
> Why do you prefer the use of Sage Worksheets over Jupyter Notebook?
I'm not entirely clear on when "Sage Worksheets" became Jupyter
notebooks. I think, when we started 5 years ago, that we weren't
aware of the switch; I certainly wasn't. I personally haven't
looked enough into the details and/or differences to write
intelligently about them.
Sage worksheets = a way of using Sage in Cocalc *ONLY* that involves
a single codemirror editor document, and a really powerful way to
easily define %mode's. It's very tightly integrated with Sage. It's
also written in a pretty old style (using a lot of html and jquery),
and I plan to rewrite it soon, since it's one of the only things left
in CoCalc that isn't written in Typescript/React. Sage worksheets
are implemented entirely separately from the Jupyter stack, not even
using the Jupyter kernel for Sage (instead, they have their own
backend server process, which uses fork each time you make a new
connection, for faster startup). They do have a way to easily create
any number of connections to different Jupyter kernels, and use them
all in the same worksheet. I wrote Sage worksheets mainly
2012-2014, and have maintained them ever since, because they are
pretty popular on CoCalc, e.g., they just use a normal single
document editor interface, rather than a "weird" modal interface with
many little editors like Jupyter notebooks, and some people find the
Sage worksheet approach more natural.
One nuisance of Sage worksheets is that the exact version of Sage
isn't specified anywhere in the file format -- it just uses whatever
"sage" is in your path. Jupyter is better in this regard.
Jupyter notebooks = of course we all know what they are.
I'm personally a huge fan of both, but they are very different. I
hope I can unify the two approaches sometime soon, so that there's a
mode for using any Jupyter notebook that looks like a Sage
worksheet... and so the custom Sage server mentioned above is just a
different Jupyter kernel (maybe called "cocalc-sage").
john perry
On Sunday, June 20, 2021 at 1:15:28 PM UTC-5 ingo...@gmail.com
<mailto:ingo...@gmail.com> wrote:
That looks great and I am looking forward to reading it more
in detail. Just two quick questions to get started.
Is this also published on CoCalc?
Why do you prefer the use of Sage Worksheets over Jupyter
Notebook?
Best wishes
Ingo
john_perry_usm schrieb am Sonntag, 20. Juni 2021 um 02:58:57
UTC+2:
Greetings
Five years ago, a couple of colleagues and I began
writing a Sage-based textbook to serve a class we teach
at our institution. When we announced it to Sage users,
we received an encouraging reception and excellent
feedback. If that was meant to discourage us, it failed
completely. ;-)
We've updated it pretty regularly since then, correcting
a lot of errors and adding a few new features, even
updating to Python3. The sources have been available
online for a while, but after half a decade it seems time
to get a little less behind the times than we have been
and move the entire project to GitHub. So, here you go:
https://github.com/johnperry-math/mew_cats
<https://github.com/johnperry-math/mew_cats>
A new PDF version is included as a "Release", so you
don't have to clone it, let alone build it. (Look for
"Releases" on the right.) The license is CC-BY-SA, so
feel free to clone it, fork it, commit it, push it, and
any other unethical-sounding VCS operation that suits
your fancy. You can even introduce errors that we haven't
already included!
To honor the occasion we changed the title. Two of the
authors are very pleased with the acronym.
We hope people find this useful for teaching, learning,
and using Sage. People besides us, that is. :-)
regards
john perry
--
You received this message because you are subscribed to the
Google Groups "sage-support" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to sage-support+unsubscr...@googlegroups.com
<mailto:sage-support+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/sage-support/da1bcc45-970b-4b66-afad-287254637330n%40googlegroups.com
<https://groups.google.com/d/msgid/sage-support/da1bcc45-970b-4b66-afad-287254637330n%40googlegroups.com?utm_medium=email&utm_source=footer>.
--
-- William Stein
--
You received this message because you are subscribed to the Google
Groups "sage-support" group.
To unsubscribe from this group and stop receiving emails from it,
send an email to sage-support+unsubscr...@googlegroups.com
<mailto:sage-support+unsubscr...@googlegroups.com>.
To view this discussion on the web visit
https://groups.google.com/d/msgid/sage-support/CACLE5GDP9FrZQXEQWnaTbwr9%3D2B%3D8kBSHN4DMNQodxquW6vKmg%40mail.gmail.com
<https://groups.google.com/d/msgid/sage-support/CACLE5GDP9FrZQXEQWnaTbwr9%3D2B%3D8kBSHN4DMNQodxquW6vKmg%40mail.gmail.com?utm_medium=email&utm_source=footer>.
