--- stéphane_ducasse <ducasse at iam.unibe.ch> wrote:
> Hi all
> 
> the last two/three days I have been browsing a lot of
> code while mainly 
> playing with BookMorph.
> And I noticed a lot of "nearly working" or "half broken"
> behavior. 
[...]
I have the same impression on some parts of morphic

> May be this is because I'm bad in Morphic but my
> impression is there is 
> a lot of stuff broken in Morphic and in Squeak in
> general.


As far as I know Morphic is very complex and a lot of
people work on it. 
I have similar problems now refactoring Celeste, because 
some modules like SMTP client are used also in other
context, and uses superclasses or subclasses.
When I must modify a method, I first search how it is used,
and I must decide if my action will broke some other
software parts.
I think this is a peculiar characteristic of Smalltalk, 
because the high dynamic environment bring the developer to
easily integrate his code into the existing, boosting code
reuse in an incredible strong way.

[...]
> 	But I'm sure that having some task force to fix some
> parts would be a 
> good answer to the 	problem.
By the way, there is some quite up-t-date tutorial we can
look for building morphin interfaces? 
Morphic seems changed a lot from two year ago...
Ciao ciao!

=====
// Giovanni Giorgi    http://www.siforge.org