Jesse,
I would like to contribute some patches to RT so that a
different CSS would be used when printing. Some of the
menus and input don’t make sense when viewing a ticket
or search result on paper. What’s needed first to
support this is some additional classes and ids to
identify parts of the interface. This should be pretty
straight forward.
Would you want using a print stylesheet an option for
the config file or just on for everybody?
Also, we could have one CSS for screen and one for
print, or they could be combined. Do you have a
preference?
Finally, do you think this is a good idea at all?
Thanks!
-Todd
Todd,
I’m looking forward to a more proper fully css-driven RT UI. I know
we’re not there yet, though RT 3.3 is a bit better than 3.2.
I believe that using different stylesheets for web and print is
recommended, rather than using one combinded sheet for both media.
I don’t think there’s any reason to make this a configured option,
rather than just included in the core dist.
JesseOn Tue, Oct 05, 2004 at 04:02:24PM -0400, Todd Chapman wrote:
Jesse,
I would like to contribute some patches to RT so that a
different CSS would be used when printing. Some of the
menus and input don’t make sense when viewing a ticket
or search result on paper. What’s needed first to
support this is some additional classes and ids to
identify parts of the interface. This should be pretty
straight forward.
Would you want using a print stylesheet an option for
the config file or just on for everybody?
Also, we could have one CSS for screen and one for
print, or they could be combined. Do you have a
preference?
Finally, do you think this is a good idea at all?
Thanks!
-Todd
Should I just submit patches against 3.3, or do you want
patches against 3.2 and then merge?
Also, while I’m at it I can convert some of the tables
to proper DIVS and SPANS…
-ToddOn Tue, Oct 05, 2004 at 04:47:16PM -0400, Jesse Vincent wrote:
Todd,
I’m looking forward to a more proper fully css-driven RT UI. I know
we’re not there yet, though RT 3.3 is a bit better than 3.2.
I believe that using different stylesheets for web and print is
recommended, rather than using one combinded sheet for both media.
I don’t think there’s any reason to make this a configured option,
rather than just included in the core dist.
Jesse
On Tue, Oct 05, 2004 at 04:02:24PM -0400, Todd Chapman wrote:
Jesse,
I would like to contribute some patches to RT so that a
different CSS would be used when printing. Some of the
menus and input don’t make sense when viewing a ticket
or search result on paper. What’s needed first to
support this is some additional classes and ids to
identify parts of the interface. This should be pretty
straight forward.
Would you want using a print stylesheet an option for
the config file or just on for everybody?
Also, we could have one CSS for screen and one for
print, or they could be combined. Do you have a
preference?
Finally, do you think this is a good idea at all?
Thanks!
-Todd
–
Should I just submit patches against 3.3, or do you want
patches against 3.2 and then merge?
I’d prefer for this sort of thing to be against 3.3 (until that freezes,
then I’ll want em against 3.5)
Also, while I’m at it I can convert some of the tables
to proper DIVS and SPANS…
nod Do try to be careful not to totally break RT in w3m, though 
nod Do try to be careful not to totally break RT in w3m, though
me too. I use w3m a lot with RT. It’s mighty handy
over a triple-hop ssh session via my phone. Please don’t break it 
A
Andrew Sullivan | ajs@crankycanuck.ca
The fact that technology doesn’t work is no bar to success in the marketplace.
–Philip Greenspun