Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CapeCode installer should describe how to start CapeCode #2

Open
cxbrooks opened this issue Oct 2, 2017 · 2 comments
Open

CapeCode installer should describe how to start CapeCode #2

cxbrooks opened this issue Oct 2, 2017 · 2 comments

Comments

@cxbrooks
Copy link
Member

cxbrooks commented Oct 2, 2017

Note: the issue was created automatically with bugzilla2github tool

Original bug ID: BZ#2
From: @cxbrooks
Reported version: unspecified
CC: accessors-devel@terraswarm.org

@cxbrooks
Copy link
Member Author

cxbrooks commented Oct 2, 2017

Edward wrote:

"- After installing, it's not obvious how to run it. The web page
suggests the command line, but doesn't explain $PTII. I navigated to
the bin directory of the temporary location and clicked on the app and
that worked. Perhaps the .app file should go in the top-level directory?"

This is an interesting issue. Typical Mac applications consist of a .app directory that contains the application. When the user clicks on the .app directory, then the application starts up.

Ptolemy II and CapeCode consist of multiple applications it it is expected that the user will browse the distribution, so we don't ship a single .app directory. In addition, for support reasons, we want the distributions to be fairly uniform between the different platforms.

Finally, we hope that most users will extend Ptolemy II/CapeCode and rebuild it. Rebuilding Ptolemy II and CapeCode creates the Mac .app files in $PTII/bin. If we had a top level .app file for CapeCode, this would clutter the top level directory. In addition, for CapeCode, we would end up with $PTII/Vergil.app, $PTII/Ptiny.app, $PTII/CapeCode.app and possibly other .app files.

Other multi-platform applications include a bin directory on the Mac that includes the .app directories.

Still, the point is well taken that we need to make it more clear about how to start CapeCode.

One idea would be to extend adm/gen-11.0/userInputSpec.xml to display a Mac-specific message that would include this text.

Even better would be to have a window at the end that would display how to start the app under the various platforms.

It would be good to address this before the December 2017 demo.

@cxbrooks
Copy link
Member Author

cxbrooks commented Nov 1, 2017

I updated the installer to display a Mac-specific window ($PTII/adm/gen-11.0/startupCapeCodeMacOSX.htm) and save that file as $PTII/startupCapeCodeMacOSX.htm.

To close this, we need to get Edward's feedback on the new installer at http://chess.eecs.berkeley.edu/ptexternal/nightly/builds/ptII-latest.setup.mac.app.tar.gz on after Thursday November 2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant