Do we want hosts and universe Beacon signals?

[tinchodias]

These Beacon signals are only signaled (i.e. only referenced to emit an instance):

They allow a developer to turn on a Beacon logger and watch what happens under the hood.

I create this issue to discuss if either we start to use them to debug, or we remove them and just debug this code as with other projects.

IMHO, this code doesn't help: it makes Bloc a bit harder to comprehend, and just regular Pharo debugging and profiling tools and are enough to debug or understand what happens under the hood.

Reasons would be similar for deleting telemetry months ago: #439

[tinchodias]

Note: without those signals, the BlParallelUniverse's id becomes not necessary.

[tinchodias]

@plantec @labordep do you agree on removing these classes?

[labordep]

@tinchodias I agree with you.

[plantec]

yes

[tinchodias]

BlParallelUniverse is so much simplified after removing the signal emitting!

[tinchodias]

Only one Beacon signal remains: BlParallelUniverseErrorDuringPulseSignal (the Signal suffix was missing and I added it)

[tinchodias]

In part, I had the idea to remove the signals because they were quite 1:1 with BlSpaceEvent*s. I mean, handling events looked enough to generate a log, and also events are more oriented to react via handlers as a user software.

In that sense, BlParallelUniverseErrorDuringPulseSignal may be replaced by a new BlParallelUniversePulseErrorEvent.

[labordep]

hi @tinchodias, with @Nyan11 we for doing stuff when a space is open with Pyramid (to install a keyboard shortcut to edit it), what event can we used?