General > General Discussion

Proto Throttle

<< < (6/6)

G8B4Life:
I'm not arguing against you Al, everything you said is part of the good part of the RailPro user experience, my reference to  the LokProgrammer software was not about how powerful (and potentially complicated for some) it is but was about the user interface, it is neat, logical and doesn't look like a early 1990's 16 colour .pcx file (there, that's showing my computer age, I used .pcx images!).

The user experience is made up of both the functionality and the user interface to that functionality. Going back to DCC here for a minute, historically DCC has had a very poor UI for the functionality (those old 100 button throttles, having to work out CV's etc). JMRI came along and improved part of that DCC UI and DCC's UX went up a huge amount. Leaving aside European developments here DCC continued with an partly improved UI to the functionality of DCC with JMRI in that programming got a whole lot improved (thought JMRI's UI itself could be better) but the UI to driving was still the same. Then came along ProtoThrottle. ProtoThrottle put a brilliant UI to the driving functionality and DCC's UX went through the roof for those that bought it.

Coming back to RP now, RP has some brilliant functionality, but the UX is being let down by the UI, both on the handheld and RPA. If your UX is good with the UI that we have then I'm happy for you, but I think it could be greatly improved, for the betterment of the RP UX.

- Tim

nodcc4me:
I get it, Tim. It might be a good idea for you to make a short list of improvements you would like to see in RPA and send it to TR. The worst thing that could happen is that he says he can't make those changes, but I would think he would at least try to work out some of them. I know you had some issues with him in the past but hopefully, that's behind you both. Can't hurt to try.

Navigation

[0] Message Index

[*] Previous page