I'm so sorry - my big mistake was to not continue reading in the
readme file. I was so stuck on step 3 that I never noticed that step 4
was exactly what I needed to do. Not only that, but just now I didn't
even make it all the way through step 4 - I browsed a bit for
Terminal, then used the search button to find Terminal instead of
following the steps in step 4 to find it.

Watching the video again, I noticed that it does eventually pan to the
whole dialog and briefly mention it - I don't know how I missed that
before. I never got this dialog, perhaps it does not appear on OS X.4.
However, the operator pushes the Open button on the dialog and
immediately gets a Terminal window running sage - this probably
happens because he has run sage on the machine before, so it has
already been configured to run with Terminal. This is what was so
misleading to the first time user. Before redoing the video, the
operator should clear the association between sage and Terminal so
that the dialog mentioned in step 4 will appear.

dwb

On Mar 31, 9:59 am, dwb <[EMAIL PROTECTED]> wrote:
> Perhaps the video only applies to OS X.5, in which case it should be
> so labeled.
> Perhaps the dialog box which appears in the video should be brought
> fully into view and discussed rather than glossed over.
> Perhaps the video could be made more encompassing, since currently it
> seems to assume things will just work, which they may under OS X.5,
> but not in my case.
> Perhaps you would like to actually test the OS X.4 binary on OS X.4 in
> order to update the video and readme.
> Perhaps you would like to try to fix the specific problem I
> encountered, for which I stll have no direct solution, that the icon
> doesn't seem to be runnable.
> Perhaps the video and readme just need a clarification for OS X.4.
> Perhaps as a newbie user of OS X and very rusty unix user I merely
> forgot about something that should have been in the video and readme.
> Perhaps an effort could be made to document what has not been tested
> yet so that volunteers could know what needs to be tested, and newbies
> could steer clear.
> Perhaps older, but more stable and more fully tested versions could be
> made available as options to those less able or willing to debug.
>
> From my limited experience, I would add to the readme: "If when you
> click the sage icon, it doesn't know how to run, instead search for
> unix in the Finder help in order to bring up a Terminal window, into
> which type: /applications/sage/sage". But, is that really what you
> want to say to Mac users? I mean, it's a work around, but isn't there
> a fix?
>
> A recent post to this list about creating an icon on the desktop that
> would run sage did for me create a desktop icon, but the icon does not
> directly run sage.
> I used TextEdit to see that the XML of the icon does contain the
> string /applications/sage/sage, but for some reason it doesn't launch
> sage.
> It does however give me easy access to a Terminal window, into which I
> can type: /applications/sage/sage, which does work.
>
> Also, my wife in an effort to help tried to install each of the two
> binaries currently available for her Power PC based Mac, and got a
> corrupted file error each time.
>
> dwb
>
> On Mar 31, 4:37 am, mabshoff <[EMAIL PROTECTED]
>
> dortmund.de> wrote:
> > <SNIP>
>
> > Hi,
>
> > > >  It is unclear to me what you want us to do? Could you clarify?
>
> > > I think he is suggesting to whoever creates theMacbinaries to modify
> > > the README file
> > > to make it easier to use for the first-time user. Maybe the poster could 
> > > be more
> > > specific about the exact words he would suggest?
>
> > Yes, I got that much. But what *specifically* would you suggest to
> > change or add?
>
> > Cheers,
>
> > Michael
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send email to sage-support@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-support
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---

Reply via email to