There are several things I would like to say:

- The ImageSegment code really suc.. and it is very difficult to understand, maintain and test. It is full of etoys, morphic, project and other stuff.
- There are a lot of methods that do a lot of black magic
- The code is VERY fragile and may be broke any time (if it is not already broken)

However,

- Some people use it
- It is fast

If you ask if we should remove it form core, I would say:

- It won't very VERY easy to completely remove them. There are some places where ImageSegment are inside the code and won't be easy to remove. Or at least, leave the code with Smalltalk at: #ImageSegment ifPresent: [blah..]
Look for example,
Behavior >> allInstancesEverywhereDo:��
ClassDescription >> updateInstancesFrom: �
All those doGently and isInMemory

So...remove then would be easy, but put them in a separate package, still working and without Smalltalk at: ifPresent�� I think it would be difficult.

I have already clean, fix and test it as much as possible. I will let them in Pharo and as Martin said, getting it better when someone has time and is willing to do it.

Another problem is that if we remove ImageSegment to an external package, will be soon outdated and nobody will maintain it.

Cheers

Mariano