> Besides error intractability, there is also a cost to understanding the > system via exploration - a glorious benefit of Morphic. In the past, one > only had to bring up halos on and inspect a button to see how to duplicate > its action. Now, to see what happens when one presses Versionner's "Commit > the project" button, you have to drill down in the inspector from > aButtonXyzMorph -> model -> actionHolder -> value, a tedious and opaque > process.
> Of course, I'm not in any way against Spec or its goals, just sharing my > unfolding experience using it. I'm running Squeak 4.0 but I assume my question still applies. If not, other Pharo users might want to know. I am not in the habit of using halos, not really sure what they are for. But your description implies they are quite useful. What does "bring up halos on and inspect a button to see how to duplicate > its action" mean? Could you please describe in step by step detail. Ralph Boland
