Hello!
Here’s a greatly improved version of Quickpicks, with the following
improvements:
-
Cleaned up tremendously the nasty bookmark URLs I had in there;
I’ve come to understand better how to do plaintext GET URLs with
RT. [Note: This was easy thanks to all the work that Jesse’s
put into making RT modular and easy to understand. See
http://www.bestpractical.com/pricelist.html for ways you can
help RT continue to develop.]
-
The “Unresolved Tickets I Requested” pick now works and got moved
to the top as it felt like it should be near “Unrequested Tickets
I Own”
Quickpicks is a small WebRT element which adds a drop-down menu
containing searches and websites for easy selection. It’s smart enough
(just barely 
to open RT pages in the same window and open non-RT
pages into new windows. Only shows picks related to ticket ownership
(“Unresolved Tix I Own” etc.) to privileged users; unprivileged users
see only “Unresolved Tix I Requested” and any external links you
include.
Quickpicks owes its existance to Bruce Campell’s post of JumpBar
(thanks, Bruce!); that tool can be found at
http://lists.fsck.com/pipermail/rt-users/2002-January/006330.html
To add this to your RT Start Page:
-
Put Quickpicks in RTHOME/WebRT/html/Elements
-
chmod a+x Quickpicks
-
Add these two lines to RTHOME/WebRT/html/index.html
<& /Elements/Quickpicks &>
… above or below these two lines:
<& /Elements/Quicksearch &>
You may also want to add it to your
RTHOME/WebRT/html/Search/Listing.html and other places as well.
The great thing about being alive is learning. I’ve been having a great
time. =]
Cheers!
–j
Jim Meyer, Geek At Large purp@wildbrain.com
Quickpicks (2.49 KB)
Here’s a greatly improved version of Quickpicks, with the following
improvements:
Thanks for the great module!
I may have some more questions for this, but before I do, I have a question
about one of the queries.
Here are the queries, probably with mail composer munging.
Un
resolved Helpdesk Tickets
All Unresolved
Ti
ckets
Why does the first query have a ValueOfOwner setting? With it, the query
returns odd things, without it, it looks like it works.
If the second query differs from the first only by the queue we are looking
at, why are the queries so different from one another?
rob
Nice spin on the JumpBar, and another great submission by Jim. I find that
when I click on the list it is very narrow and I cannot read the list of
choices. Since it was such an easy install I’d assume it’s something local to
my RT2 install. I can probably find a way to modify it but I don’t want to
break anything and was wondering if anyone else is seeing this behavior?On February 12, 2002 04:11 pm, you wrote:
Hello!
Here’s a greatly improved version of Quickpicks, with the following
improvements:
-
Cleaned up tremendously the nasty bookmark URLs I had in there;
I’ve come to understand better how to do plaintext GET URLs with
RT. [Note: This was easy thanks to all the work that Jesse’s
put into making RT modular and easy to understand. See
http://www.bestpractical.com/pricelist.html for ways you can
help RT continue to develop.]
-
The “Unresolved Tickets I Requested” pick now works and got moved
to the top as it felt like it should be near “Unrequested Tickets
I Own”
Quickpicks is a small WebRT element which adds a drop-down menu
containing searches and websites for easy selection. It’s smart enough
(just barely to open RT pages in the same window and open non-RT
pages into new windows. Only shows picks related to ticket ownership
(“Unresolved Tix I Own” etc.) to privileged users; unprivileged users
see only “Unresolved Tix I Requested” and any external links you
include.
Quickpicks owes its existance to Bruce Campell’s post of JumpBar
(thanks, Bruce!); that tool can be found at
http://lists.fsck.com/pipermail/rt-users/2002-January/006330.html
To add this to your RT Start Page:
-
Put Quickpicks in RTHOME/WebRT/html/Elements
-
chmod a+x Quickpicks
-
Add these two lines to RTHOME/WebRT/html/index.html
<& /Elements/Quickpicks &>
… above or below these two lines:
<& /Elements/Quicksearch &>
You may also want to add it to your
RTHOME/WebRT/html/Search/Listing.html and other places as well.
The great thing about being alive is learning. I’ve been having a great
time. =]
Cheers!
–j
Nice spin on the JumpBar, and another great submission by Jim. I find that
when I click on the list it is very narrow and I cannot read the list of
choices. Since it was such an easy install I’d assume it’s something local
to
my RT2 install. I can probably find a way to modify it but I don’t want to
break anything and was wondering if anyone else is seeing this behavior?
What web browser are you using?
If I use mozilla 0.9.7, it works okay, with mozilla dropping down a listbox
which is wider than the ‘Choose one’ text seems to be (the ‘Choose one’ text
is cut off at the right end, near the down arrow).
konqueror (kde 2.2) does not display it correctly, I can’t read the whole
text.
Netscape does display it so I can read the whole thing.
Lynx displays it fine, but of course the javascript does not work.
Links would not authenticate to my SSL site, so I don’t know how it works.
w3m gave an unknown uri error on the https redirect, don’t know how it works.
I think that the best thing to do to “fix” the problem (which is a web browser
problem) is to change the “Choose one” text to read “Please make a selection
abcd abcd” or whatever, to make it as long as the longest text in the
dropdown. This could be done programmatically, instead of hardcoding it
in.
rob
[snip]
What web browser are you using?
If I use mozilla 0.9.7, it works okay, with mozilla dropping down a listbox
which is wider than the ‘Choose one’ text seems to be (the ‘Choose one’
text is cut off at the right end, near the down arrow).
Yeah Mozilla 0.9.8 works fine… I had tried it in Konqueror and IE5.x in
VMWare and both were broken… But your suggestion of making the initial
prompt longer is probably the ticket.
Thanks!
[snip]
What web browser are you using?
If I use mozilla 0.9.7, it works okay, with mozilla dropping down a
listbox
which is wider than the ‘Choose one’ text seems to be (the ‘Choose one’
text is cut off at the right end, near the down arrow).
Yeah Mozilla 0.9.8 works fine… I had tried it in Konqueror and IE5.x in
VMWare and both were broken… But your suggestion of making the initial
prompt longer is probably the ticket.
Well, I think that the proper way to fix it is to fix a whole lot of different
browsers, but that is a lot of hard work, which I do not have the resources
to accomplish.
From what we control here, the initial prompt is a workaround which we could
affect.
rob
Spoke too soon… Changing the length of the prompt didn’t work very well… So I manually did a tweak to /path/to/rt2/WebRT/html/Elements/Quickpicks :
Where ‘style=“width: 250px;”’ was originally ‘style=“width: 110px;”’…
Your mileage may vary… Font sizes and choices and text zoom settings all factor in…
-----Original Message-----
From: Rob Walker [mailto:rob@myinternetplace.net]
Nice spin on the JumpBar, and another great submission by
Jim. I find that
when I click on the list it is very narrow and I cannot
read the list of
choices. Since it was such an easy install I’d assume it’s
something local
to
my RT2 install. I can probably find a way to modify it but
I don’t want to
break anything and was wondering if anyone else is seeing
this behavior?
What web browser are you using?
If I use mozilla 0.9.7, it works okay, with mozilla dropping
down a listbox
which is wider than the ‘Choose one’ text seems to be (the
‘Choose one’ text
is cut off at the right end, near the down arrow).
konqueror (kde 2.2) does not display it correctly, I can’t
read the whole
text.
Netscape does display it so I can read the whole thing.
Lynx displays it fine, but of course the javascript does not work.
Links would not authenticate to my SSL site, so I don’t know
how it works.
w3m gave an unknown uri error on the https redirect, don’t
know how it works.
I think that the best thing to do to “fix” the problem (which
is a web browser
problem) is to change the “Choose one” text to read “Please
make a selection
abcd abcd” or whatever, to make it as long as the longest text in the
dropdown. This could be done programmatically, instead of
hardcoding it
in.
The width (in pixels) is set in a snippet of CSS code at the very end of the
tag. You could change the value to suit your needs, or you could
(as I did) just remove the CSS snippet, which allows the combo box to size
itself according to its widest entry. Jim probably figured that would make
the screen too wide and so he limited it.
I’ll second the “another great submission by Jim” comment. Jim’s only been
on the list for what, a couple months?, but he’s already become one of my
favorite posters. He’s picked up the internals of RT way faster than I have
and he’s given back some great stuff. And his posts are often entertaining.
Kendric Beachey
Spoke too soon… Changing the length of the prompt didn’t work very well…
So I manually did a tweak to /path/to/rt2/WebRT/html/Elements/Quickpicks :
Where ‘style=“width: 250px;”’ was originally ‘style=“width: 110px;”’…
Your mileage may vary… Font sizes and choices and text zoom settings all
factor in…
Wow. What happens if you don’t use a width style at all? Cannot a browser be
allowed to do The Right Thing, without prompting by the html code?
rob
Howdy!
The width (in pixels) is set in a snippet of CSS code at the very end of the
tag. You could change the value to suit your needs, or you could
(as I did) just remove the CSS snippet, which allows the combo box to size
itself according to its widest entry. Jim probably figured that would make
the screen too wide and so he limited it.
Change that last “Jim” to “Bruce Campbell of RIPE” and you’re probably
dead on; I didn’t frob that bit of code at all. However, I’ve now tried
it both ways and in several browsers and prefer it with the style
statement, so I’ll be leaving it in.
I’ll second the “another great submission by Jim” comment. Jim’s only been
on the list for what, a couple months?, but he’s already become one of my
favorite posters. He’s picked up the internals of RT way faster than I have
and he’s given back some great stuff. And his posts are often entertaining.
As Sir Isaac Newton said, “If I see farther than others, it is because I
stand upon the shoulders of giants.” RT’s design is straightforward and
intuitive, which makes the twiddling I’ve done so far very easy. The
praise should rest at Jesse’s doorstep – and did you know he does
consulting for a living? Request Tracker... So much more than a help desk — Best Practical Solutions for details.
As to entertaining, well, I do try. =]
Cheers!
–j
Jim Meyer, Geek At Large purp@wildbrain.com