On Jan 25, 2010, at 10:24 , Igor Stasenko wrote:
2010/1/25 Adrian Lienhard <adi@netstyle.ch>:
On Jan 25, 2010, at 09:57 , Mariano Martinez Peck wrote:
On Mon, Jan 25, 2010 at 9:02 AM, Adrian Lienhard <adi@netstyle.ch> wrote:
Hi Stef
We can move the few classes related to image segments into a separate package in SqueakSource. The system (ideally) does not depend on them so it should not be too hard to package them separately.
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
I think image segments is a very nice idea and it works very well if you know how to use them. The core, which is used for basic store/load, is not that complicated. But image segments have been hacked in ugly ways for project persistency. Hence, there is a lot of complexity that is not needed.
Just one question: Why it is an ImageSegments which been hacked, but not a Project themselves?
Probably because it was easier that way ;). As far as I understand a lot of code deals with storing presenters (Etoys) and projects/morphs in clever ways. This is additional behavior that you don't need (anymore). I think if we remove this, we get a very small class that is much simpler to understand and use. Adrian