[Rt-devel] Advice sought on RT plugin development.
Todd Chapman
todd at chaka.net
Tue Nov 30 13:50:40 EST 2010
Ruslan,
By dynamic I mean that an arbitrary number of portlets would be created
based on RT configuration. The number of portlets is determined at runtime,
not install. The portlets would be created with a dhandler.
On Tue, Nov 30, 2010 at 1:29 PM, Ruslan Zakirov <ruz at bestpractical.com>wrote:
> Hi,
>
> I don't know what you mean by dynamic, but I see it this way. Your
> extension puts a portlet into default "RT at Glance", you also mention
> this portlet in docs. That's it.
>
> On Tue, Nov 30, 2010 at 7:40 AM, Todd Chapman <todd at chaka.net> wrote:
> > Fellow RT Devs,
> > I'm working on an RT plugin and running into some implementation
> challenges.
> > 1. I'd like to dynamically add some components to the "RT at a glance"
> > preferences pane, but don't see any callbacks to do so.
> > 2. Even if I could do 1. above, or just manually edit the
> RT_SiteConfig.pm
> > file, my components don't really exist. I would like to generate their
> > output dynamically from a dhandler, but /Elements/MyRT uses $m->comp,
> which
> > doesn't activate dhandlers.
> > Can anyone think of solutions to these problems? Clearly I could submit a
> > patch to add support in core RT for this but thought someone might
> suggest
> > another solution.
> > Thanks!
> > -Todd
> >
> > _______________________________________________
> > List info:
> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel
> >
> >
>
>
>
> --
> Best regards, Ruslan.
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-devel/attachments/20101130/16d04d94/attachment.html>
More information about the rt-devel
mailing list