Feature: `ifProp` and `ifFeatProp` - [merged]

[benloh]

Merges dev-bl/if -> dev-next

Branch: dev-bl/if

This adds two new keywords: ifProp and ifFeatProp targeted at making it easier for students to construct if statements. ifExpr still works.

ifProp

ifProp lets you construct conditions taking advantage of built-in gvar prop methods. e.g.

  `ifProp Fish.energyLevel gt 0 [[ ... ]]`
  `ifProp Fish.name eq 'Wanda' [[ ... ]]`

ifFeatProp

Similarly, ifFeatProp accesses gvar prop methods for featProps. e.g.

 `ifFeatProp Fish.Movement.movementType eq 'stop' [[ ... ]]`
 `ifFeatProp Fish.Costume.scale lt 1 [[ ... ]]`

ifProp comparison to another prop

ifProp has a code-only feature that allows you to use another property as the argument for a prop method. e.g.

  `ifProp Fish.energyLevel gt Fish.threshold [[ ... ]]`

But there are a few caveats:

• there is no GUI support for entering or modifying this, it needs to be entered in the CODE view
• it will display as an error in the wizard.

prop methods

Note that prop methods are strings, not symbol operators (e.g. gt, not >). The methods are actual javascript method names, so it is not easy to use symbols to replace them. That can potentially be a 2.0 feature.

The prop methods can be entered using the GUI, so it should be relatively easy to construct the if statements. And like other block commands, the consequent block will be added automatically when you create or edit the line.

[benloh]

requested review from @jdanish

[benloh]

added 1 commit

• 189f619a - if: Add `notEq` gvar methods. Expose number comparison methods.

Compare with previous version

[benloh]

In GitLab by @moravick on Aug 29, 2022, 08:33

could we get a list of the working prop methods? i.e. eq, gt, etc?

[benloh]

@moravick there's two ways you can do this:

The easiest is actually to use the GUI: Do an addProp for each proptype (string, number, boolean), then do a prop xxx <method>. You'll see all the methods listed. Then do the same for each feature (e.g. featProp xxx <method>

The second easiest way is to code dive: search for class-sm-string, class-sm-number and class-sm-boolean. At the bottom of the file is a list of methods. Then search for feat-agentwidgets (etc.) and look for the list of methods at the bottom of the file.

[benloh]

added 1 commit

• 0ac65784 - if: agentObjRef and featObjRef need to use the spec'd agent's properties, not...

Compare with previous version

[benloh]

added 1 commit

• 7f9931b6 - if: agentObjRef should not fail if objref is not yet defined.

Compare with previous version

[benloh]

In GitLab by @jdanish on Sep 3, 2022, 07:54

I think this can be merged in with help.

[benloh]

mentioned in commit ae3104b18445b6d3d78f899f637a035646f9909f

[benloh]

Merged with feature-help branch in !268