anything is doable. The barrier always is knowledge. There is already a project to bring documentation and a specific kind of documentation called Pillar which is what we use for updated PBE and Pharo for the Enterprise books inside the GTInspector. Its a WIP.
On the side of GTSpotter you have a morphic wrapper called Brick that is used to ease the design of the GUI. But whether you use Glamour or Spec or Brick or whatever you use Morphic. Only Bloc which suppose to be the new kid in the block to replace Morphic is not Morphic but for now at least the heavy weight gorilla is Morphic. As soon as you understand morphic you are unstopable. Dynamic documentation is one of the things that Pharo really lacks if you ask me, I am that annoying guy that complains about documentation all the time. I think however that we get closer to this . >From what I see you talk about class and instance comments. Of course with Pillar at your side you can go way above that and provide functionality that can rival pdf and html help files. So yes its doable and yes you can take it very far but as always is about having the will to do the hard work because in the end nothing is easy as it looks or else someone else would have done it by now. On Wed, Dec 10, 2014 at 8:49 PM, Edward Povazan <empova...@gmail.com> wrote: > Hello, > > I am having a blast with GTSpotter - it’s the missing link for me, just > one step to ask a question from Pharo. Keeps the flow going! > > Being new to the innards of Pharo, I’ve decided to try something. > I would love documentation in GTSpotter. For example, I am interested in > how packages are organized in Pharo. > Cmd+Enter: ‘Package' > I get a list of package type classes. > > Cmd+Sh+Right Arrow. > Now I see all the classes in the Classes category ... > PackageInfo, PackageOrganizer, GRPackage, RPackageOrganizer - all > interesting candidates in my exploration. > > But now I need to browse into each, look at the docs, then bring back > GTSpotter, navigate to the last context with History, and repeat. More than > one step. > > So I am going to try: > - when showing all items in classes and methods categories, add a little > [d] tag to the end of the item text to indicate if there is documentation > for that item (class/instance or method docs) > - Cmd+Sh+Right will display the docs. > > Is this doable within the current framework? > If so, I am going to chip away on this. > > Thanks, > -Ed > > >