On Nov 1, 9:49 am, Remy Blank <[EMAIL PROTECTED]> wrote: > Noah Kantrowitz wrote: > > See also:http://trac-hacks.org/browser/adminconsoleproviderpatch/0.9 > > > One of the first things ever posted to trac-hacks ;-) > > Thanks for the reference, I didn't know about that patch. > > Mmmh... It doesn't seem to apply cleanly... ;-) > > More seriously, this opens a few questions: > > - Should the admin commands be placed into separate components? I was > going to integrate them into either the *System components, or the admin > panels. The patch above creates separate components. > > - Should it be possible for a plugin to safely override existing > commands? I would say no, as this might make support more difficult.
Interesting questions. My preference would be to split them up into many components. That way they can be easily disabled and replaced by other components. For instance if some permission-related plugin wants to replace the default permission commands, it can disable that component only and provide its own implementation for 'permission....' handling. By having many clearly defined components, I don't think it would not be necessary to provide support for overriding. :::simon https://www.coderesort.com --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
