Interesting that you are asking that question. This basically means that the whole philosophy of the GTInspector did not get communicated well. We have to work on this because I think GTInspector is the most significant step in object inspection since the introduction of the original inspector.
So, here is the main page: http://gt.moosetechnology.org Here is the introduction: http://www.humane-assessment.com/blog/the-moldable-gtinspector-deconstructed/ Some examples: http://www.humane-assessment.com/blog/browsing-files-with-gtinspector/ http://www.humane-assessment.com/blog/browsing-files-with-gtinspector-video/ http://www.humane-assessment.com/blog/managing-morph-keybindings-with-gtinspector/ http://www.humane-assessment.com/blog/assessing-pharo-performance-with-gtinspector/ http://www.humane-assessment.com/blog/dynamic-exploration-of-a-postgres-db-with-the-gtinspector/ How to manage the extensions: http://www.humane-assessment.com/blog/managing-gtinspector-extensions/ And a more thorough list: https://www.google.com/search?q=site%3Ahumane-assessment.com%20gtinspector Cheers, Doru On Mon, Dec 1, 2014 at 1:21 PM, kilon alios <kilon.al...@gmail.com> wrote: > "Take the inspector for example. It is a tiny piece of code that can be > extended in many ways and in doing so, it can support various workflows." > > What is its API and where is documented ? > -- www.tudorgirba.com "Every thing has its own flow"
