Review BlSpaceFrameIdlePhase and BlSpaceFrame

[tinchodias]

A BlSpace has a BlSpaceFrame (i.e. space's main loop).
A BlSpaceFrame has a collection of phases. This allows, for example, Toplo's skins to add 2 new phases to a space on runtime.
Okay until here. But there is a phase that runs nothing:

added to default initialize:

I don't see the point on having BlSpaceFrameIdlePhase by default on spaces.

[plantec]

No idea, I would have the same question :)
I tried to remove it and no consequence for now

[tinchodias]

Let's remove the idle phase.

---

Additionally, I'd rename BlSpaceFrame. Why? To me, since first time I browsed it, the name of BlSpaceFrame is misleading:

A BlSpaceFrame has a sequence of phases that can be modified and run via its API. In this sense, a BlSpaceFrame corresponds to what is usually called a "main loop" in technologies to build desktop applications (and especially to create games).

A BlSpaceFrame also knows what is the next phase to be executed. So this "frame" represents a particular execution state of a "main loop" of a specific space.

I'd rename it as BlSpaceLoop or BlSpacePhaseLoop or BlSpaceMainLoop.

And I would either make it point to the associated space (now, it is received by parameter in runOn:), or move runOn: to BlSpace.

Also, I'd do something with the BlSpaceFrame's id (an instvar that starts in 0 and increments on each run). It is misleading to discover in the debugger that an object's id changes constantly during a window's lifetime, and then discover that in fact it is the number of loops done until creation. It could be renamed as iterationCount or frameCountor loopCount or runCount.

[tinchodias]

Additional note: There is an unreferenced BlIdleErrorHandler that strangely, I guess, would handle errors during the idle phase. A mystery for me.

edit: I removed this error handler

[tinchodias]

#871 removed idle phase