Add BreakBeforePoint + Break on component lifecycle

[Nyan11]

No description provided.

[Nyan11]

[Nyan11]

[LabordePierre]

@Nyan11 I think we need to clarify two cases:

• Object Centric Breakpoint
• No-Object Centric Breackpoint (classic)
  This can be done by explicit labels (not sur to know if this OCB or not).

Other remark:

• A component can be re-activated after passivation, not only when a new component is create. This is why I'm asking on top. Example: Can I add a breakpoint on passivate for "this" component (#default) of for all components with this "component type"?

[Nyan11]

@Nyan11 I think we need to clarify two cases:

Object Centric Breakpoint
No-Object Centric Breackpoint (classic)
This can be done by explicit labels (not sur to know if this OCB or not).

I agree, i think there should be 2 type of logos:

• The "!" red: for classic breakpoint.
• A "!" + something else for object-centric.

This change should be done also in the PharoDebugger project.

• A component can be re-activated after passivation, not only when a new component is create. This is why I'm asking on top. Example: Can I add a breakpoint on passivate for "this" component (#default) of for all components with this "component type"?

In the inspector of deployed components:

• Halt once when #initialize is a classic Breakpoint. It will break on any new instance (or the same instance).
• Halt once when #activate is a classic Breakpoint. It will break on any new instance (or the same instance).
• Halt when #passivate is an Object Centric Breakpoint. It will only break for this instance.
• Halt when #remove is an Object Centric Breakpoint. It will only break for this instance.

In the browser:

• Break once on #componentInitialize is a classic Breakpoint. It will break on any new instance (or the same instance).
• Break once on #componentActivate is a classic Breakpoint. It will break on any new instance (or the same instance).