On Thursday, August 1, 2019 at 7:15:27 PM UTC-5, Jason Grout wrote: > > This looks really cool! > Thanks. Glad you think it has potential. For me it solves a serious problem with convincing non-programmers to try Jupyter for simple things, because it flattens the learning curve for producing notebooks containing instructions for our students.
> > I would suggest that if at all possible, you work within the existing > notebook format and not introduce a new cell type. There is a massive > amount of momentum behind the notebook format as it stands. > >> >> I am not sure it is possible. The WYSIWYG cell is an extension of the basic cell type not the textcell (e.g. markdown). This means a new cell type had to be defined, so that it would be interpreted properly. Presently, the cell data is stored as a wordprocessor-like 'delta' json object. At best, I can imagine a way to store the data as raw html to maintain the formatting, but that would generate more overhead when loading a notebook (still, this might make issues with nbconvert simpler to address). All that said, the extended notebook format is the addition of a new cell type to the present format, so can read the present format, with zero issues. Going back the other way is more of an issue. It is probably best to convert the new cell type to html code cells or raw nbconvert cells with html content when going backwards. We are definitely struggling with the back conversion issue. Jonathan -- You received this message because you are subscribed to the Google Groups "Project Jupyter" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/d0340d82-2f3a-48e7-ad1d-ee2c54cd0104%40googlegroups.com.
