Indeed, Polymorph can still be loaded into 3.9 (though not a simple thing to 
do due the "hacks" that were necessary since based around Morphic).
Not tried a fresh load into 3.9 for a long while though, it is likely that 
the current Universes version would need to be used as a starting point, 
along with the Polymorph-Squeak-Widgets package (that factors out most of 
the Pharo/3.9 differences).

It is becoming increasingly difficult to maintain 3.9 compatability due to 
Pharo adaptations. Keith is right that it is unfortunately too much work to 
keep up with an additional moving target (trunk). Even so, the Pharo version 
is quite different to the packaged version as available on SqueakSource.

Of course, it would have been nicer if Morphic/EToys was less complicated 
and full of dependencies in the first place...
Still, Morphic had a lot to offer, hence the decision to base Polymorph upon 
it.

Polymorph could have been made to work *within* Morphic, without extensions 
but then, without rewriting the IDE tools, no benefits would be gained for 
the development environment, just for new "end user" applications.

If nothing else, I hope that Polymorph has given people some ideas to help 
improve Squeak. It is not just about look and feel but also things you might 
take for granted in most other widget kits, DropLists, common dialogs etc...

Regards, Gary

----- Original Message ----- 
From: "keith" <keith_hodges at yahoo.co.uk>
To: "The general-purpose Squeak developers list" 
<squeak-dev at lists.squeakfoundation.org>
Sent: Saturday, March 13, 2010 1:09 AM
Subject: Re: [squeak-dev] Regarding Polymorph


>
> On 13 Mar 2010, at 01:02, Igor Stasenko wrote:
>
>> Casey,
>> i think you are a bit subjective when saying that Polymorph is for  Pharo 
>> only.
>> Originally, it was developed for Squeak and used by squeak.
>> Then, in times of apathy, when Squeak was a rotting swamp, Pharo team
>> took an effort to incorporate
>> this package into Pharo.
>
> Not quite accurate, the developer of polymorph integrated it into  pharo, 
> and did the work of keeping up with pharo.
>
> It loaded into squeak 3.10.2 already,
>
> The only reason it may not load into trunk now is if trunk  contributors 
> broke something, because evidently its developer doesn't  have time to 
> keep up with both forks. This is the inevitable scenario  that forking 
> produces.
>
> Keith
>
>