Neo: rename Trigger to ExecutionMode

[igormcoelho]

Many people are still confused by the name Trigger, so perhaps Neo3 could call it ExecutionMode. What do you think?

[shargon]

I think that is a good idea

[lock9]

I agree too. I think that ExecutionMode makes more sense

Sent from my iPhone

On 7 Jul 2019, at 12:59, Shargon [e-mail] wrote:

I think that is a good idea

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

[vncoelho]

agreed too.

[igormcoelho]

@erikzhang do you think this change is harmful to the whitepaper or any ecosystem perspective? if not, we can proceed soon in applying this fix.

[erikzhang]

I think Trigger is more accurate. For example, in the future we add "Timer" as a new trigger?

[igormcoelho]

Well.. so Trigger may indeed become a timer trigger at some point hahaha if scope is not closed yet, so we better keep the name and let things flow.

[vncoelho]

ahauheshahau, keep Triggering.

[lock9]

If we have a new Timer Trigger, we can create a "Scheduled Execution Mode" (example).
For the user (Smart Contract developer), it is not a trigger, it is a context. Could we reconsider closing this?