[rt-users] New UX for RT: REST 2.0, json, and what?

[akos.torok at docca.hu]

Hi All,

This is some kind of request for comment. Please, feel free to give us
advice, support, ideas. If you have similar effort, if you know any
solution that makes this problems causeless, let us know please!

Thanks,

Ákos

You can find this (and comment and contribure) here:
http://requesttracker.wikia.com/wiki/RT_new_UX

Goal in terms of real life:
==================
Keep RT alive as a competitive system in 2014.
We like RT, we have a lot of competency related to RT, but our clients
require such UX as FBook, gmail, etc. They want
http://en.wikipedia.org/wiki/Single-page_application

Goal in terms of development:
======================
We are going to develope a brand new user interface - in v1.0 just for the
most popular pages. Our goals are:
- server side: let us use RT as a stable, secure, safe, functuon rich
server side system,
- user side: "click as few as it possible", few page reload, simple,
towards to single page app.

User functions
==========
We are going to create a limited functionality in v1.0:
- login
- Dashboards (including: home page)
- One page Display.html: that means Display.html is combined with
Update.htm and all the standard and custom fields user actions. User can do
all the actions on the same web page without navigation away: user can see
the history, add comment, edit fields. No transaction CFs supported in the
v1.0.
- Results (new ajax grid, table). I mean: user can filter, sort the rows,
and maybe edit the results list's fields. Without clicking away from the
page.
- Create new ticket

Architecture overview:
================
Our architecture vision is so simple:
RT <-> REST v2.0 <-> JSON <-> client's browser

REST v2.0
========
We are going to extend the REST API. We create new functions and replace
the old ones, since we are going to use JSON.

In client's browser
=============
We have no idea which framework or solution is the best, we never used any
of them. Every help is appreciated.

Thanks for any comment!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20140306/eef2a12b/attachment.htm>