Live renderer for markup cells

[dpsanders]

Add a pop-out window with a live rendering of the current markup cell.

This exists out there so should be easy for someone with moderate javascript skills (i.e., not me):

http://rst.ninjs.org/

[minrk]

What do you mean by this? There are no markup cells, and the main markup we might add (hopefully not) is reST, where cell-at-a-time render doesn't make sense.

[dpsanders]

I mean that in principle I don't see any reason to exclude somebody's
favourite markup language as an option. So there would just be a 'markup
cell' type, with sub-types for different markup languages

On Sun, Jul 21, 2013 at 12:53 PM, Min RK notifications@github.com wrote:

What do you mean by this? There are no markup cells, and the main markup
we might add (hopefully not) is reST, where cell-at-a-time render doesn't
make sense.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/3715#issuecomment-21313920
.

Dr. David P. Sanders

Profesor Titular "A" / Associate Professor
Departamento de Física, Facultad de Ciencias
Universidad Nacional Autónoma de México (UNAM)

dpsanders@gmail.com
http://sistemas.fciencias.unam.mx/~dsanders

Cubículo / office: #414, 4o. piso del Depto. de Física

Tel.: +52 55 5622 4965

[minrk]

I mean that in principle I don't see any reason to exclude somebody's favourite markup language as an option.

We very specifically do not want to do this kind of thing. There is actually a huge cost in supporting each additional markup language beyond zero.

If you want markup of your choice, you can today use a raw cell - this adds zero complexity to our obligations, because raw cells are untransformed as they pass through nbconvert (there is one piece missing, and that is using metadata to specify the output type, so it will be simply excluded from other output formats).

[dpsanders]

OK, I see, thanks.

[dpsanders]

OK, I see.

But would a live rendering popout be acceptable / desirable (/ possible) ?

On Sun, Jul 21, 2013 at 1:08 PM, Min RK notifications@github.com wrote:

I mean that in principle I don't see any reason to exclude somebody's
favourite markup language as an option.

We very specifically do not want to do this kind of thing. There is
actually a huge cost in supporting each additional markup language
beyond zero.

If you want markup of your choice, you can today use a raw cell - this
adds zero complexity to our obligations, because raw cells are
untransformed as they pass through nbconvert (there is one piece missing,
and that is using metadata to specify the output type, so it will be simply
excluded from other output formats).

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/3715#issuecomment-21314162
.

Dr. David P. Sanders

Profesor Titular "A" / Associate Professor
Departamento de Física, Facultad de Ciencias
Universidad Nacional Autónoma de México (UNAM)

dpsanders@gmail.com
http://sistemas.fciencias.unam.mx/~dsanders

Cubículo / office: #414, 4o. piso del Depto. de Física

Tel.: +52 55 5622 4965

[dpsanders]

An alternative, rather interesting idea:

Have the output placed to the right of the input cell.
I will open an issue for this.

On Sun, Jul 21, 2013 at 2:50 PM, David P. Sanders dpsanders@gmail.comwrote:

OK, I see.

But would a live rendering popout be acceptable / desirable (/ possible) ?

On Sun, Jul 21, 2013 at 1:08 PM, Min RK notifications@github.com wrote:

I mean that in principle I don't see any reason to exclude somebody's
favourite markup language as an option.

We very specifically do not want to do this kind of thing. There is
actually a huge cost in supporting each additional markup language
beyond zero.

If you want markup of your choice, you can today use a raw cell - this
adds zero complexity to our obligations, because raw cells are
untransformed as they pass through nbconvert (there is one piece missing,
and that is using metadata to specify the output type, so it will be simply
excluded from other output formats).

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/3715#issuecomment-21314162
.

Dr. David P. Sanders

Profesor Titular "A" / Associate Professor
Departamento de Física, Facultad de Ciencias
Universidad Nacional Autónoma de México (UNAM)

dpsanders@gmail.com
http://sistemas.fciencias.unam.mx/~dsanders

Cubículo / office: #414, 4o. piso del Depto. de Física

Tel.: +52 55 5622 4965

Dr. David P. Sanders

Profesor Titular "A" / Associate Professor
Departamento de Física, Facultad de Ciencias
Universidad Nacional Autónoma de México (UNAM)

dpsanders@gmail.com
http://sistemas.fciencias.unam.mx/~dsanders

Cubículo / office: #414, 4o. piso del Depto. de Física

Tel.: +52 55 5622 4965

[minrk]

it might be possible, but should be done through a third-party extension, and not as a part of IPython proper.

[dpsanders]

nvALT has an live renderer for MultiMarkdown, an enhanced version of Markdown with support for footnotes, citations etc. Could we support MultiMarkdown instead of just plain Markdown (if that's what it is) in a Markdown cell?