Closed fniephaus closed 8 years ago
Where appropriate, the configuration file should be the same squeak.ini as for regular bundles/VMs. In particular, we should not reinvent names for options that are also relevant in the other VMs.
https://github.com/HPI-SWA-Lab/RSqueak/commit/6b6980258602bca7bc9f88d43f899112ac7c2020 adds support for an INI config file, smalltalkCI now supports Squeak-latest. The rest is pretty much straightforward....
For a first alpha release, it'd be great to have an app bundle that runs on all supported platforms. The bundle should be build on Travis and pushed to our artefacts repository. A bundle should ship with a working Squeak image that we could prepare with smalltalkCI. If we use a template, we only need to add the RSqueak binaries and the image to make a new bundle.
It'd also be good to add a configuration file support for RSqueak, so that it is possible to configure flags (e.g. image to open or nohdpi) in a file that resides in a vm's directory.