#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:30 kcrisman]:
 > > I mean that when I right-click and choose "Open With" that for zip
 files Sage is in the list, for txt files it isn't.  Obvious for sws files
 it is.  But one can still surf through the mini-Finder window and use
 that, or drag a text file onto the Sage in the Dock (well, I didn't try
 that, and right now I definitely can't).
 >
 > I still get a little flakiness opening txt files.  It did work once or
 twice.  Dragging onto the Dock Sage doesn't work.

 That should be fixed now.

 > > > > Changing the default browser works in that it opens and it tries
 to get localhost, but it asks for password and of course I haven't got a
 clue, since it usually just logs in.  This happened in both FF and Chrome.
 > > >
 > > > Hmm.  I can't reproduce this with Safari.
 > >
 > > That's my point.  In Safari it's fine, but go into Safari prefs and
 change the default browser to FF or Chrome, and they don't auto login when
 you click on a sws file.  (That might even be the case without the double
 click, just when opening Sage - I didn't think to check that.)
 >
 > I can confirm that
 >  1. Changing the default browser while the Sage app server is running
 >  1. Trying to use Sage.app by double-clicking an sws file
 >  1. Leads to login requests at pages with the login screen like
 > {{{
 >
 
http://localhost:8000/?next=http%3A%2F%2Flocalhost%3A8000%2Fupload_worksheet%3Furl%3Dfile%3A%2F%2Flocalhost%2FUsers...%2Ftest.txt
 > }}}
 > The only way I got it to log in by itself was by asking it to upload a
 worksheet; apparently that confused it enough that it logged me in for the
 "extra window" with the worksheet list, but not for the actual uploaded
 guy.  That only worked once, though.
 >
 > But apparently it works ok if you turn off the server first.  I think?
 What do you think, is this a bug?  At least I figured out what was going
 on.  Because of the way it works, I'm inclined to let it go for now, or at
 most to ask for some clarifying addition to documentation.

 Ah, yes that makes sense.  If you switch the default browser in the middle
 there is no way for Sage to know that you need it to log in automatically
 except by restarting the server.  The same would happen if you logged out
 explicitly.  I'm not sure if this is possible to fix since I think the
 login token is only generated when the server is started.  I could be
 completely wrong about that, but I think we should probably create a new
 ticket for this since it will almost certainly require changes to sagenb.

 > ----
 >
 > So the moral of the story is that I like this overall.  Can you think of
 something else I should try in breaking this?  I also tested with an older
 binary and it still works that way.

 I think you've broken it pretty good.  :-)  I can't think of anything else
 to test, except perhaps zip files (if you haven't tested those already).
 And of course on different operating systems.

 > Unfortunately the new diff is too big for preview :(  Reading through
 it, it seems like there is a lot more of stuff like
 > {{{
 > +                             <object class="IBConnectionRecord">
 > +                                     <object class="IBActionConnection"
 key="connection">
 > +                                             <string
 key="label">viewSageLog:</string>
 > +                                             <reference key="source"
 ref="57092200"/>
 > +                                             <reference
 key="destination" ref="112170745"/>
 > +                                     </object>
 > +                                     <int key="connectionID">1686</int>
 > +                             </object>
 > }}}
 > and
 > {{{
 > +
 <string>com.apple.InterfaceBuilder.CocoaPlugin</string>
 > +
 <string>com.apple.InterfaceBuilder.CocoaPlugin</string>
 > +
 <string>com.apple.InterfaceBuilder.CocoaPlugin</string>
 > +
 <string>com.apple.InterfaceBuilder.CocoaPlugin</string>
 > +
 <string>com.apple.InterfaceBuilder.CocoaPlugin</string>
 > }}}
 > than in the other patches.  Is there a good reason why the patch is
 nearly twice as big for this stuff?

 I'm using a new version of Xcode and so it thinks it needs to rearrange
 everything.  It's very frustrating to me, but I don't think there is much
 I can do short of editing the file manually which scares me.  Sometimes I
 with nib files were still binary since they basically have to be treated
 as such.

 > Anyway, this is looking quite good now.  Thanks for all this hard work.

 Finally, eh? :-)

-- 
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/11026#comment:31>
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.

Reply via email to