#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:44 nkirchner]:
> On OS X Lion, running Sage 5.5 compiled from source.
>
> Notes on lingering process after stopping server:
>
> {{{ ps aux | grep (process id) }}} reveals it's sage-cleaner. The
process persists for at least six hours. I'm looking into this further,
and think it's a separate issue from Sage.app: I had previously observed
that running sage from a terminal did not spawn a lingering process, but
that has changed. Running sage from terminal also creates a sage-cleaner
process.
I agree it's _probably_ a separate issue. But it's often hard to tell.
> About the opening of files:
>
> On opening up documents by double clicking or right-clicking and
selecting Open With..., I have found that compressed .sws (.sws.zip) files
do not open. Text files open fine... I had the enigmatic title "{{{id=9|"
in my test case, but all the cells imported just fine. Compressed text
(.txt.zip) does the same thing as non-compressed text.
>
> Opening with .sws format also preserves output cells, including
graphics. Opening .txt files preserves non-graphical output cells.
Uploading like this should work exactly like uploading from the interface.
I would have thought that `.sws.zip` files would work, but I can't swear
that I tested it. I will do it later tonight.
> One issue I came across with the opening of files: With Sage.app
running, but the server not active, opening a .txt file via Open With...
-> Sage.app did not work. I resolved this by noting that my sage.log
complained "Worksheet admin/xx does not exist". Deleting the
~/.sage/sagenb.../admin/xx folder fixed the problem and the text file
opened fine.
I have seen this before (complaining about worksheets not existing). I
don't know if it's related to Sage.app (I suspect not), but I haven't been
able to replicate it reliably. If you have a replication path that would
be great (and probably a separate trac ticket).
After you deleted that, were you able to open the text file with the
server not active?
> Otherwise, when instructing Sage.app to open files, it does not matter
whether the server is running, or Sage.app is running. Sage.app will open
and start the server as necessary and open up the files.
Excellent.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11026#comment:45>
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.
