#11026: Add double clicking of sws files for Mac app
----------------------------------+-----------------------------------------
Reporter: iandrus | Owner: iandrus
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-5.6
Component: user interface | Resolution:
Keywords: mac app | Work issues:
Report Upstream: N/A | Reviewers: Karl-Dieter Crisman
Authors: Ivan Andrus | Merged in:
Dependencies: #8473, #13121 | Stopgaps:
----------------------------------+-----------------------------------------
Comment (by iandrus):
Replying to [comment:42 nkirchner]:
>
> I'm on OS X Lion.
>
> This patch does start and stop the server. Starting the server
initializes three python2.7 processes. Two of them are ~100MB and one is
~5MB. Stopping the server or exiting Sage.app terminates the two larger
of these, while leaving the ~5MB python2.7 process running. This last
running process is a problem for deleting/renaming Sage.app, and does not
go away on its own.
I think that is a sage-cleaner process, and it _should_ go away. You can
check what process it is by running in a terminal
{{{
ps aux | grep PID
}}}
where you can get the PID from Activity Monitor (left most column).
Does this happen every time you start the server, thereby accumulating a
new process every time?
> Telling Sage.app to start a terminal session also spawns a ~5MB
python2.7 process which persists after exiting both that terminal session
and Sage.app.
When I open a terminal session, I only see one python2.7 process, using
about 113MB of memory. After exiting the session the process terminates.
Maybe there is something about your system that causes sage-cleaner to
hang around, or perhaps the difference is due to different Sage versions.
What version are you using? I'm actually still using 5.4.rc2 with some
patches e.g. for new ipython.
> Right-clicking a .txt file and selecting Sage.app to open it results in
the text of the file being placed above the first input cell without
linebreaks. That is, a text file consisting of
>
> """Hello. I'm a[[BR]]
> sample text file in Sage.app"""
>
> ends up being opened with the text "Hello. I'm a sample text file in
Sage.app", with the first input cell following the text. I've not yet
tried it with a proper text Sage worksheet.
Cool.
> Double-clicking a .sws file saved via Sage.app's File->Save As menu does
activate Sage.app. It pulls up an error page:
>
> "There was an error uploading the worksheet. It could be an old
unsupported format or worse. If you desperately need its contents contact
the sage-support group and post a link to your worksheet. Alternatively,
an sws file is just a bzip2 tarball; take a look inside!"
This is because the `File -> Save As` doesn't work. I have already
removed it in another patch. Sadly, it touches a nib file (which are
virtually unmergeable) so I would rather not add that same change here
since all further changes would have to be rebased.
> Instead using the in-browser's File->Save worksheet to file... does not
appear to save anything.
I have opened #13931 for this.
> Using Firefox instead, I can save an sws file and open it by double
clicking. I'm testing this functionality further right now.
Awesome. Thanks.
For reference, some of this discussion also took place on the
[https://groups.google.com/forum/?fromgroups=#!topic/sage-
devel/HHiXD0NGec0 mailing list].
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11026#comment:43>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
