> -----Original Message----- > From: [email protected] [mailto:[EMAIL PROTECTED] On > Behalf Of Nicholas Bergson-Shilcock > Sent: Friday, June 20, 2008 3:42 PM > To: [email protected] > Subject: [Trac-dev] Re: Registration confirmation for AccountManager > > > Thanks, I hadn't seen #874. The interface described there is similar > to what I proposed, though I think it might be better in a few > respects. E.g., the code from #874 includes two separate interfaces > (IRegistrationFieldProvider and IRegistrationManipulator), which makes > things a bit more general than what I did. I posted a link to my patch > along with a note about the interface differences on the ticket. > > Also, I noticed in the original patch submitted by coderanger in #874 > that there is code to support adding both optional and required > fields. This seems likes A Good Idea to me. Ideally, it would handle > cases where two plugins add fields of the same name, where one of them > is optional and the other is required. In this case the required field > would subsume the optional one. > > Do you know what the present state of #874 is? Are there plans to roll > the patch into AccountManager?
Given that stream filters are now available, I would rather see people use those to alter the UI before adding such single-case extension points. You can use a request filter to handle the verification step. --Noah --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Trac Development" 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/trac-dev?hl=en -~----------~----~----~----~------~----~------~--~---
