Hi Best Practical Folks, Hi Everyone,
We are big fans of RT, we use it as an in-house project management,
ticketing, document management system (and CRM :)).
We have helped start using RT for dozens of companies and organizations as
well.
We love RT for its customization possibilities, its flexibility, its
community, and surely because we are commited to RT since we have been
working on RT daily for 8 years.
Now we would like to make a new theme, something that makes non-tech users
fall in love at first sight. ((And we will release some new plugins like:
- drag-n-drop organizing tickets (among saved searches),
- per queue customizable ticket look-and-feel.))
Our goal is to make RT more desirable for everyday people.
For this reason we (more precisely: our designer friends) would ask for
inserting a lot of divs (with classes, ids) into certain points of the
code. I think it is not easy since it could cause structural changes on the
html pages of RT.
My question is: what do you think is the best way to make it? I mean how to
avoid old themes from disruption and keep our contribution being an RT
friendly one? And how to create this theme to a maintainable contribution?
- Can we propose lots of new divs into the code (in git)?
- Or should we insert callbacks, and into the callbacks should we put the
new divs? In this case we should have closer tag () callbacks too.
- Any other idea?
Thanks,
Ákos
Our goal is to make RT more desirable for everyday people.
++ 
For this reason we (more precisely: our designer friends) would ask for
inserting a lot of divs (with classes, ids) into certain points of the
code. I think it is not easy since it could cause structural changes on
the html pages of RT.
There are already a lot of divs and what not in RT. While the HTML
structure could use some cleanup, it’s not completely hopeless either.
I think you’ll be more successful as a community contribution if you
approach with the intention to make as few HTML changes as possible
rather than the intention of redoing most of it.
My question is: what do you think is the best way to make it? I mean how
to avoid old themes from disruption and keep our contribution being an
RT friendly one? And how to create this theme to a maintainable
contribution?
- Can we propose lots of new divs into the code (in git)?
Yes, you can create a branch and do your hacking there. If you want it
to be considered for merging into core, it’ll need to be well written
and a reasonable set of changes (i.e. not superfluous “just because”).
Any large scale core changes to HTML will need to be against master, not
the 4.0-trunk series, since changing it mid-release series may break
existing customizations folks are using.
Check out our hacking doc:
http://bestpractical.com/rt/docs/latest/hacking.html
- Or should we insert callbacks, and into the callbacks should we put
the new divs? In this case we should have closer tag () callbacks too.
While callbacks are nice for some things, this use case gets ugly quick.
I’d recommend against it.
- Any other idea?
If you need to do some DOM manipulation that isn’t too extensive, you
could use a bit of custom JS to move things around. It’s not a great
solution, but perhaps a stop gap until the core HTML is better.
Hi Ákos, I only joined the RT forum here recently and just noticed your post.
We actually are looking at doing the same thing, make the RT UI (and UX)
look-n-feel better.
How is your initiative going (we haven’t started yet)? Are you using a
front-end framework at all?
http://requesttracker.8502.n7.nabble.com/rt-devel-RT-Tracker-styling-look-n-feel-td53550.html
akos.torok@docca.hu wrote
Now we would like to make a new theme, something that makes non-tech users
fall in love at first sight. ((And we will release some new plugins like:
- drag-n-drop organizing tickets (among saved searches),
- per queue customizable ticket look-and-feel.))
Our goal is to make RT more desirable for everyday people.
View this message in context: http://requesttracker.8502.n7.nabble.com/rt-devel-New-RT-theme-love-at-first-sight-maker-theme-tp53190p53675.html
Hi Geert,
We are going to start a similar direction as you mentioned in the “styling
look n feel” thread. I just want you to know that our new initiative is on
the RT users list, since it has more traffic.
Regards,
ÁkosOn Mon, Apr 29, 2013 at 11:02 AM, Geert Claes geert.wl.claes@gmail.comwrote:
Hi Ákos, I only joined the RT forum here recently and just noticed your
post.
We actually are looking at doing the same thing, make the RT UI (and UX)
look-n-feel better.
How is your initiative going (we haven’t started yet)? Are you using a
front-end framework at all?
http://requesttracker.8502.n7.nabble.com/rt-devel-RT-Tracker-styling-look-n-feel-td53550.html
akos.torok@docca.hu wrote
Now we would like to make a new theme, something that makes non-tech
users
fall in love at first sight. ((And we will release some new plugins like:
- drag-n-drop organizing tickets (among saved searches),
- per queue customizable ticket look-and-feel.))
Our goal is to make RT more desirable for everyday people.
–
View this message in context:
http://requesttracker.8502.n7.nabble.com/rt-devel-New-RT-theme-love-at-first-sight-maker-theme-tp53190p53675.html
Sent from the Request Tracker - Dev mailing list archive at Nabble.com.