Platypus has been discussed a number of times before, including by Ivan: http://groups.google.com/group/sage-devel/browse_thread/thread/86b087a2fb157678 http://groups.google.com/group/sage-devel/browse_thread/thread/647f9610f161f2fd http://groups.google.com/group/sage-devel/browse_thread/thread/a6b8dced9953074e http://groups.google.com/group/sage-devel/browse_thread/thread/c181f8ccde549cdd
I have been spectacularly unsuccessful with Platypus, but it certainly sounds like others have been able to get it working. Anyway, it sounds like what mabshoff really needs is just the best tarball possible to then be able to drop a Sage build into for a fully functional .app bundle. If that was created just once with Platypus by someone else, presumably for every new Sage release the new binary could just be dropped into the bundle. My own bundle is very bare-bones - so for instance the suggestion above about "open -f Terminal.app $location/sage" might make it better. If someone sent mabshoff one that supported things like knowing whether Terminal was already open, whether a Sage process was already running, being able to drag-and-drop .sws or .py or .sage files (contextually knowing whether to open the notebook!) that would be even sweeter! But it sounds like (correct me if I'm wrong) the thing which has held this up lo these many months and threads is just having something that could be fully automated, needing no additional effort other than slapping a new binary in or perhaps changing a version number, which a script could do. - kcrisman --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
