On Oct 1, 10:08 am, Itamar O <[email protected]> wrote:
> don't read this as a complaint, but as a use-case for the generic object > model, combined with the tabbed views concept (e.g. wiki's should also have > cc-fields, and a discussion view (facet? :-) ), that can exist "behind" the > "current content"). I'm am currently working hard to prepare AnnouncerPlugin for inclusion in Trac proper. It includes a wiki "watcher" that allows users to simply click a "Watch This" link to receive change notifications on wiki pages. This, in my opinion, is a much better experience then adding a CC field, although that could be useful too. This doesn't help users who haven't gone to their preference page and setup an email address though. Perhaps we could (eventually) introduce a workflow where, if you don't have an email address and click "Watch This", you are prompted to enter one, then sent back to the referrer. The GenericTrac does affect my work, and I have added some comments in certain places. It would certainly reduce the amount of code required for announcer, but it wouldn't be a drastic reduction. Only a small amount of code is concerned with event listeners. Shameless plug: Anyway, I'd love help/feedback with announcer if anyone is interested. If you don't code, even documentation would be helpful. Feedback would be especially helpful. -- 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.
