The DecisionMaker editor currently supports one primary kind of editing: replacement. If the storybuilder selects a term and then a menu item, that menu item is put in place of the selected term. Along the way, any internal arguements of the term are tossed out. This can be aggravating. I propose several other options:
Outsertion: This is already in place for the dyadic operators. Outsertion places the newly chosen operator in front of the already selected operator. In the full-blown version of outsertion, we would enable any menu item that includes the data type of the selected term as one of its arguements. Problem: if there are several appropriate arguements, which one should be used? I suppose that the first would be the best choice; the storybuilder can always rotate arguements. Outsertion would have to be selectable with a prefix key such as the control key. I would then have to carry out an on-the-fly menu enabling/disabling routine. That might be a bit of work.
Insertion: This does not exist in any form as yet. In this form of editing, the chosen menu item is substituted for the selected term without changing any of the internal arguements. This could be a valuable editing capability. Again, I would have to assign a prefix key (option) to indicate this capability and then perform a frantic on-the-fly enabling/disabling routine. This would be even more stringent than the earlier one, as the parameter list of the available menu item would have to exactly match the existing parameter list. That would be quite a chore!
Replacement: this is what we currently have. Dumb, but simple.
Now, do I really want to implement these features?