[squeak-dev] SimpleMorphic Editors

David T. Lewis lewis at mail.msen.com
Sun Apr 10 15:28:02 UTC 2011


On Sun, Apr 10, 2011 at 07:25:23AM -0300, Edgar J. De Cleene wrote:
> 
> 
> On 4/10/11 3:35 AM, "Bal?zs K?si" <rebmekop at gmail.com> wrote:
> 
> > Yep. I think Edgar, you are a bit lighthearted with overrides. Luckily
> > I think, we can get rid of them:
> 
> As I write in the comments, take as slow dirty beginning.
> Sure all need review and improve, but at less we have Monticello Browser
> into SimpleMorphic , right ?
> 
> > ?- One set of these overrides occur in MCTool ui building. MCTool uses
> > ToolBuilder sometimes, sometimes not. If we would use ToolBuilder
> > everytime, this problem would go away. Nicolas has a simple change in
> > the inbox, which fixes this (Monticello-nice.404). IMO we should adopt
> > it.
> 
> Updating a fresh Squeak4.3-11157.image go to Squeak4.3-11224.image
> This have Monticello-cmm.454 and no Monticello-nice.404 in the history.
> I merge by hand, see if could improve code and still works....
> 
> > ?- The other is ProgressInitiationException >> defaultMorphicAction.
> > It's sent by said class' defaultAction:
> > 
> > defaultAction
> > ? ? ? ?Smalltalk isMorphic
> > ? ? ? ? ? ? ? ?ifTrue: [self defaultMorphicAction]
> > ? ? ? ? ? ? ? ?ifFalse: [self defaultMVCAction].
> > 
> > Edgar added isSimpleMorphic to PasteUpMorphs, and branched on it in
> > defaultMorphicAction. I think we should go in the opposite way and
> > replace isMorphic sends with dispatching on UIManager default or
> > Project current. What do you think?

Are you thinking of something like "UIManager default progressInitiationAction"
or "Project current progressInitiationAction"? That sounds like a good approach
to me. Something like this will be needed in order to make Morphic reloadable
anyway.

> I think the future is SimpleMorphic and wish get rid of LegacyMorphic as
> soon as possible.

This is from the SqueakSource project description:

  "The focus here is to make SimpleMorphic runnable within its own
  type of project such that classic Morphic, SimpleMorphic, and MVC
  can coexist within a Squeak image."

Once we reach the point where all of these are reloadable packages,
there will be no need to debate which is best. Each can stand on its
own merits :)

Dave

p.s. I just updated the " SimpleMorphic for Squeak" project to send 
commit notices to the squeak-dev list for future commits. If anyone
objects, speak up and I'll turn it off.




More information about the Squeak-dev mailing list