While I agree there's alot going on, I'm not sure what the problem->solution path is that you propose. As Jothay mentions, just because we change the technology, doesn't mean the UI would look much different. You mention that it's complicated,
how do you propose we make it less complicated? What do you mean exactly by complicated?

While I agree there's alot going on, I'm not sure what the problem->solution path is that you propose. As Jothay mentions, just because we change the technology, doesn't mean the UI would look much different. You mention that it's complicated,
how do you propose we make it less complicated? What do you mean exactly by complicated?

It would be less complicated if you couldascertain it's functuality at a glance, make it more intuitive.

It is true that a simple port to WPF would not change anything, but it would give you an opportunity to create intuitive UI components in minutes, that would take hours in WinForms, if possible at all.

I can click a lot and do a lot in Rawr, but I'm never sure what I see, since there is little description.

MAC OSX and Redhat use both more or or less the same backend (POSIX, UNIX ... ), the Kernel may be different, but it's function is the same, it operates in the same fashion, the backend is similar

and yet the MAC OSX UI is easy to use even for beginners while the Redhat UI is, well ... primal, unintuative and unmanagable for beginners ...

It's not about what is shown, but merely how it's shown.

It would help a lot if there was some hints and comments about what is shown when a buttons is pressed, and why I should press it.

For instance, when pressing optimize DPS, some results are logical, Rawr shows me a better weapon in my offhand, unfortunately some slots are empty, or didn't change at all although much better items are available.

Perhaps it's just me, but there are lots of functions which provide me with results I just do not understand :(

By 'back end', Jothay meant the UI framework (Winforms vs WPF). Porting to WPF won't improve usability, but it will allow for more easier improvement of the usability, which is exactly what we've been doing for Rawr3, which already is Silverlight/WPF. In
fact, your example, the optimizer results, has already been shown off in this forum, of its redesign for Rawr3.