Kevin Dangoor wrote: > Hi Simon, > > On 4/2/06, Simon Belak <[EMAIL PROTECTED]> wrote: >> Just a heads-up. In [1066] I committed >> turbogears.genericfunctions.MultiorderGenericFunction class allowing >> fine-tuning of resolution order. > > That looks like a nice, simple solution to the problem. One other > approach that we have a long standing ticket for (but may not apply > quite as generally as this) is to allow passing in of a context object > (could be anything) that the rule can inspect to help it make a > decision (that would automatically be more specific because those > rules have extra detail). > > Numeric indexes get unwieldy pretty quickly, but I realize that in > this case it's just an additional override.
In my experience adding "super" rules only delays precedence problems while pushing them completely into user space, requiring them to know all intricacies of RuleDispatch. If we do it right on the TG side, 90% of the time, a normal when (with order=0) should do. We could however provide a super_when (working name) to circumvent overriding one's own rules. Cheers, Simon P.S. I closed that "long standing ticket" ticket. ;) --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TurboGears Trunk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/turbogears-trunk -~----------~----~----~----~------~----~------~--~---
