1. 2013 - Release 0.12.0
  2. ===============================
  3. After 3 months of work we are pleased to announce the 0.12.0 release of Amber.
  4. Besides the usual bug fixes a lot of new features have emerged.
  5. The biggest change is the switch to RequireJS to specify Amber package dependencies
  6. and for loading the packages as AMD modules.
  7. Amber is now additionally available as Bower [2] component.
  8. Bower is also used to manage required JavaScript libraries which don't have to be kept
  9. around in the repository anymore.
  10. The repository layout was restructured to provide a cleaner separation of different Amber parts:
  11. * Smalltalk code is located in 'st'
  12. * Compiled Amber packages are located in 'js'
  13. * Supporting JavaScript code is located in 'support'
  14. Together with the RequireJS changes the specifying their dependencies the Brickz [3]
  15. reconfigurable micro composition system was introduced.
  16. This is used for
  17. On the Smalltalk side support has been added for writing exponential numbers of the form 2e5.
  18. Helios (the new IDE) is progressing nicely and has seen a lot of improvements.
  19. One of the great parts is the new stepping debugger which is also making progress.
  20. To try Helios, open the helios.html page or
  21. evaluate in any other amber page `require('amber/helpers').popupHelios()`.
  22. The last enhancements target the commandline compiler which can be used as
  23. `amberc` (an executable script) or as a Grunt task.
  24. The following features have been added:
  25. * generation of shebang line (#!/usr/bin/env node)
  26. * specification of target namespace (`-n` flag; `amd_namespace` option in Grunt)
  27. * specification of additional library directories (`-L` flag; `library_dirs` option in Grunt)
  28. The following features have been removed:
  29. * creation of *.deploy.js files (`-d` flag; `deploy` option in Grunt)
  30. * optimization passes via Closure compiler (`-o`/`-O` flags; `closure_jar` option in Grunt)
  31. The same behavior can be achieved by using specific Grunt tasks
  32. Additionally, the Grunt task now handles the -v/--verbose flag which triggers the same behavior
  33. as the `verbose` option which can be specified in the Gruntfile.
  34. Some numbers about this release (starting from 0.11.0):
  35. * 660 commits
  36. * 10 committers
  37. * 66 unit tests added
  38. * 152 issues were closed
  39. * 379 unit tests in total
  40. Commits:
  41. Issues:
  42. For the most important API related changes see the file API-CHANGES.txt.
  43. * Installing Amber from NPM
  44. To install Amber from NPM, run
  45. npm install amber
  46. * Installing Amber from Bower
  47. To install Amber from Bower, run
  48. bower install amber
  49. * Migration from Amber 0.11.0
  50. First, the loading of JavaScript files must be adapted. The custom loader has been replaced with
  51. requirejs for loading files in the browser. New loader code is thouroughly
  52. explained in [4].
  53. After updating the loader part, `.st` files need to be recompiled
  54. into new AMD `.js` files. During loader changes, a namespace was choosen and will be needed for recompilation.
  55. Go to your directory with `.st` files and issue this from the shell:
  56. ```sh
  57. <path-to-amber>/bin/amberc -l SUnit,Canvas -n <chosen-namespace> -D <path-for-compiled-js-files> *.st
  58. ```
  59. In windows, use `\` as path separator, the rest is identical.
  60. The `-l SUnit,Canvas` is just a general guess, if your code depends on more (or less) non-kernel packages from amber, list them here accordingly.
  61. This migrate scenario only covers simple deployments with your project's code and amber.
  62. If your project is more complicated, using libraries and packages from multiple sources,
  63. it is hard to give general advices to migrate - you must do it library by library,
  64. giving each location its own namespace, and `-L` option of `amberc`
  65. comes handy when integrating; ask on the mailing list if problems arise.
  66. [1]
  67. [2]
  68. [3]
  69. [4]
  70. 09th July 2013 - Release 0.11.0
  71. ===============================
  72. Three months have passed and we are happy to announce the release
  73. of Amber 0.11.0!
  74. Some numbers about this release:
  75. * 494 commits
  76. * 13 committers
  77. * increasing the number of core committers to 25
  78. * 50 unit tests added to the kernel
  79. * 313 unit tests in total
  80. Since the last release 60 issues were closed, bringing us to 499
  81. issues closed.
  82. This release includes a lot of bug fixes, improvements to the
  83. CLI, as well as a preview of the next IDE, named Helios. Amber
  84. now also uses a CI server [1].
  85. To try the Helios, the new IDE, open the helios.html page, or
  86. evaluate in any other amber page `amber.loadHelios()`.
  87. The compiler also received some improvements, especially
  88. regarding message send optimisations and super sends.
  89. Here's the list of commits and closed issues:
  92. There is a lot more to come with Helios, a stepping debugger
  93. based on the AST is in progress and currently in the 'debugger'
  94. branch on GitHub.
  95. * Installing Amber from NPM
  96. To install amber from NPM, run
  97. npm install amber
  98. * Migration from Amber 0.10.0
  99. Amber compiled code should be compatible with Amber 0.10.0, but
  100. recompiling is needed in order to get contexts working:
  101. Compiler new recompile: (Package named: 'MyPackage') classes.
  102. (Package named: 'MyPackage') commit
  103. For API related changes see the file API-CHANGES.txt.
  104. 13th March 2013 - Release 0.10.0
  105. ================================
  106. Here's a summary of change since the 0.9.1 release:
  107. - Travis CI jobs
  108. - Almost 300 issues closed
  109. - 150 new unit tests written
  110. - All classes in the Kernel are documented
  111. - New and much improved compiler toolchain, providing:
  112. - Semantic analysis
  113. - AST Node annotation
  114. - Intermediate representation (easier to optimize)
  115. - Better inlining
  116. - an AST interpreter
  117. - support for blocks contexts
  118. - New build system based on grunt.js, replacing the old makefiles
  119. - New bin/amberc compiler written in Amber/Node.js
  120. - SUnit improvements and cleanup, with support for async assertions
  121. - Improved ClassBuilder with better class migration support
  122. - Improved loader for third party packages
  123. - New: Announcements
  124. - Classes can be augmented by light-weight methods created from blocks
  125. - Snippets of HTML can be marked to become virtual tags in HTMLCanvas
  126. - Amber server supports Basic HTTP authentication (not recommended for production environments/unencrypted connections)
  127. - New IDE on it's way for Amber 1.0
  128. 16th January 2012 - Release 0.9.1
  129. =================================
  130. Here's a summary of changes since the 0.9 release:
  131. - 80 new unit tests written
  132. - 52 issues fixed
  133. - All classes in Kernel-Objects, Kernel-Classes and Kernel-Methods has been documented
  134. - New documentation framework (see
  135. - Better class organisations, "Kernel" package split into several packages
  136. - First class packages have replaced class categories
  137. - Internet Explorer 7+ compatibility
  138. - New Announcement framework ported from Pharo
  139. - New console-based REPL written in Amber using node.js
  140. - Symbol class implemented together with object identity and #==
  141. - New OrderedCollection and Set implementation
  142. - Dictionary can now have any kind of object as keys. String-key dictionary has been renamed HashedCollection
  143. - New TwitterWall example
  144. - Improved HTML Canvas, now compatible with IE7
  145. - Improved JSObjectProxy for seamless JavaScript objects access from Amber
  146. - No more jQuery binding. Amber is fully capable of sending messages to JavaScript objects
  147. 13th September 2011 - Release 0.9
  148. =================================
  149. Amber has been evolving furiously since the presentation at ESUG 2011 in Edinburgh less than 3 weeks ago.
  150. This is a summary:
  151. Language, compiler and runtime
  152. - New 100x faster parser built using PEGjs instead of the old parser built using PetitParser.
  153. - New much faster ChunkParser implementation in handwritten Amber instead of using PetitParser.
  154. - Improved parsing error report with quoted source code plus marker pinpointing parsing error.
  155. - Removed PetitParser since it is no longer needed by Amber itself.
  156. - Added compiler optimizations in the form of speculative inlining of specific messages and control structures.
  157. - Added support for dynamic Arrays, just like in Squeak/Pharo.
  158. - Added support for similar dynamic Dictionaries, not seen in other Smalltalks.
  159. - Added & and | as allowed binary selectors and implemented them in Boolean.
  160. - Added a Set implementation.
  161. - Added first basic support for real Packages with dependency information.
  162. ...and various extensions, enhancements and bug fixes to the library classes.
  163. Development environment
  164. - A working Debugger with integrated inspector, proceed etc.
  165. - A new structure with
  166. - A working amberc command line compiler including a Makefile for recompiling the whole Amber.
  167. - Enabled TestRunner in the IDE for running unit tests based on SUnit.
  168. - Added "File in" button in Workspace to easily paste and filein source code in chunk format in the IDE.
  169. Example code and ports
  170. - Ported ProfStef interactive tutorial, available on Amber homepage but also in examples directory.
  171. - Included the ESUG presentation as an example also in the examples directory.
  172. - Several new examples running on Node.js and webOS included, all with Makefiles.
  173. Various other things
  174. - Issue tracker on github now used as primary source, closed a bunch of reported issues.
  175. - Wiki pages on github with information on how to port code from other Smalltalks, lists of articles, tutorials, roadmap and more.