Hi Doru, >Great job.
Was very simple to do in one evening, thanks to GT tools. I like infrastructure that empowers us and the only thing I can lament on so far is that "Workspace" menue still opens a "Playground" and I do give not up the hope that you get convinced that this is confusing to people ;) >Some feedback about the extensions: > >- I saw that you figured out the new feature of searching with spotter from >the inspector without any public announcement. Did you figure >it out from the >code of GT or by seeing an example? In any case, very nice :). By accident. I first implemented an own Spotter model and a custom action in the inspector for PRDocumentItems to open it. Then I've noticed there is another icon to click on in the inspector beside mine - and as id did the same (open Spotter) I was able to remove a lot of code again. Would have been nice to know earlier - but thats life when living on the latest Pharo 4 updates and getting things solved quickly. >- use "composite pharoPlayground" only when you want syntax highlighting and >code completion for Pharo code. Otherwise, use >"composite text" Ahh, I see. It's fixed now >you get extensions for working with files. See here: >http://www.humane-assessment.com/blog/writing-pillar-books-with-the-gtinspector I've seen that, but it did not really work. When I load (in 4.0#40537) PetitParser from MetaRepoForPharo30 using config browser, then the GT-InspectorExtensions-Pillar package and look by inspecting "FileSystem workingDirectory" onto a *.pillar file I can see the new tab "Pillar" - but it does not highlight the syntax. >- now that the inspector and spotter are part of Pharo, we can move these >extensions directly into Pillar. >The only problem is that this syntax highlighting is based on PetitParser, so >we would have to add a dependency from Pillar to >PetitParser. What do you >think? Would make sense - the dependency to PetitParse could be set for "Pillar-Pharo-Tools" so it is not loaded if one does not use the tool extensions. No time to look into this, although it would be nice to get the syntax highlighting in and it would be better to place this into Pillar itself instead of GT. Please keep up the good work. Spotter already allows other nice things as easily building custom helpers for developing or own applications. See the attached screenshot: I already use a custom spotter to combine development commands, browse domain objects, Mongo collections - easily done with a few methods and pragmas. Pharo is on the right track... Bye T.
