Skip to main content

Smalltalk Challenge: Post 6 - Morphic

As the Dynabook/Smalltalk environment was the first to introduce the windowed user interface, it's no surprise that the Model View Controller (MVC) pattern also made its first appearance in Smalltalk. In Smalltalk, the term "MVC" refers to both the architecture pattern that separates code responsibilities into model, view, and controller objects, and the user interface framework used to develop visual and interactive elements. The MVC framework manages objects in the environment using the MVC pattern.
  • Model objects are responsible for maintaining the behavior and state of the element.
  • View objects are responsible for the representation or appearance of the element within the world.
  • Controller objects are responsible for accepting user input and passing messages to the model and view objects.
But because of the complexity and limitations of the MVC architecture, Squeak has replaced the MVC framework with Morphic, a direct-manipulation user interface toolkit. Unlike MVC, Morphic didn't originate with Smalltalk. Rather, it was written by Randy Smith and John Maloney for Self, another OO programming language influenced by Smalltalk, and ported to Squeak by Maloney who is also one of the core Squeak developers.

All interactive elements that exist within the environment in Morphic are subclasses of Morph, and the majority of code that would normally be required by MVC is encapsulated in the Morph class. For example:
Morph new openInWorld.
will open a blue rectangle that you can move about the screen, resize, rotate, and more. When a custom morph extends Morph, it inherits all of its parent's functionality and the programmer is freed to focus on customizing the morph instead of writing boiler-plate code. As Maloney wrote in An Introduction to Morphic, "In morphic, a little code goes a long way, and there is hardly any wasted effort."

I actually took advantage of Morphic in my Kember Identity search code, though it's not something one might think of as requiring a manipulatable object. The step message is intended for creating animations and morphs that update themselves dynamically over time (adding liveness to the interface). Morphic repeatedly sends step messages to each morph which may respond by executing their step method (the rate at which step messages are sent to an object can be specified by responding to the stepTime message, but by default I believe it's set for every few milliseconds or so). The method actions run concurrently with whatever else is happening in the rest of the environment. This builtin threading was exactly what I needed to ensure the rest of the system remained responsive to the user while the code was searching for a hash that exhibits the Kember Identity.

I subclassed the TextMorph class and supplied the following step method:
Kember » step
    found | (currHash = stopHash)
        ifFalse: [self contents: 'Testing ' , currHash.
            found := self test: currHash.
                found ifTrue: [self contents: 'Found '
                        , currHash , '!'].
            currHash := self nextHash: currHash.
            currHash = stopHash
                ifTrue: [self contents: 'KI was not found.']].
The contents: method is inherited from TextMorph to set the displayed text string, and the rest are instance variables and methods specific to my Kember class.

Morphs can respond to several other messages sent by the framework, too. Responding to the drawOn:message allows a morph to customize its appearance, or how it "draws" itself in the environment. Responding to mouseDown:, mouseUp:, mouseMove:, and keyStroke: events lets the morph interact with the user's mouse and keyboard activities.

Well that's 6 posts down now and only 4 more to go before I complete my challenge!
Labels:

Comments

Post a Comment

Popular posts from this blog

What's Wrong with OOP

Proponents of Object Oriented Programming feel the paradigm yields code that is better organized, easier to understand and maintain, and reusable. They view procedural programming code as unwieldy spaghetti and embrace OO-centric design patterns as the "right way" to do things. They argue objects are easier to grasp because they model how we view the world. If the popularity of languages like Java and C# is any indication, they may be right. But after almost 20 years of OOP in the mainstream, there's still a large portion of programmers who resist it. If objects truly model the way people think of things in the real world, then why do people have a hard time understanding and working in OOP? I suspect the problem might be the focus on objects instead of actions. If I may quote from Steve Yegge's Execution in the Kingdom of Nouns : Verbs in Javaland are responsible for all the work, but as they are held in contempt by all, no Verb is ever permitted to wander about ...
9 comments
Read more

Does Esperanto-USA have a Transparency Problem?

I’ve been an active member of Esperanto-USA for many years, even serving on its board of directors. I wanted to help build a strong, healthy national organization that effectively promotes Esperanto in the United States. But when I stepped down from the board, that desire didn’t end. I continued to bring problems to the attention of the organization, ranging from member rights to strategy to proper governance. I’ve decided to be public about this latest issue because of its seriousness and because of how the board has been secretive about it. The membership deserves to know what is done in their name. What Happened In November 2025, the board of Esperanto-USA sent a formal letter to Esperanto-Ligo en Israelo (ELI) with a copy to UEA, concerning an article published in ELI’s bulletin. The article, written by Eduardo Topol, contained inflammatory political content. And although I agree that the article was extremely offensive, the board’s decision to inj...
Post a Comment
Read more

Composing Music with PHP

I’m not an expert on probability theory, artificial intelligence, and machine learning. And even my Music 201 class from years ago has been long forgotten. But if you’ll indulge me for the next 10 minutes, I think you’ll find that even just a little knowledge can yield impressive results if creatively woven together. I’d like to share with you how to teach PHP to compose music. Here’s an example: You’re looking at a melody generated by PHP. It’s not the most memorable, but it’s not unpleasant either. And surprisingly, the code to generate such sequences is rather brief. So what’s going on? The script calculates a probability map of melodic intervals and applies a Markov process to generate a new sequence. In friendlier terms, musical data is analyzed by a script to learn which intervals make up pleasing melodies. It then creates a new composition by selecting pitches based on the possibilities it’s observed. . Standing on Shoulders Composition doesn’t happen in a vacuum. Bach wa...
9 comments
Read more