Quoth Glenn Skinner on Wed, Jun 28, 2006 at 01:49:16PM -0700: > The NWAM section contains the following paragraph: > > To determine the precedence of active profiles, both active and > inactive profiles will carry a precedence attribute, which the user > may modify. Profiles with equal precedence will be arranged in the > order that they were activated (most recent on top). Precedences > will be expressed as floating point numbers between 0 and 1. The > local profile will have the highest precedence (1.0 + ?), and the > base profile will have the lowest (0.0). The precedence of other > profiles will default to 0.5. This should free NWAM from needing to > store profile precedence in NWAM-specific configuration. > > Adding a notion of precedence begs the question of how precedence > values should be assigned. If I'm developing a profile, how should I > go about picking a precedence value? How can I be sure that the value > I pick won't interfere with (or be interferred with by) the value some > other profile developer chooses?
I don't think the precedence should be up to the developer. I think it's an administrative choice. I'll clarify that in the next version. David
