MIPs on controls

As part of my action to write spec text for MIPs on controls, doing an 
analysis of the best approach, the only thing I would like to discuss at 
the call today is how we'd best like to separate @calculate from the rest.

It seems to me that the two options are:

1. remove @calculate from MIPs, and then use MIPs on both <bind/> and 
controls, and treat @calculate specially on <bind/>
2. Keep @calculate in MIPs, and then forbid its use on controls.

I have a preference for 1. because since it is syntactic, it can be spotted 
earlier, and easier.

If we agree that that is the better approach, then I would make an 
attribute collection, let's say Properties, that contain all the MIPs 
except @calculate, then make <bind/> use that, and add calculate 
separately.
I would then add Properties to Control Common, and remove UI Common (all 
attributes being already in MIPs).

Does that sound like a plan?

Steven

Received on Friday, 26 April 2024 12:15:30 UTC