Timeline for How to have an Input cell that doubles as an Output
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:55 | history | edited | CommunityBot |
replaced http://mathematica.stackexchange.com/ with https://mathematica.stackexchange.com/
|
|
| Jan 3, 2016 at 8:59 | comment | added | Kuba |
What is LargeOverviewMouseover? p.s. what about a new styles, where input-like has Input options in Working environment + is invisible in e.g Slideshow. And which produces Output-like cell which is visible in Slideshow (may or may not be seen in Working, depends what you like).
|
|
| Jan 1, 2016 at 11:26 | history | tweeted | twitter.com/StackMma/status/682885645149310977 | ||
| Dec 31, 2015 at 19:44 | comment | added | John Fultz | Another possibility is the use of a template notebook to generate the notebook you wish to redistribute. The template notebook does exactly the sort of transformation (output replacing input) that you describe, but as part of a deployment step rather than an interactive widget like the one you describe. If the non-interactive, deployment-based approach is appealing to you, I could write it up as an answer. | |
| Dec 31, 2015 at 19:42 | comment | added | John Fultz | Sometimes people ask questions which, even if properly and successfully answered, wouldn't represent the best solution to the actual problem they're experiencing. That's why I want to understand your problem, and why one existing solution to that problem was not sufficient for you. Given your problem, I would have gravitated toward a tagging-based solution...perhaps to the end of automatically reverse-closing the appropriate cell groups. It's unclear from your description whether you would find such a solution adequate and, if not, why not. | |
| Dec 31, 2015 at 9:55 | comment | added | P. Fonseca | @JohnFultz That's why I insisted with the stylesheet solution, because if there was a way to create a style that acted like that, it wouldn't feel odd, and the nb writer would just need to choose the input cell formatting as (standard) input or hybrid. From then on, no need to keep track of what would need to be closed or opened, etc. and WYSIWYG. But thank you for your comment, since, if you say it would be like reinventing the interface, then, I guess that is answered... and I thank all the answers for their imaginative tries, that for sure revealed interesting ways of text cells inline code | |
| Dec 31, 2015 at 9:48 | comment | added | P. Fonseca | @JohnFultz Imagine I have a 700 pages notebook (I have several of them). Many of the input should be printed as a report, but most of them do not need to show. I've been finding it difficult to keep track of this, either with the reverse-closing, or with hiding. A tagging system with some automatic parsing should be possible (for hiding, it's easy, but formatting is not great, deleting on duplicated nb is slow and odd). But I was wondering it there was some sort of hybrid cell type possible. Yes, from the answers, it does fill like reinventing the interface. But asking doesn't hurt... Right? | |
| Dec 31, 2015 at 0:51 | comment | added | John Fultz | I would have thought that the ability to close a cell group, alternatively on the Input cell or reverse-closing on an Output cell, would have been pretty close to what you're looking for without trying to invent a new interface. Certainly I see reverse-closing as a very common way of hiding implementation in notebooks. | |
| Dec 30, 2015 at 14:46 | answer | added | Edmund | timeline score: 3 | |
| Dec 30, 2015 at 14:34 | history | edited | P. Fonseca | CC BY-SA 3.0 |
added 161 characters in body
|
| Dec 30, 2015 at 13:38 | history | asked | P. Fonseca | CC BY-SA 3.0 |