Kepler

also need to clean up the installer for osx. make sure no windows specific files are included. Sean also agreed to help on this bug.

Currently, Kepler is installed in /Applications/Kepler. The Kepler.app shortcut shows up in the Kepler folder. This shortcut could be put directly in the /Applications folder. Some applications do this, others do not. Personally, I think it makes more sense for the shortcut to be in the Kepler folder, where you can then drag it out into the Dock if you want to.

This could turn into a bit of a religious discussion, but does anyone have any comments on where they think this launcher should be?

I think that Kepler.app should be inside the Kepler folder mainly to keep the installed version looking like the CBS head for anyone who wants to do development.

One can have the best of both worlds by creating an 'alias' to Kepler.app and putting the alias directly into /Applications

I took a look at the installation XML definition, with an eye toward hiding
away much of the complexity. I got it to hide pretty much all of the files in
the app bundle (including demo workflows and documentation, which should
certainly come out) so that the bundle is self-contained. I think that this is
much more aesthetically pleasing. Any comments?

Dan's suggestion that the folder structure in the OS X installation mimic the development version checked out of CVS brings up an interesting point. Who are we making the installer for?

From a non-developer's point of view I think an installer that creates a Kepler.app bundle directly under /Applications, with most stuff hidden inside, would be ideal. But then to make it easy to find demos and docs, we probably need an /Applications/Kepler folder containing just the demos and docs folders, anyway, and then we need to make it easy to find the readme and license files etc either directly in /Applications/Kepler or in the docs subfolder. At least this way all the other files, folders, and details would be hidden when users go looking for things they actually need.

However, if we expect users to be developers who use their installed 1.0 release to actually develop new, Java-based actors with, then it's a whole different story. Is this indeed what we're doing? Or would it be better for developers to check out 1.0 from cvs using a tag and not use the installer for this at all?

I think the installed version is for users only. Developers who want to write java code should get a development version (i.e. a CVS version) of Kepler. I think the more stuff we hide in the .app directory on the mac, the better. Most mac users are used to this. I could see an /Applications/Kepler director with the Kepler.app, license, docs, etc and a demos directory only. I think this would be the cleanest but also allow us to have the demos and the readme type documents with the application.

The mac installer now installs like this:

/Applications/Kepler/Kepler(.app) - launcher directory...includes most of kepler
/Applications/Kepler/demos - demos dir
/Applications/Kepler/src - source code (if you choose to install it)
/Applications/Kepler/Uninstaller - the izpack uninstaller

The directory looks clean and is fully functional. Thanks to Sean for getting the guts of kepler into the Kepler.app dir.

Original Bugzilla ID was 3144