New name suggestions?

[renyuneyun]

So, there are some/many issues about the un-intuitive names for some elements of Easer. I also hate the bad names but don't really have good proposals.

Now, as I'm doing lots of refactoring to allow remote plugins in Easer (which will be presented in v0.7) and reading new users get confused, I also think it's time to get good names in this version (or soon).

#94 proposes some possible changes. However the names there include plurals which I don't think is a good idea. From this proposal and some later thoughts, I have the following prepared, but expect everyone (interested) to spread your opinions.

Script ==> Task Profile ==> Script

The motivation is:

• "Script" can often be seen as a series of actions, at least on computers. This lies exactly with what we currently call "Profile" intends to provide.
• However, if we rename Profile to Script, there is a naming conflict.
• The current "Script" provides two functions:
  1. A node in a state tree, containing the Event and Condition states
  2. An associate of actions to be performed with the node (when the node is "satisfied")
• (As also mentioned by @natrius ) "Task" can mean to "do something when something is met"

Any ideas?

p.s. discussion also welcomed in the chatroom (see README)

[spaetz]

Hi there, I would keep the profile name as is. profiles are used in Lineageos (and even possibly AOSP?) and people I talk to have understood a profile as a certain set of system settings to be used. which fits.

What we call now script is perhaps better names 'trigger'? ie it describes the conditions and profiles and under which situation what action is triggered. I am a nonnative speaker myself though, so perhaps some English mothertongue could also weigh in here.

[natrius]

Not good imho. The trigger or event is what creates the task, action or a set of actions. Pull the trigger, weapon fires. Read NFC, Profile XY active. Time reached, profile YZ active.

[renyuneyun]

@natrius I think you meant to reply to @spaetz ?

@spaetz one of the ideas why I'd like to replace the name "Profile" is that "Profile" is considered "static" and only about "system settings" (at least from my point of view), but what this function intends to provide is a series of actions, which can include changing system settings, but can also include other actions (e.g. send network packet). There is also a plan to allow perform/trigger/load "Profile B" in "Profile A", which seems to break the meaning of a LineageOS Profile.

By the way, there is a Remote Plugin (Operation) of Easer which can load a LineageOS Profile. You can have a try if interested. It (/every Remote Plugin) acts as a normal action/Operation in a "Profile" in Easer, so you can combine it with other Operations too.

[natrius]

Yes, it was an reply to @spaetz , specially to the trigger part :)

[racuna]

I would change "Profile" to "Action" or "Task" (implying "do something"). Also, I will put "Events and Conditions" inside a section of "Triggers" (because is planned to get rid of the Events, IIRC)

Then the main menu sorted this way to make it more intuitive:

• Triggers
• Actions
• Scripts (disabled until user creates some Trigger and an Action first)

edit: correct some shitty english

[renyuneyun]

@racuna The plan is to remove some Events which should better be expressed as Conditions, not all Events ;p

Do you feel comfortable about the name "Script"? This is one of my main concerns about the names.

I prefer not to use plurals for the names, so "Action" doesn't seem like a good name; Condition doesn't seem like a trigger from my perspective. (I may be totally wrong about the meaning of "trigger".) (Even though I'm using "trigger" internally in Easer's storage of Scripts.)

[renyuneyun]

I have a name emerged from #178 : We can move "Event" and "Condition" to one section called "Atom", to reflect the design purpose.

However the weak point is that "atom" do not reflect the utilization purpose...

[spaetz]

Actually, I like the term 'condition' a lot. Seriously, I think it is more important to stick to the terms than to rename them to something incrementally better. Easer is hard enough to understand and by renaming the core concepts all current users need to relearn things 😃. So a term change only if it is MUCH better than before,please...

[natrius]

Can't see how anyone would have an idea about "Atom" at first sight. But i agree with apetz: Try to choose something you think is apropriate now and stick with it unless more and more people are complaining about a specific term.

And, i still don't see the problem with using plural. Es in every section multiple entrys are possible, it would be completely valid, using plural in english and german all over. You said you don't have plural in your mother tongue - don't use plural there, if its not possible.