Hi Ralph, On Mon, Oct 20, 2014 at 9:08 AM, Ralph Boland <rpboland@gmail.com> wrote:
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 would upgrade to 4.5 asap. That's ancient. Are you still using the interpreter VM? If so, you can change to the JIT. It's a lot faster. And to the Spur VM which is faster still.
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.
Right click on any window. Then grab the Swirl halo (dark blue) and tug it. Quite useful I'd say ;-) [image: Inline image 1] The rotation halo might be only for fun, but many of the others are really useful, allowing you to move, delete, inspect, take an image, copy, etc, etc, etc. -- best, Eliot
