On Jan 31, 2012, at 2:56 PM, Jason Grout wrote: > On 1/31/12 5:27 AM, Ivan Andrus wrote: >> On Jan 31, 2012, at 11:15 AM, Jason Grout wrote: >>> On 1/31/12 2:16 AM, Ivan Andrus wrote: >>>> I want to wait a few days to get any more bug reports and then >>>> I'll push another version (say, Friday) fixing this and anything >>>> else not too major. Of course it will take a few days to get >>>> through the review process, but I'm hoping it's faster the second >>>> time around. >>> >>> Great work on this! If you're looking for small things to fix, >>> here is one: can the default computations that come with the app >>> not have errors as the top two computations (or maybe not have >>> errors at all in the saved computations)? >> >> Hmm. That was deliberate so that people would see what errors looked >> like, but maybe that's not important. > > I figured, but I could also see it be a little unnerving to see that the top > two computations were "mistakes", when it looked like there should have been > a library of cool computations I could modify.
Yes, I can definitely see that now. :-) On a related topic what other cool (but short) examples should be included? For example, I would like something from number theory (about which I know nothing), and maybe an ODE or something. A few to show off the breadth of Sage. >>> This is a bigger issue: when I type in a computation, I'm in the >>> full screen mode (i.e., the one computation is taking the full >>> screen, with its output. How do I stay in that mode when I submit >>> the computation? All I see is the Done button, which takes me back >>> to the index listing. I then have to click on the computation >>> again to examine the output. It'd be great if I could stay in that >>> single-computation full screen, and maybe just have a "+" button to >>> make a new computation, which would clear the screen and let me >>> input another computation. The only time I would go back to the >>> index screen is to look at the history of computations. >> >> That's a good point. I'll see if I can fix that. I wasn't sure how >> to do that many things in the interface, but there has to be a way. > > Great! I hope it's not hard, but I have no idea. We'll see. I already have a few ideas. >>> Also: is it easy to make an ipad version? I don't know how easy it >>> is to scale up from an ipod version. >> >> I don't know. I haven't really looked into that yet. I think mostly >> it's a matter of creating the interface. The "problem" is that the >> interface is so spartan right now I'm not sure how to "fill up" an >> iPad without looking silly. :-) It's definitely on my list of things >> to think about though. I'm also not familiar with what other iPad >> applications do since I don't have one. >> > > The Sage output would fill up the ipad just fine in the single-cell screen. > Just a plain textbox at the top and leave all the rest of the room for the > command output. We could spice it up later, but that itself would make it > much more usable on the ipad. As for the index, just showing more index > entries would be great. That sounds like it should be easy then. -Ivan -- To post to this group, send an email to [email protected] To unsubscribe from this group, send an email to [email protected] For more options, visit this group at http://groups.google.com/group/sage-devel URL: http://www.sagemath.org
