Fellow RT Devs,
I’m working on an RT plugin and running into some implementation challenges.
-
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.
-
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
Just a guess, Todd, but Saved searches do this trick… maybe you can crib the technique or emulate it from that code.
-Andy D’Arcy Jewell (Just an RT/Perl Newbie)
Just a guess, Todd, but Saved searches do this trick… maybe you can
crib the technique or emulate it from that code.
Andy,
That would work if I was displaying search results, but I’m doing something
along the lines of the Quick Search component but a little more
complex/dynamic.
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@chaka.net wrote:
Fellow RT Devs,
I’m working on an RT plugin and running into some implementation challenges.
- 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.
- 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: The rt-devel Archives
Best regards, Ruslan.
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@bestpractical.comwrote:
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@chaka.net wrote:
Fellow RT Devs,
I’m working on an RT plugin and running into some implementation
challenges.
- 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.
- 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:
The rt-devel Archives
–
Best regards, Ruslan.
Hi Todd,
how about creating a simple portlet and within this you create your
dynamic portlets as “sub portlets”.
-ChrisAm 30.11.2010 19:50, schrieb Todd Chapman:
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.
Chris,
That is an interesting idea, though it limits the organization of portlets.
Thanks for giving me something to think about though!
-ToddOn Tue, Nov 30, 2010 at 2:39 PM, Christian Loos cloos@netsandbox.de wrote:
Hi Todd,
how about creating a simple portlet and within this you create your
dynamic portlets as “sub portlets”.
-Chris
Am 30.11.2010 19:50, schrieb Todd Chapman:
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.
I made a similar mod on my local installation, adding the ability to
display any number of arbitrary RSS feeds on MyRT. I had to override
Prefs/MyRT.html, so I don’t think there’s any way to do it without a
patch.
One callback in Prefs/MyRT.html giving access to the @items array should do it.
-BradOn Mon, Nov 29, 2010 at 8:40 PM, Todd Chapman todd@chaka.net wrote:
Fellow RT Devs,
I’m working on an RT plugin and running into some implementation challenges.
- 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.
- 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: The rt-devel Archives
This totally sounds like new type(s) of saved objects along with saved
searches, graphs and charts. These three can be saved with some
preferences and then added to home page and/or dashboard.
I think you should re-use this area.On Tue, Nov 30, 2010 at 9:50 PM, Todd Chapman todd@chaka.net wrote:
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@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@chaka.net wrote:
Fellow RT Devs,
I’m working on an RT plugin and running into some implementation
challenges.
- 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.
- 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:
The rt-devel Archives
–
Best regards, Ruslan.
Best regards, Ruslan.
Ah, I see how this works now! I had no idea that a saved object could
just be any arbitrary set of parameters and values.
I was able to convert my RSS feed mod to use this mechanism, storing
my RSS feeds as new type of saved search, and I don’t need to override
anything. The only somewhat awkward thing is that /Elements/ShowSearch
generates a TitleBox with pretty inflexible parameters and it might
make more sense for really dynamic portlets to take care of that
themselves.
-BradOn Tue, Nov 30, 2010 at 12:49 PM, Ruslan Zakirov ruz@bestpractical.com wrote:
This totally sounds like new type(s) of saved objects along with saved
searches, graphs and charts. These three can be saved with some
preferences and then added to home page and/or dashboard.
I think you should re-use this area.
On Tue, Nov 30, 2010 at 9:50 PM, Todd Chapman todd@chaka.net wrote:
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@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@chaka.net wrote:
Fellow RT Devs,
I’m working on an RT plugin and running into some implementation
challenges.
- 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.
- 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:
The rt-devel Archives
–
Best regards, Ruslan.
–
Best regards, Ruslan.
List info: The rt-devel Archives
Thanks Ruslan! I had forgot that saved searches had been generalized like
that.On Tue, Nov 30, 2010 at 3:49 PM, Ruslan Zakirov ruz@bestpractical.comwrote:
This totally sounds like new type(s) of saved objects along with saved
searches, graphs and charts. These three can be saved with some
preferences and then added to home page and/or dashboard.
I think you should re-use this area.
On Tue, Nov 30, 2010 at 9:50 PM, Todd Chapman todd@chaka.net wrote:
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@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@chaka.net wrote:
Fellow RT Devs,
I’m working on an RT plugin and running into some implementation
challenges.
- 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.
- 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:
The rt-devel Archives
–
Best regards, Ruslan.
–
Best regards, Ruslan.