#11026: Add double clicking of sws files for Mac app
----------------------------------+-----------------------------------------
Reporter: iandrus | Owner: iandrus
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-5.3
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:37 kcrisman]:
> Okay, I did a bunch more testing on this box. It works fine but
''very'' slow as long as you start Sage.app first. I have more trouble if
I do the click first - it seems to start two servers and gives errors.
This is a reproducible sequence.
> {{{
> Traceback (most recent call last):
> File "/Users/crisman/Desktop/sage-5.2.beta0/local/bin/sage-notebook",
line 36, in <module>
> notebook(port=8000)
> File
"/Users/crisman/Desktop/sage-5.2.beta0/devel/sagenb/sagenb/notebook/notebook_object.py",
line 206, in __call__
> return self.notebook(*args, **kwds)
> File
"/Users/crisman/Desktop/sage-5.2.beta0/devel/sagenb/sagenb/notebook/run_notebook.py",
line 434, in notebook_twisted
> return run(port)
> File
"/Users/crisman/Desktop/sage-5.2.beta0/devel/sagenb/sagenb/notebook/run_notebook.py",
line 419, in run
> raise socket.error
> socket.error
> }}}
> Once this happens, then subsequent login attempts cause me to have to
log in to get to see the sheets.
What if you quite Sage.app and start it again. Does it recognize that a
server is running? Is one running? If quitting stops both servers, then
try holding Option when you quit to not kill the server and see if
Sage.app recognizes the server then.
What happens (i.e. does it work okay) if you start the server yourself
from the command line, and then double click a sws file (without Sage.app
being open)? Does 5.2.beta0 use the new notebook?
> So we ''could'' add a very careful set of instructions to try to warn
people to avoid this situation. I mean, it ''does'' work. Just not
ideally.
I'd like to get this fixed since it's supposed to work, but I guess it
depends on how long we have to wait for me to fix it. It's not going into
5.2 though so we have some time. I can't reproduce the problem so it
might be a timing issue. I'll try to look at the code and see if I can
figure it out.
> ----
>
> By the way, switching my default browser to the Sage.app one worked fine
:)
You mean, that you don't see the above problems, or just that it works in
other ways?
> ----
>
> I'm going to try the
> {{{
> #import <Foundation/Foundation.h>
> }}}
> trick now in a rebuilt app and see what happens.
>
> Didn't seem to help; I got the same
> {{{
> /Users/crisman/Desktop/sage-5.2.beta0/data/extcode/sage/ext/mac-
app/AppDelegate.m:189: warning: (Messages without a matching method
signature will be assumed to return 'id' and accept '...' as arguments.)
> }}}
> and the sleep warning, twice each. Would it matter where I put that
import in the top few lines? I tried it at the end and the middle, same
thing both times.
No, where you put it shouldn't matter.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11026#comment:38>
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.
