> > Or is something else what happens? > > > +++ > > > The reason I ask is that I had multiple requests about the single-cell > > at the Joint Meetings table, and in particular this issue of > > persistence came up for one gentleman (Jason, I think you spoke with > > him too). I strongly suspect that some of the other users of the > > single-cell wouldn't mind this, either, though their uses are more > > amenable to the once-off computations. But if we had some really > > clear documentation for how to "simulate" persistence in the way Ivan > > is, that could be very useful - for instance, Volker's Android app > > could probably use it (?). > > The only thing the iPhone app (currently) does is save the text input and > output (as well as images). So if you want A+1, you copy the cell and add > A+1 to the end (or you edit the cell and add A+1 to then end) and then run > the whole computation over.
Oh, this makes a lot more sense. > It's not ideal in many ways, but it makes it very easy for quick computations > and if you want to do more complicated things you should probably be using a > notebook IMHO. I guess you could say that I save notebooks which have a > limit of one cell. It would certainly be possible to add multiple cells, but > if I do that then I think we should just use the notebook (making whatever > improvements are necessary for use on mobile devices). Which is a different project, of course. Thanks for the clarification! -- To post to this group, send an email to sage-devel@googlegroups.com To unsubscribe from this group, send an email to sage-devel+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
