Hi Doru, yes - but the concept of moldable tools is nothing new for Smalltalk - it's a long tradition. Even in Java world we have them (NetBeans and Eclipse can be adopted to own needs as well). The GT inspector with the tabs is similar to the known concept of custom inspectors in Smalltalk and custom views in Eclipse. The #act: methods who provide the buttons usually care on the current GT presentation. In Eclipse one has explicit extension points so I can even add a button on another tab view easily. Dont know how this can currently be done in GT tools as usually now a single extension method represents the whole composite with the menues, context menues, ... Also there are more concepts abstracted away in Eclipse (workbench, perspectives, actions, ...) that allow one to customize the whole IDE for a rich client platform. For sure it is easier to lively inspect/provide code in Pharo with less LOC than in Java. And yes I know that in Eclipse there is a gap because extensions require a bad mix of XML and code in the plugins and all that is based on a language with dead code in text files ;) Small issues I've found: - the tabs constantly display a "a MyClass" followed by the #gtDisplayString in parantheses - havent found where to adopt this - I was not able to find out quickly how to avoid the "Browse" button at the top There is a much better approach/alternative to the way we do it now with less coding ... but I can not talk about that further. Not yet ;) Bye T.
Gesendet: Mittwoch, 04. November 2015 um 23:09 Uhr Von: "Tudor Girba" <tudor@tudorgirba.com> An: "Any question about pharo is welcome" <pharo-users@lists.pharo.org> Cc: "Pharo Development List" <pharo-dev@lists.pharo.org> Betreff: Re: [Pharo-dev] [Pharo-users] [ANN] QuickAccess for Pharo 5
Hi,
Nice work!
I love the details you went through to implement this, especially given that the UI is just a custom inspector. Itâs naked objects on steroids :).
I think this is a beautiful use case for moldable tools. It shows that once the cost of tools drops, unforeseen solutions will emerge. We need to focus on more support to make more things like this possible.
Cheers, Doru
On Nov 4, 2015, at 10:35 PM, Torsten Bergmann <astares@gmx.de> wrote:
Hi,
I quickly wrote yet another small tool to work faster with Pharo. I call it "QuickAccess" - it's some kind of "ScriptManager 2.0" allowing you to quickly access actions (defined as code scripts) via Spotter, Menu, Button, etc.
You can load it from Spotter/Catalog in Pharo 5.0 beta.
The following video demonstrates how to use it:
The defined structure including the scripts can be exported to a file and send around. So far it is "complete" for my own requirements - if you feel something is missing you can contribute and help moving it forward.
The repo is at http://www.smalltalkhub.com/#!/~TorstenBergmann/QuickAccess Contact me with your STHub account if you need access.
The tool has some similarities with Playground/script cache, but GT tools lack the category structuring for scripts that you find in QuickAccess. It might be an inspiration for a future unified script management solution in Playground.
Have fun!
Bye T.
-- www.tudorgirba.com
"Obvious things are difficult to teach."