cmd/alt-m handler fails "wysiwyg"

[WardCunningham]

We speculated, simple alt-m handler, might be best #206

We now think that this is not the case as explained in the following explanation quoted from chat.

I've had a few minutes this morning to look at Eric's make-a-new-plugin page and have found sure evidence of an "uncompleted cmd-m". This is an item from the page where a new type had been selected but no action sent that persists the selection.

    {
      "type": "factory",
      "id": "3888ea132a89c4f3",
      "text": "Tip: use conditions to export the right functions the right way at the right time:"
    },

We have no action that says "change type", only an action that says "replace whole item with edited version, including new type". The cmd-m sequence could have ended with this second action except that the text editor won't save a change that doesn't change the text.

This is not desirable behavior. This fails the "what you see is what you get" test. Eric sees the completed type conversion on his screen but has the conversion suspended at the factory menu state as persisted on his server.

[WardCunningham]

I am now of the opinion that selecting a type from the factory menu should emit an edit action AND not return to the text editor as it now does. This will be NEW behavior for the factory menu which has been coded to always enter the editor after a type selection.