>> I think this could be an exciting way to get all the java applet >> makers out there interested in sage, although I don't completely >> understand the architecture of what this is supposed to do. > > Wouldn't a Java applet imply that the functionality it provides could only be > accessed via Sage's web interface? > > I would like to establish some (roughly) like this: If a computation cannot be > expressed from the command line (in pure Python) then it cannot be a standard > part of Sage. E.g. if you cannot compute $sin(x)$ for some $x$ from the > command line but you can do it by clicking some Java buttons, then this > functionality would not be considered a part of (standard) Sage. > > Would that make sense? > Martin
No, that makes no sense at all. First off, I don't see this as a danger. Second, interactive widgets are pretty frikkin' sweet -- you should have seen the stuff high school kids were doing with Manipulate in Mathematica at the joint math meeting. The notebook already has a number of features that the commandline doesn't. Why do you feel the need to "freeze" the interface of Sage so it can never grow past the commandline? That's Matlab's approach, and I think their interface sucks. --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@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-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
