View Single Post
Posts: 345 | Thanked: 467 times | Joined on Nov 2007 @ Germany
#27
Originally Posted by ragnar View Post
I'm no developer, but I read the bug that you can place a button in the UI to switch the property of that component.
You are no developer, so i assume you are an ui designer. You basically say that you won't provide a generic solution to this, but instead want every developer to invent his own solution for this.

I haven't seen yet how text selection works in the browser, but we can safely assume it's not the same button doing this in osso-xterm. And modest is imho dealing with this by trying to avoid text selection at all and using all kinds of "hyperlinks" wherever possible. Is that true?

These are three example handling text selection completely different. All those third party guys out there will also come up with their own ideas. The same will happen with the help systems. I am really concerned that this will result in too many completely different solutions addressing the same problem. This will confuse users and this is what gui frameworks are there: To give users a consistent ui.

I'd understand (albeit not appreciate) if you'd just remove those features and say "We don't want help systems nor text selection in fremantle ... period). But you say "We still want this, but we remove support from the frameworks and want individual solutions instead. I don't understand the idea behind this. Imho you are risking pretty inconsistent user interfaces this way.
 

The Following 8 Users Say Thank You to Master of Gizmo For This Useful Post: