среда, 18 сентября 2013 г.

Current state of project

The GSoC2013 is comming to final evaluation point... What i have?

  • Simple network protocol, that was made using WebSocket technology
  • Client on Amber side with auto-reconnection to the Pharo server
  • Client can process 'doIt#string', 'printIt#string' and 'inspectIt#string' requests from Pharo
  • Server in Pharo
  • Remote workspace tool in Pharo
  • Remote inspector tool in Pharo
I can have time to finish this before the end of GSoC2013:
  • Error processing
  • Some usability improovements
  • Documentation
  • Screencast
  • Some refactoring of the code

Inspector is ready

Now inspector works normally.
There are were problems with integration into Inspector in Pharo 1.3, but we solved this.
How it works:
- You start AmberRemoteWorkspace and run Amber
- After that you can evaluate code in Amber using this tool.
- If you wants to inspect some object - just push button "Inspect it on.." and you will see AmberRemoteInspector.
- Dive in realized in inspector, you can inspect objects like you did it with Pharo objects.

- You can evaluate/print result/inspect only whole text written in workspace (it is not comfortable)
- You can evaluate/print result/inspect workspace text only after you save changes (it is not comfortable too)