> PS: The final step in the whole saga would be to use Interface Builder > to make, well, an interface (which presumably would just add some kind > of Aqua niceness to a terminal session implanted in the interface?). > I have no idea how to do this, but > http://www.iwu.edu/~cskiadas/Apps/index.html > is an older example of doing this with Macaulay 2 which as far as I > know was fairly functional. Anyway, that would be suh-weet.
I don't know if we could make Platypus <http://www.sveinbjorn.org/platypus > part of the build process, but it's very nice and can easily integrate into a command-line build process. It creates the bundle and everything for you. It's GPL, if it helps. I would have suggested this a lot sooner, but just starting the sage server isn't that exciting to me. What I want is a dedicated application (like the Macaulay front end), but one that opens a browser window instead of a terminal. What I use is a hacked up version of a Site Specific Browser created with Fluid <http://fluidapp.com/> that starts the server in the background and opens a browser window. Unfortunately, Fluid is closed source, but something like Prism might work. It's been a while since I looked at Prism, so it might suck less now. I could never even figure out how to begin to build it (and the forums were no help despite several people asking the same question--Argh!). Anyway, if I have some time (not likely in the near future) I will look into a Prism application, or creating an SSB from scratch to use with sage. It really shouldn't be that hard, but my Cocoa skills aren't that great. Either that or I might try and add browser windows to Platypus. -Ivan --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-devel@googlegroups.com To unsubscribe from this group, send email to sage-devel-unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
