If someone implements a full GUI for my Desktop computer in Flash I'll probably quit using computers at all ;-) Well, thinking about new ways of user interaction is good - but don't forget the 'power-users'. I don't want my system to tell me what to do rather I want my system to do what I want. And a *good* application should provide intuitive access to the processes it supports (a good application should help the user to do something better and quicker than without (computer)). This means, for me is the current approach quite reasonable: there are data (information) stored in files (like sheets of papers) and there is a meta-programm (the OS) where I can execute applications to modify these data. And each application in turn does its jobs (more or less well). Hope this wasn't too offensive. Regards. Am Mittwoch, den 10.02.2010, 17:08 +0100 schrieb Diego Moya: > > > On 10 February 2010 15:38, Thorsten Wilms wrote: > On Wed, 2010-02-10 at 14:58 +0100, Diego Moya wrote: > > > - they still program using the interaction techniques of > the late 70s > > (main application event loops, event-based triggering of > subroutines, > > and throwing everything into a single application window > with separate > > function points - all (mis)organized into lots of submenus. > > > I thought event loops belong to software architecture, not > "interaction > techniques". > > I should have said "event loops controlling event-based triggering of > subroutines". Most desktop applications are defined by an event-based > "collection of reactive commands activated throug menu entries, > toolbars or keyboard shortcuts, with a collection of static widgets > showing feedback", which is definitively an interaction technique. > > Software architecture is definitely related to the interaction > techniques supported - anything too complex will not get implemented > using the wrong architecture. Complex interactions are best served by > hierarchical state machines which allow creating and destroying > interface elements on the fly. But most industrial-grade GUI tookits > are based in the Widgets+events architecture, and GUI builders are > little more than widget composers that help with the composition of > static interfaces. > > > Anyway, what would be more modern approaches? > > See Post-WIMP interfaces at Wikipedia > (http://en.wikipedia.org/wiki/Post-WIMP), plus "Non Command User > Interfaces" and "The humane > interface" (http://en.wikipedia.org/wiki/The_Humane_Environment) for a > good entry point. Physical interaction, zooming interfaces, continuous > input and feedback, gestures recognition. > > Adobe-Macromedia Flash is a good and successful industrial example. > Flash contains an advanced architecture for interaction, the Timeline. > This makes coordinating animation through time much easier than with a > reactive event loop plus timers. Modern RAD web applications in Flash > are ditching the timeline and using the classic widget approach, > though. They call this progress. > > > > > > > All private companies have that underlying goal. That is not > > incompatible with providing what the intended users need. I > think > > Apple got it right in focusing on users with little > computing > > experience/needs. > > > > The suggested solution (self-contained apps) is just one > viable format > > for this, currently popular because of the success of the > iPhone. As > > you say, this is not good for all users (only the majority > of them) - > > so different solutions will evolve for the kind of users > left behind. > > > I suspect that emphasizing applications has quite a lot to do > with > pushing sell-able entities. > > > Maybe, maybe not. The Linux desktop emphasizes applications, even > though they're Free and thus not sell-able. Maybe they are a > relatively good and stable structure for grouping computing functions. > This doesn't mean there can't be better ways. > > > _______________________________________________ > Usability mailing list > Usability gnome org > http://mail.gnome.org/mailman/listinfo/usability
Attachment:
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil