SimpleMorphic

> Hi Folks,
>
> A few days ago I released SimpleMorphic for Pharo. SimpleMorphic is the
> Morphic implementation in Cuis. It is much smaller and simpler than the
> one in Pharo (and in Squeak). Please see
> http://lists.gforge.inria.fr/pipermail/pharo-project/2010-November/035302.html
> . A link to the code (for Pharo 1.2) is included.
>
> While this release of the code is for Pharo, it shouldn't be a big deal
> to make it run on Squeak. My hope is that the Pharo community studies it
> in detail, adopts it, and eventually remove the old Morphic. For Squeak,
> maybe the same happens. Or perhaps there would be 2 Morphic UIs for
> Squeak: FullMorphic+Etoys and SimpleMorphic... So, what do you think?
>
> I also sent this comment to the Pharo mail list recently, trying to make
> clear why SimpleMorphic is useful:
>
> "Size of 4 core classes (Morph, MorphExtension, PasteUpMorph and
> WorldState)
> Pharo / Squeak / Cuis
> totalIvars:  39 / 46 / 26
> totalClassVars: 15 / 10 / 5
> totalInstMethods: 1170 / 1764 / 663
> totalClassMethods: 55 / 71 / 16
>
> Size of the whole Morph hierarchy
> Pharo / Squeak / Cuis
> totalClasses: 197 / 331 / 58
> totalIvars:  649 / 1063 / 257
> totalClassVars: 54 / 138 / 28
> totalInstMethods: 6651 / 9186 / 2115
> totalClassMethods: 303 / 858 / 127
>
> SimpleMorphic is much smaller. Core classes are simpler and easier to
> understand, fix and extend. The most important part is that this is not
> blind removal of unused code. A lot of the functionality has been
> redesigned to make it simpler, and the removal was done with great care
> to result in a consistent system. This work started in 2004, so we're
> talking of about 6 years of careful work. All this means that
> SimpleMorphic does not support all the features that Pharo or Squeak
> might support. Please use the browsers and other tools in Cuis to check
> what it indeed can do.
>
> Talking about complexity, let's take for example, morph layout. This is
> started with #doLayoutIn: in Pharo and #doLayoutIfNeeded in SimpleMorphic.
>
> In Pharo, this method calls #adjustLayoutBounds: (19), #layout:in:
> (149), #layoutProportionallyIn: (10),
> #computeCellArrangement:in:horizontal:target: (87),
> #computeGlobalCellArrangement:in:horizontal:wrap:spacing: (31),
> #computeCellSizes:in:horizontal: (30),
> #computeExtraSpacing:in:horizontal:target: (136), #layoutLeftToRight:in:
> (91), #layoutTopToBottom:in: (91), #placeCells:in:horizontal:target:
> (70). The numbers in parenthesis are the sum of the lines of code of the
> implementors. Total lines of code for layout (taking only these most
> important methods) is 714. I doubt there are many people who really
> understand all of this code.
>
> In SimpleMorphic (Cuis), this calls #layoutSubmorphsIn: (10),
> #applyLayoutFrameIn: (11), #layout:in: (24). Total lines of code is 45.
> I believe any smalltalker could understand these in just minutes."
>
> Cheers,
> Juan Vuletich
>
>

> Hi Folks,
>
> A few days ago I released SimpleMorphic for Pharo. SimpleMorphic is the
> Morphic implementation in Cuis. It is much smaller and simpler than the
> one in Pharo (and in Squeak). Please see
> http://lists.gforge.inria.fr/pipermail/pharo-project/2010-November/035302.html
> . A link to the code (for Pharo 1.2) is included.
>
> While this release of the code is for Pharo, it shouldn't be a big deal
> to make it run on Squeak. My hope is that the Pharo community studies it
> in detail, adopts it, and eventually remove the old Morphic. For Squeak,
> maybe the same happens. Or perhaps there would be 2 Morphic UIs for
> Squeak: FullMorphic+Etoys and SimpleMorphic... So, what do you think?
>
> I also sent this comment to the Pharo mail list recently, trying to make
> clear why SimpleMorphic is useful:
>
> "Size of 4 core classes (Morph, MorphExtension, PasteUpMorph and
> WorldState)
> Pharo / Squeak / Cuis
> totalIvars:  39 / 46 / 26
> totalClassVars: 15 / 10 / 5
> totalInstMethods: 1170 / 1764 / 663
> totalClassMethods: 55 / 71 / 16
>
> Size of the whole Morph hierarchy
> Pharo / Squeak / Cuis
> totalClasses: 197 / 331 / 58
> totalIvars:  649 / 1063 / 257
> totalClassVars: 54 / 138 / 28
> totalInstMethods: 6651 / 9186 / 2115
> totalClassMethods: 303 / 858 / 127
>
> SimpleMorphic is much smaller. Core classes are simpler and easier to
> understand, fix and extend. The most important part is that this is not
> blind removal of unused code. A lot of the functionality has been
> redesigned to make it simpler, and the removal was done with great care
> to result in a consistent system. This work started in 2004, so we're
> talking of about 6 years of careful work. All this means that
> SimpleMorphic does not support all the features that Pharo or Squeak
> might support. Please use the browsers and other tools in Cuis to check
> what it indeed can do.
>
> Talking about complexity, let's take for example, morph layout. This is
> started with #doLayoutIn: in Pharo and #doLayoutIfNeeded in SimpleMorphic.
>
> In Pharo, this method calls #adjustLayoutBounds: (19), #layout:in:
> (149), #layoutProportionallyIn: (10),
> #computeCellArrangement:in:horizontal:target: (87),
> #computeGlobalCellArrangement:in:horizontal:wrap:spacing: (31),
> #computeCellSizes:in:horizontal: (30),
> #computeExtraSpacing:in:horizontal:target: (136), #layoutLeftToRight:in:
> (91), #layoutTopToBottom:in: (91), #placeCells:in:horizontal:target:
> (70). The numbers in parenthesis are the sum of the lines of code of the
> implementors. Total lines of code for layout (taking only these most
> important methods) is 714. I doubt there are many people who really
> understand all of this code.
>
> In SimpleMorphic (Cuis), this calls #layoutSubmorphsIn: (10),
> #applyLayoutFrameIn: (11), #layout:in: (24). Total lines of code is 45.
> I believe any smalltalker could understand these in just minutes."
>
> Cheers,
> Juan Vuletich
>

> Juan
>
> Your work is exciting. A work of 6 years! Thank you for making this
> available and thanks to ESUG for partially sponsoring your work.
>
> I think we should try it out in any case.
>
> Any suggestions how to proceed? There are four change sets -- some of
> the Pharo specific.
>
>
> --Hannes
>  

> Hi Folks,
>
> A few days ago I released SimpleMorphic for Pharo. SimpleMorphic is the
> Morphic implementation in Cuis. It is much smaller and simpler than the
> one in Pharo (and in Squeak). Please see
> http://lists.gforge.inria.fr/pipermail/pharo-project/2010-November/035302.html 
> . A link to the code (for Pharo 1.2) is included.
>
> While this release of the code is for Pharo, it shouldn't be a big deal
> to make it run on Squeak. My hope is that the Pharo community studies it
> in detail, adopts it, and eventually remove the old Morphic. For Squeak,
> maybe the same happens. Or perhaps there would be 2 Morphic UIs for
> Squeak: FullMorphic+Etoys and SimpleMorphic... So, what do you think?

> Hannes Hirzel wrote:
>> Juan
>>
>> Your work is exciting. A work of 6 years! Thank you for making this
>> available and thanks to ESUG for partially sponsoring your work.
>>
>> I think we should try it out in any case.
>>
>> Any suggestions how to proceed? There are four change sets -- some of
>> the Pharo specific.
>>
>>
>> --Hannes
>>
>
> Hi Hannes,
>
> The first thing to do is to try it. Start PharoCore 1.2, install the 5
> change sets in numerical order. After loading them, you can evaluate
> 'SimpleMorphicUIManager start' to enter SimpleMorphic and
> 'SimpleMorphicUIManager stop' to return to regular Morphic.
>
>
> Cheers,
> Juan Vuletich
>
>

> Hi Folks,
>
> A few days ago I released SimpleMorphic for Pharo. SimpleMorphic is the
> Morphic implementation in Cuis. It is much smaller and simpler than the
> one in Pharo (and in Squeak). Please see
> http://lists.gforge.inria.fr/pipermail/pharo-project/2010-November/035302.html 
> . A link to the code (for Pharo 1.2) is included.
>
> While this release of the code is for Pharo, it shouldn't be a big deal
> to make it run on Squeak. My hope is that the Pharo community studies it
> in detail, adopts it, and eventually remove the old Morphic. For Squeak,
> maybe the same happens. Or perhaps there would be 2 Morphic UIs for
> Squeak: FullMorphic+Etoys and SimpleMorphic... So, what do you think?

>
> I also sent this comment to the Pharo mail list recently, trying to make
> clear why SimpleMorphic is useful:
>
> "Size of 4 core classes (Morph, MorphExtension, PasteUpMorph and
> WorldState)
> Pharo / Squeak / Cuis
> totalIvars:  39 / 46 / 26
> totalClassVars: 15 / 10 / 5
> totalInstMethods: 1170 / 1764 / 663
> totalClassMethods: 55 / 71 / 16
>
> Size of the whole Morph hierarchy
> Pharo / Squeak / Cuis
> totalClasses: 197 / 331 / 58
> totalIvars:  649 / 1063 / 257
> totalClassVars: 54 / 138 / 28
> totalInstMethods: 6651 / 9186 / 2115
> totalClassMethods: 303 / 858 / 127
>
> SimpleMorphic is much smaller. Core classes are simpler and easier to
> understand, fix and extend. The most important part is that this is not
> blind removal of unused code. A lot of the functionality has been
> redesigned to make it simpler, and the removal was done with great care
> to result in a consistent system. This work started in 2004, so we're
> talking of about 6 years of careful work. All this means that
> SimpleMorphic does not support all the features that Pharo or Squeak
> might support. Please use the browsers and other tools in Cuis to check
> what it indeed can do.
>
> Talking about complexity, let's take for example, morph layout. This is
> started with #doLayoutIn: in Pharo and #doLayoutIfNeeded in SimpleMorphic.
>
> In Pharo, this method calls #adjustLayoutBounds: (19), #layout:in:
> (149), #layoutProportionallyIn: (10),
> #computeCellArrangement:in:horizontal:target: (87),
> #computeGlobalCellArrangement:in:horizontal:wrap:spacing: (31),
> #computeCellSizes:in:horizontal: (30),
> #computeExtraSpacing:in:horizontal:target: (136), #layoutLeftToRight:in:
> (91), #layoutTopToBottom:in: (91), #placeCells:in:horizontal:target:
> (70). The numbers in parenthesis are the sum of the lines of code of the
> implementors. Total lines of code for layout (taking only these most
> important methods) is 714. I doubt there are many people who really
> understand all of this code.
>
> In SimpleMorphic (Cuis), this calls #layoutSubmorphsIn: (10),
> #applyLayoutFrameIn: (11), #layout:in: (24). Total lines of code is 45.
> I believe any smalltalker could understand these in just minutes."
>
> Cheers,
> Juan Vuletich

> On Wed, Nov 10, 2010 at 02:46:54PM -0300, Juan Vuletich wrote:
> > Hi Folks,
> >
> > A few days ago I released SimpleMorphic for Pharo. SimpleMorphic is the
> > Morphic implementation in Cuis. It is much smaller and simpler than the
> > one in Pharo (and in Squeak). Please see
> > http://lists.gforge.inria.fr/pipermail/pharo-project/2010-November/035302.html 
> > . A link to the code (for Pharo 1.2) is included.
> >
> > While this release of the code is for Pharo, it shouldn't be a big deal
> > to make it run on Squeak. My hope is that the Pharo community studies it
> > in detail, adopts it, and eventually remove the old Morphic. For Squeak,
> > maybe the same happens. Or perhaps there would be 2 Morphic UIs for
> > Squeak: FullMorphic+Etoys and SimpleMorphic... So, what do you think?
>
> Many thanks to Juan for creating SimpleMorphic, and thanks also to ESUG
> for supporting his work to make SimpleMorphic available to the community.
>
> To load SimpleMorphic into a fully updated trunk image, install the
> following from the Squeak inbox:
>
> Morphic-dtl.523.mcz
> SMx-dtl.12
> SimpleMorphic-dtl.7
>
> After loading these three files, you can open a new SimpleMorphic project
> from the menu bar or from the world menu. Not everything works yet, but
> there is enough in place to open browsers, workspaces, etc and generally
> get a feel for how it works.
>
> Notes:
>
> This is based on the original distribution for Pharo:
> http://pharo.googlecode.com/issues/attachment?aid=6793947083037793423&name=SimpleMorphicR01.zip&token=0e3d443e10d0d5a6d8239158ec9e273d
>
> I attempted to preserve the SimpleMorphic package with as few changes as
> possible, and ended up with a SimpleMorphic package and an SMx support
> package, where all of the Squeak-specific changes are in SMx. The Project
> and ToolBuilder classes are modified copies of the Morphic versions, with
> no attempt to refactor or clean up unnecessary code (this can be done later,
> as the intent is to make SimpleMorphic available in a form as close as
> possible to the original distribution).
>
> All of the development MCZ files are on my hard disk, and I can copy
> them either to SqueakSource or to squeak.org if there is an interest
> (not sure what to do with this, suggestions welcome).
>
> The SimpleMorphic and SMx packages are entirely self-contained, and
> can be loaded and unloaded without affecting the normal Morphic or MVC
> environments:
>
> (MCPackage named: 'SMx') unload.
> (MCPackage named: 'SimpleMorphic') unload.
>
> Dave
>
>
> >
> > I also sent this comment to the Pharo mail list recently, trying to make
> > clear why SimpleMorphic is useful:
> >
> > "Size of 4 core classes (Morph, MorphExtension, PasteUpMorph and
> > WorldState)
> > Pharo / Squeak / Cuis
> > totalIvars:  39 / 46 / 26
> > totalClassVars: 15 / 10 / 5
> > totalInstMethods: 1170 / 1764 / 663
> > totalClassMethods: 55 / 71 / 16
> >
> > Size of the whole Morph hierarchy
> > Pharo / Squeak / Cuis
> > totalClasses: 197 / 331 / 58
> > totalIvars:  649 / 1063 / 257
> > totalClassVars: 54 / 138 / 28
> > totalInstMethods: 6651 / 9186 / 2115
> > totalClassMethods: 303 / 858 / 127
> >
> > SimpleMorphic is much smaller. Core classes are simpler and easier to
> > understand, fix and extend. The most important part is that this is not
> > blind removal of unused code. A lot of the functionality has been
> > redesigned to make it simpler, and the removal was done with great care
> > to result in a consistent system. This work started in 2004, so we're
> > talking of about 6 years of careful work. All this means that
> > SimpleMorphic does not support all the features that Pharo or Squeak
> > might support. Please use the browsers and other tools in Cuis to check
> > what it indeed can do.
> >
> > Talking about complexity, let's take for example, morph layout. This is
> > started with #doLayoutIn: in Pharo and #doLayoutIfNeeded in SimpleMorphic.
> >
> > In Pharo, this method calls #adjustLayoutBounds: (19), #layout:in:
> > (149), #layoutProportionallyIn: (10),
> > #computeCellArrangement:in:horizontal:target: (87),
> > #computeGlobalCellArrangement:in:horizontal:wrap:spacing: (31),
> > #computeCellSizes:in:horizontal: (30),
> > #computeExtraSpacing:in:horizontal:target: (136), #layoutLeftToRight:in:
> > (91), #layoutTopToBottom:in: (91), #placeCells:in:horizontal:target:
> > (70). The numbers in parenthesis are the sum of the lines of code of the
> > implementors. Total lines of code for layout (taking only these most
> > important methods) is 714. I doubt there are many people who really
> > understand all of this code.
> >
> > In SimpleMorphic (Cuis), this calls #layoutSubmorphsIn: (10),
> > #applyLayoutFrameIn: (11), #layout:in: (24). Total lines of code is 45.
> > I believe any smalltalker could understand these in just minutes."
> >
> > Cheers,
> > Juan Vuletich
>

> Great work, thanks.
>
> A suggestion, why don't follow a common pattern to name the
> Pharo/Squeak/Gemstone specific code for package XXX with the format:
>
> XXX-Squeak
>
> so that the packages be:
>
> XXX-dtl.123.mcz
> XXX-Squeak-dtl.123.mcz
> XXX-Pharo-dtl.123.mcz
>
> This way if a Metacello configuration is created for this package it
> will pull the corresponding dependency for tha platform where is being
> installed.
>
> Cheers.
>

> Many thanks to Juan for creating SimpleMorphic, and thanks also to ESUG
> for supporting his work to make SimpleMorphic available to the community.
>
> To load SimpleMorphic into a fully updated trunk image, install the
> following from the Squeak inbox:
>
> Morphic-dtl.523.mcz
> SMx-dtl.12
> SimpleMorphic-dtl.7
>
> After loading these three files, you can open a new SimpleMorphic project
> from the menu bar or from the world menu. Not everything works yet, but
> there is enough in place to open browsers, workspaces, etc and generally
> get a feel for how it works.

