Hi,
In case anybody cares, I'm doing a complete rewrite of the Jupyter
frontend client from scratch (and also using nteract's node.js backend
instead of the python backend). Thanks for mentioning some
missing/desired features, e.g., customizability of a "typeset"
checkbox. If anybody else has any wishes, it can't hurt to let me
know.
I hope to use the rewrite to also fundamentally integrate sagews
("sage worksheets" in SMC) with jupyter.
I don't have time to do anything related to politics or bureaucracy,
so if you want to write something like to me, don't bother. If you
have questions, the code is here:
https://github.com/sagemathinc/smc/tree/jupyter/src/smc-webapp/jupyter
-- William
On Tue, Mar 21, 2017 at 7:08 AM, Erik Bray <erik.m.b...@gmail.com> wrote:
> On Tue, Mar 21, 2017 at 1:26 PM, kcrisman <kcris...@gmail.com> wrote:
>>
>>
>> On Tuesday, March 21, 2017 at 7:00:56 AM UTC-4, Eric Gourgoulhon wrote:
>>>
>>> To add on Travis post, some rationale for having default LaTeX typeset
>>> outputs in the Jupyter notebook is
>>> - Jupyter is scheduled to be the default notebook in Sage 8.0
>>> - It is likely that users (especially beginners) who employ the notebook
>>> instead of the console are expecting to have "nice" outputs
>>> - A strength of Sage, as compared e.g. to Mathemetica, is to provide LaTeX
>>> typeset display
>>> - However, currently, one must type "%display latex" in some cell to
>>> trigger LaTeX typesetting; it is very likely that a beginner will miss this
>>>
>>
>> In the Sage notebook sagenb, there was since forever a "Typeset output"
>> button which accomplished this. I know we don't want to fork the Jupyter
>> notebook. But I hope people are seeing why William might have decided to
>> implement sagews beyond ipynb (though I don't know whether that supports
>> this so obviously).
>>
>> However, with regard to this, I don't think the default should be
>> typesetting everything, and I don't think it should be default for "easy"
>> stuff either. There should instead be a very easy obvious way to make this
>> happen that is then amply documented. Preferably not always a percent
>> directive - I am starting to hate those (when they are the only option)
>> because anyone with CLI experience thinks they are obvious, and anyone
>> without it would be hopelessly confused.
>
> I was actually surprised, the first time I used Sage in the Jupyter
> notebook, that it *wasn't* using LaTeX output by default. I think for
> beginners especially there's a certain "wow" factor to that which
> can't be ignored. More intermediate users could change the default
> (though it should be well documented how) in their .ipython
>
> (What I really wish was that there was a display mode that showed the
> plain-text repr and the latex side-by-side though.)
>
> --
> You received this message because you are subscribed to the Google Groups
> "sage-devel" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to sage-devel+unsubscr...@googlegroups.com.
> To post to this group, send email to sage-devel@googlegroups.com.
> Visit this group at https://groups.google.com/group/sage-devel.
> For more options, visit https://groups.google.com/d/optout.
--
William (http://wstein.org)
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at https://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
