Contributions
Page created at the behest of Göran Krampe
This page lists suggestions about improvements to Amber and its tools which contributors might "adopt" and realize. After implementation they can initiate a pull request to have their changes merged with upstream.
-
"auto-complete" aka Shout in the Browser (complexity: intermediate).
-
extension of search to more elements incl source (like Pharo's Finder) (complexity: intermediate)
-
More views in the Browser like those offered by other Smalltalk (i.e. inheritance, hierarchy, variables) (complexity: intermediate)
-
switch between "Local" and "Remote" modes for IDE. A local mode would be equivalent to the current IDE, i.e. work with the Javascript engine in the browser. A remote mode would offer a view of the remote system, including the option to modify code, evaluate expressions (complexity: high).
-
DONE tool to generate getters/setters (complexity: intermediate)
- rpc layer to seamlessly integrate "backend Smalltalk" (Amber in Node.js, Squeak/Pharo) with client (complexity: high). This would allow "live" eidting
- option to have all Smalltalk packages in directory "st" loaded (when deploy = false). After a commit and later page reload, any newly created package would automatically be loaded and shown in the Browser. Would need an interface with server-end (complexity: intermediate)
-
Support for "SourceMaps" in Amber. This would allow the debug/display of the "original source" in the Chrome (and later: firefox) debugger instead of the generated source. So you would be able to break on and step through your Smalltalk code while utilizing the JavaScript debugger. This would especially be helpful in case the IDE itself fails or if the IDE is unavailable for other reasons.
-
Insert suggestions for Ambers own "native" debugger here