ext [EMAIL PROTECTED] wrote: [...] >> Which has the disadvantage of taking some more memory, but the >> advantage >> of being sensibly simpler. > > I disagree: you expose the client to the science of expression forms; in the > example above, it has to duplicate mandatory conditions in every term in the > OR disjunction. Arbitrarily complex expressions are possible, which is > problematic with UI representations. With the two-level structure, updates > and notifications become either more complex, or less efficient.
Ah, now I see that I didn't understand your proposal; so, you mean to have only one rule per account, consisting of a list of Account_Conditions and Account_Condition_Rules, right? If so, then, you will not be able to express a condition like this: connect the account if (A and B) or (C and D), but since I cannot think of a single case where we might need similar conditions, I guess we can forget about it. And then, indeed, your proposed scheme is definitely simpler. [...] >> In the latter proposal, we could combine them so that the conditions >> specified in the .manager and .presets files will be appended to every >> rule specified in the accounts; > > I'm wary about such a combination. > Let's have the condition parameters override the presets, as do any other > account parameters. If the condition namespaces are the same, yes; but if some condition appears in the presets and not in the account, it should be taken into consideration, too. Ciao, Alberto -- http://www.mardy.it <-- Geek in un lingua international! _______________________________________________ Telepathy mailing list Telepathy@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/telepathy