pharo-spec / chest Goto Github PK

BaselineOfChest>>#createChestExamples depends on the package Chest that the baseline loads (circular dependency)

It opens a popup to ask to declare it as a temp or instance variable.

see issue here

I don't know how to implement the underlying data structure though.

Should I implement a circular linked list of fixed size ? Should I even set a fixed size ?

For now, to display its content, we need to select another chest and then select again the first chest

See dupriezt#7

when i load chest in Pharo 11 latest with a

Metacello new
    baseline: 'Chest';
    repository: 'github://pharo-spec/Chest';
    load.

I do not have the ctrl+c (copy) in the debugger window ...

I think this enhancement will be very cool :)
The idea is to use stored value in Chest directly in a Playground (or generaly a text input) by pasting chest access code.

1 - I have an object in an inspector. I can place this object into a Chest, easy.

2 - I have my object in a Chest.

3 - Now I want to use it in a playground, so I think it will be good to have a source code injection to get my var. The idea is to automatically paste the access code. For example I want to get my var in a playground like that :

Do right clic to open a contextual menu with an item like "Past object from chest", here an example with the current menu :

This menu can propose all chest and all var to select speadly the good var : Past object from chest > chest1 > var1

And finally the paste can be :

myVar := Chest name: #chest1 var: #var1.

Were the paste code will be Chest name: #chest1 var: #var1.

I'm using this script and I have an error :

Metacello new
    baseline: 'Chest';
    repository: 'github://pharo-spec/Chest';
    load.

• Pharo 11
• Windows 11

In the normal view, it seems to work but only if we set the focus on the new chest before loading its bindings

The current "copy" is actually a copy of the object reference.
It would be interesting to have a "copy object" (perhaps with options, shallow and deep copy?) to duplicate and store objects for backup or future use?

As a result, if the presenter has a variable named "toto", and if the user wants to load the binding named "'toto" as a variable named "var", a popup will open saying a variable with the name "toto already exists, though we don't care

see issue here

This is because selectedChest is nil in the tree view because only one item is selected (here the object from the chest and not the chest itself)

I would like to be able to use the "paste" function from the source code editor. I'm not always in the debugger, sometimes I'm working within class methods (examples, tests...) and I'd like to be able to paste chest objects from there.

I'm specifically talking about the context menu option "paste object from chest >" which is currently only available from a playground or a debugger window.