Does Pharo use Morphic? Is there a conscious decision on people's parts
to NOT try and keep the various flavors of Morphic compatible, or is it
just "too hard," or that people don't care, or think it irrelevant?
Some graphical frameworks manage to keep a centralized core of classes
because they are created by one group of people for one language and
then bindings ported to other languages. Morphic is unique in that it is
being [re]implemented in 3 different languages: Self, Smalltalk (with
several variations within that branch) and JavaScript. Is there any way,
or even desire, to coordinate between the differing versions?
L
On 2/1/12 2:51 PM, Stéphane Ducasse wrote:
Hi lawson
may I ask you how this information is relevant to pharo?
Stef
On Feb 1, 2012, at 8:38 PM, Lawson English wrote:
It seems to me that the most active place where development of Morphic is
taking place is in the context of Lively Kernel. Is anyone tracking what the LK
people are doing and seeing how it can be backported, or used to create a new
version, or integrated with the current version of Morphic or Cuis, etc?
Lawson
