Loading up the code
All versions of the system are available from the OpenSkills common Store repository, but please do not load the bundle directly from there. Instead, replicate the bundle to your local Store repository and load from that.
So, load the "OS SkillsBase Development" bundle into the clean VisualWorks image from your local Store repository.
... start coding.
When publishing changes to the SkillsBase, always publish the top most development bundle. This will keep all the work contained in your version together. The alternative to to publish only the component bundles and packages that you have changed - don't do this.
Version names must take the form v iii.nnxx
- The v is a simple integer version number. e.g. 1, 2 or 5656
- The iii is an increment that indicates the attempt number for achieving the version. So, when work starts on version 2, the first increment would be 001, so the whole version string would be "2 001", the next version name for work on getting version 2 going would be "2 002" and so on.
- The .nnxx is an optional suffix if you are publishing changes to a bundle you don't own. So, if I changed something that was currently being managed by someone else, I might publish it as 2 034.bb01 to indicate that this is my version branching from 2 034. The owner can see my work and can then merge it into the main branch as appropriate.
Class names are prefixed with OSSB (for OpenSkills SkillsBase) because not all Smalltalk implementations support namespaces yet, and the system should be portable, particularly, to the two open souce Smalltalks: Squeak and GNU Smalltalk.