Porting code from other Smalltalk dialects

Amber is different than regular Smalltalk in a few ways which makes porting code a non-trivial thing, but also quite manageable. Things you need to fix in MyCategory.st before it works:

• Rewrite character literals as single character Strings and make changes accordingly. Jtalk does not have Character, but String does implement some of Character behavior.
• Rewrite uses of class variables. Amber does support class instance variables, but not class variables.
• Rewrite uses of global variables. Amber only has global classes and packages, but not arbitrary objects. Use classes instead like "Smalltalk current" instead of "Smalltalk" etc.
• Remove any pragmas. We will add support in the parser to just ignore them.
• Remove any "SystemOrganization addCategory:" chunks, Amber creates categories on the fly.

The current way to get code into Amber from another Smalltalk goes like this:

1. After fixing the above things in your "other Smalltalk", export the code as a "fileout" in the chunk format with a .st filename extension. Make one file per class category and give it the same name as the class category - otherwise it breaks.
2. Monticello style class extensions (loose methods) using "*yaddayadda" method category names is allowed.
3. Run "amberc MyCategory.st" to compile it into MyCategory.js. Put this file into the $AMBER/js directory.
4. Edit the index.html file to load your code, and then open that file using for example [http://localhost:4000/index.html) and you should see the package called "MyCategory" in Amber. In Amber we call "class categories" packages.

After this, pressing "Commit package" should store any changes made (of selected package) back. It also stores a corresponding MyCategory.st-file in the st directory and a special MyCategory.deploy.js file which is a stripped down version for deployment purposes.