On Tue, 20 Sep 2016 17:12:28 +0100
Will Godfrey <willgodfrey(a)musically.me.uk> wrote:
On Tue, 20 Sep 2016 08:47:14 -0400
"jonetsu(a)teksavvy.com" <jonetsu(a)teksavvy.com> wrote:
> I would not impose that on SW designers and developers, for the
> simple reason that there's no solid use case supporting the
> benefits of having multiple windows per application.
I'm unaware of any solid use case not
supporting...
Or has there been some extensive study that I'm not aware of?
There are certainly studies and papers on GUI design. By both
independent researchers and by companies. There;s always research in
that field after all.
It's all this 'choice' that's the
problem isn't it/ Quite unnecessary.
Why can't 'consumers' accept there only
needs to be one music
application that has the best features of all of them (as decided by
the international features committee).
Lets save the developers even more effort. Why do we
need all these
different operating systems? Surely by now the experts have worked
out what is the best.
While we're at it, just how many different
computing devices do we
*really* need? It all just causes worry and confusion for the
'consumers'.
Need I (not a consumer) continue?
Well, it's of course up to the people creating the applications. If
one team really like the OS/2 way of doing UI and want to stick to it
today and for the next 10 years, it's up to them, really. There is no
GUI police. I think. Nor there is no guarantee in popularity.
Who knows, there might be people out there who are working in banking
institutions that have developed a nostalgia for OS/2. That would
constitute a riche market, er, a niche market.
One thing in discussing the topic is that it might start some
reflection on why certain things are done. If the result of the
reflection is that so much time is spent on doing and maintaining
something that turns out to be not so important, then that time can be
spent on doing something that is more relevant to the purpose of the
application. Otherwise, business as usual.