<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16825" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><SPAN class=718023007-28042009><FONT face=Arial
color=#0000ff size=2>Hello<SPAN class=593373707-28042009> Drew and
Alex</SPAN>,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=718023007-28042009><FONT face=Arial
color=#0000ff size=2>writing a new interface to RT would be a significant
effort, whatever tools you have. The approach we took was to leave the
interface as its is just to change</FONT></SPAN></DIV>
<DIV dir=ltr align=left><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=718023007-28042009>the most used parts to adopt them to our needs. Once
the user le<SPAN class=593373707-28042009>a</SPAN>ves the customized page, he
ends up with a standard RT interface. Like this you are sure that none of RT
functionality<SPAN class=593373707-28042009> </SPAN></SPAN><SPAN
class=718023007-28042009>will be lost. RT interface is constructed
from perl Mason components, you can override these components in
order to remove some <SPAN class=593373707-28042009>parts you do not
need</SPAN>.</SPAN></FONT></FONT></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=718023007-28042009>That's not difficult to do, and RT </SPAN><SPAN
class=718023007-28042009>provides the mechanisms to do it safely. <SPAN
class=593373707-28042009>You have to familiarize yourself with Mason, but the
basics are quick and easy to
grasp.</SPAN></SPAN></FONT></FONT></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial><FONT color=#0000ff><FONT size=2><SPAN
class=718023007-28042009></SPAN></FONT></FONT></FONT><FONT face=Arial
color=#0000ff size=2></FONT> </DIV>
<DIV><SPAN class=593373707-28042009><FONT face=Arial color=#0000ff
size=2>Cheers,</FONT></SPAN></DIV>
<DIV><FONT face=Arial color=#0000ff size=2><SPAN
class=593373707-28042009>Arnas</SPAN></FONT></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> rt-devel-bounces@lists.bestpractical.com
[mailto:rt-devel-bounces@lists.bestpractical.com] <B>On Behalf Of </B>Alexander
Finger<BR><B>Sent:</B> Monday, April 27, 2009 4:42 PM<BR><B>To:</B> Drew Barnes;
rt-devel@lists.bestpractical.com<BR><B>Subject:</B> Re: [Rt-devel] Writing a GUI
on top of RT<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV>Hi,</DIV>
<DIV>we did some work on the UI (which unfortunately did not go the way I wanted
it to be ... but anyways); RT has a RESTful interface which makes it relatively
easy to integrate with whatever GUI you chose to design. Thinking about it -
even an Adobe-AIR-based Desktop client should be doable quickly (wow, RT on the
Desktop..). I've done a stub for OpenNMS and that was really easy. </DIV>
<DIV> </DIV>
<DIV>IMHO, with Ajax or AIR and REST you can quickly come up with a slicker user
experience. I have no experience with the Selfservice interface so far but might
be I find an hour tonight to install RT again and look at it.</DIV>
<DIV> </DIV>
<DIV>best</DIV>
<DIV>Alex<BR><BR></DIV>
<DIV class=gmail_quote>On Mon, Apr 27, 2009 at 3:41 PM, Drew Barnes <SPAN
dir=ltr><<A
href="mailto:barnesaw@ucrwcu.rwc.uc.edu">barnesaw@ucrwcu.rwc.uc.edu</A>></SPAN>
wrote:<BR>
<BLOCKQUOTE class=gmail_quote
style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Have
you looked at the SelfService interface<BR>(<A
href="http://your.rt.server/SelfService"
target=_blank>http://your.rt.server/SelfService</A>)? It is much less
cluttered and by<BR>default lets an unprivileged user see only tickets they
have opened or<BR>(with one click) resolved tickets they have
requested.<BR><BR>If end users are left unprivileged, they will be directed
there by<BR>default.<BR>
<DIV class=im><BR>vxtrq wrote:<BR>> Greetings,<BR>><BR>> Where I
work, the technical department use RT for handling support errands,<BR>>
which works great. We would like, however, to let more non-technical<BR>>
departments use RT for the same purpose. I feel however that the RT GUI is
a<BR>> bit too technical for most of the people I have in mind, and we've
been<BR>> thinking about writing our own GUI on top of it, a very easy
and<BR>> non-technical one.<BR>><BR>> Have anyone done this before?
Is it doable? From what I've understand, there<BR>> are several RT Perl
Modules that can be used for this.<BR>><BR>> Any general
tips?<BR>><BR>> Thanks,<BR>> Robert<BR>><BR><BR>--<BR></DIV><FONT
color=#888888>Drew Barnes<BR>Applications Analyst<BR>Network Resources
Department<BR>Raymond Walters College<BR>University of Cincinnati<BR></FONT>
<DIV>
<DIV></DIV>
<DIV class=h5><BR>_______________________________________________<BR>List
info: <A
href="http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel"
target=_blank>http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-devel</A><BR></DIV></DIV></BLOCKQUOTE></DIV><BR></BODY></HTML>