Denis, I have the same in voyage, too. Marcus gave a possible reference for this https://github.com/pharo-project/pharo/pull/1685/files <https://github.com/pharo-project/pharo/pull/1685/files> Norbert
Am 21.08.2018 um 10:05 schrieb Denis Kudriashov <dionisiydk@gmail.com>:
Hi Norbert.
In Calypso there are no protocols for extensions. You should simply call command Move methods to package either from menu or drag and drop to package (where you see it).
I don't know what the reason for commit and removal. I will check.
вÑ, 21 авг. 2018 г., 8:32 Norbert Hartl <norbert@hartl.name <mailto:norbert@hartl.name>>: Iâm about preparing magritte to be loadable in pharo 7. I encountered a bit strange behaviour where I had to take cumbersome measures. Magritte has method extensions that are called e.g.
*Magritte-model-builder
These methods get loaded but when I commit something all of these methods are to be removed. The only thing I could do was to rename the extension methods. Is this intended? Doing the renaming I encountered of few things. Magritte had the extension method above in the Magritte-Model package. When I rename the category *Magritte-model-builder to *Magritte-Model the method gets removed. Not a very usual case but still strange. In order to create a method extension one needs first to create a new protocol before converting to extension method. If the new protocol is empty and you convert it to an extension method it gets removed. So I had to first create a protocol, move a method in and then convert. This combined with the behaviour that if you select two methods the method pane jumps to the beginning of the list is a lot of work just to do this job. Still it is not a very usual case but some might be interested.
Norbert