Hi danil

Have a look at the extension in FileReference for example.��

You will see how you can extend the default inspector.��

What you should see is that you can use any Spec20 UI within the panes.��

So we get the extensibility without the glamour and we gain the uniformity of

using Spec20.��

For us the moldability is important. If you have scenario that do not work we will study because��

the current version may need some adjustments.��

But what I can garantee is that we want to make sure that we can all build our own tools.��

Here are the extensions we are using for a new compiler we are building

On 18 Dec 2021, at 16:06, Danil Osipchuk <danil.osipchuk@gmail.com> wrote:

Dear all,

Being a long time smalltalk user (meaning I'm crafting tools for my own usage for domains I'm working with) I always relied upon the environment itself to interact with models to spare time creating user interfaces. Besides plain inspectors I used metafacilities where possible --�� seaside, then omnibrowser and lately glamour toolkit in pharo8.

Now it seems the glamourous core is not part of pharo9 anymore. Meanwhile pharo9 looks increasingly neat and I would like to make a transition but having tools in pharo8 holds me back.

I would be grateful for any pointers to help me to get started with the moldable inspectors pharo9 - papers, talks, online discussions, etc. I can likely figure it out on my own, but having an overall understanding of the approach concept would save an effort and shorten the trial and error phase.

(maybe I'm overcomplicating�� it and just having browsed around inspector code pragmas is enough to get started)

regards,

��Danil