On Fri, Mar 28, 2008 at 4:31 PM, Marshall Hampton <[EMAIL PROTECTED]> wrote: > > I added a page to the wiki for coordinating @interact suggestions, and > linked to it from the demo page: > > http://www.sagemath.org:9001/interactSuggestions > > I am still figuring out what I can do, what I can work around, and > what is a real problem, so I think it is too early to start making > trac tickets. The demo page has helped me a lot. Hopefully more > people will add to it and we can get some consensus on what needs to > be done next.
Exactly! It's really worth playing a lot with what we currently have in order to see what to do next. I'm doing the same. Once things crystalize we can make several tickets laying out the next steps. > So far I have been able to work around the issue raised above, but it > has required some extra thought and redesign. > Yep. And I think often the redesign results in one making a somewhat different GUI/application than originally planned. I just made something like Matlab's funtool (which I've never used -- I just saw a picture in a book): http://wiki.sagemath.org/interact#head-16e9c0180afb4f04813e76ab5685ef8b68e4ee8c It came out much different than expected because of some of the constraints of @interact. That said, the result is actually pretty pleasing and _straightforward_ to use, which is a good thing. One thing we'll definitely have to deal better with is recovering from crappy input or computations that take a long time. Currently recovery is not good enough... -- William --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