>
>
>
> On 3/4/11 9:41 PM, "David T. Lewis" <[hidden email]> wrote:
>
> > Many thanks to Juan for creating SimpleMorphic, and thanks also to ESUG
> > for supporting his work to make SimpleMorphic available to the community.
> >
> > To load SimpleMorphic into a fully updated trunk image, install the
> > following from the Squeak inbox:
> >
> > Morphic-dtl.523.mcz
> > SMx-dtl.12
> > SimpleMorphic-dtl.7
> >
> > After loading these three files, you can open a new SimpleMorphic project
> > from the menu bar or from the world menu. Not everything works yet, but
> > there is enough in place to open browsers, workspaces, etc and generally
> > get a feel for how it works.
>
>
> Many thanks to Juan for doing SimpleMorphic
> Many thank to you for bring it to trunk

>
> Now i could do SqueakLight4
>
> A trunk / pharo cross with SimpleMorphic and my own wild ideas
>
> I fact , in this moment i chatting with German Arduino and trying your
> recipe in my SqueakLight3-Cog-alpha.9902.image.
>
>
> What is Squeak 4.2 unloaded to my taste and updated until this morning with
> only my choices from trunk .
>
> All goes right until now, so i took the rest of Carnaval for follow
> discussion , working my ideas and test.
>
> Thanks Juan, Thank David
>
>
> Edgar
>
>
> P.S. Could follow test in Twitter as #Squeaklight4
> @morplenauta
>
>

>
>
>
> On 3/6/11 1:05 PM, "David T. Lewis" <[hidden email]> wrote:
>
>>
>> Hi Edgar,
>>
>> The integration of © as a Squeak project is not
>> complete, so think of this as "pre-alpha". But I'm still working
>> on it, and learning a lot about Morphic in the process :)
>>
>> Dave
>
> Yes , I know.
> A lot of work for having a useful system, but is a giant step having
> SimpleMorphic running.
>
>
> Need re-doing all tools windows.
> Can beg Monticello Browser first ?
>
> My idea is having a no backward compatible system.
> Run in SimpleMorphic  on top of Squeak / Pharo cross.
>
> Lots of learning....
>
>
> Edgar
>
>
>

> Yeah, in Squeak's situation it makes even more sense than it makes in Pharo,
> because we have a lot of features and applications in our image which the
> community is strongly aligned against breaking until they can be reloaded as
> external packages, which I think is admirable and responsible, but makes it
> really hard to drive Morphic into the future.
>
> SimpleMorphic is nice because we can enjoy our past while slicing off a
> delicious piece of the future (Cuis' Morphic implementation approaches an
> ideal in my view, though some features are missing.)
>
> On Mar 6, 2011, at 2:01 PM, "Edgar J. De Cleene" <[hidden email]>
> wrote:
>
>>
>>
>>
>> On 3/6/11 1:05 PM, "David T. Lewis" <[hidden email]> wrote:
>>
>>>
>>> Hi Edgar,
>>>
>>> The integration of © as a Squeak project is not
>>> complete, so think of this as "pre-alpha". But I'm still working
>>> on it, and learning a lot about Morphic in the process :)
>>>
>>> Dave
>>
>> Yes , I know.
>> A lot of work for having a useful system, but is a giant step having
>> SimpleMorphic running.
>>
>>
>> Need re-doing all tools windows.
>> Can beg Monticello Browser first ?
>>
>> My idea is having a no backward compatible system.
>> Run in SimpleMorphic  on top of Squeak / Pharo cross.
>>
>> Lots of learning....
>>
>>
>> Edgar

> It's obvious none today Morphic app could run in SimpleMorphic, right ?
> So, what about if we design a Traslator package which could take a today
> Morphic app and convert it to SimpleMorphic ?
>
> Juan could advice to a Translator "Task Force".
> As I have a nice internal LAN with all kind of computers , volunteer for
> doing test and reports.
> When learn how to do , also could help with code.
>
> Edgar
>  

> Edgar J. De Cleene wrote:
> >It's obvious none today Morphic app could run in SimpleMorphic, right ?
> >So, what about if we design a Traslator package which could take a today
> >Morphic app and convert it to SimpleMorphic ?
> >
> >Juan could advice to a Translator "Task Force".
> >As I have a nice internal LAN with all kind of computers , volunteer for
> >doing test and reports.
> >When learn how to do , also could help with code.
> >
> >Edgar
> >  
>
> I will support this initiative (or any other that involves code I
> write). I will participate in discussions, advice if needed, and fix any
> bugs found in my code.
>
> Cheers,
> Juan Vuletich