> I'm certainly not a mac expert. However, I got Sage working through a
> mac-like icon using the Platypus program (http://www.sveinbjorn.org/
> platypus). There's a good article here (http://www.tuaw.com/ 
> 2007/05/08/
> platypus-create-mac-binaries-from-ruby-perl-shell-scripts-et/) about
> how to use the program here. But it's kinda nice. Among other
> programs, the Gimp.app program uses Sage for it's Mac application
> bundle.
>
> and had Platypus run it, putting the output into a text window. This
> runs the notebook() function and the twisted server, and pops open the
> browser with the Sage notebook.

I have actually taken a slightly different approach, in that I used  
Fluid.app <http://fluidapp.com/> to create a site specific browser  
that also starts Sage.  This means that Sage is a "real application"  
that I can Cmd-Tab between etc.  Can Platypus does this?  If not it  
probably could (I may look into it).  Frankly, I hate using Sage in a  
browser, because it is mixed in with all my other browser windows.    
For me a separate application is the only acceptable long-term solution.

There are a few problems with my Fluid-based app currently.  One is  
that Fluid tacks on '.com' to the URL for local addresses.  That  
certainly means it's not ready to be released to end users.  There is  
also a certificate issue, but I assumed that was my fault for running  
the sage server wrong.  There is also a potential licensing issue.   
Fluid is closed source, and I don't know how applications built with  
it can be distributed.

If you are interested I would be more that happy to tell you more/send  
you what I have.  It's at a very early stage and I haven't worked out  
the problems, but since you brought it up, I thought I would mention  
what I have done.

> The drawback is that the script needs to know the path to my sage
> installation. I think that the workaround to this is to actually put
> the entire Sage installation in the folder that Platypus creates for
> the application. OS X applications on the Mac are actually folders
> (unix directories).

That's the solution that I was considering as well.  We could just  
distribute binary versions as regular applications.  The only  
(potential) problem that I see it that notebooks should be stored in  
some place that will be saved across upgrades/new installs.  This  
shouldn't be hard to fix though.

> Does this sound like it would be useful to the Sage community if I
> could get it working?


+1

-Ivan Andrus

--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to