Pushing Eclipse to the extreme - lessons in breaking UI rules
Ever felt that Eclipse has not changed much? That your plugin needs to do things differently than follow the Eclipse conventions? And have you felt the pains of breaking these Eclipse rules?
In trying to work hard on building something users want, we at Architexa have broken almost every rule of the user experience (and the underlying frameworks) that are part of Eclipse. And we have felt the pains of doing so.
In this session, we talk about us getting very valid requests from users to do things differently from the traditional way that Eclipse is used. We explore four of them in particular: to ship our plugin differently, to make saving an editor work differently, to integrate the builder differently, and to approach modeling/diagramming differently.
We will talk about the seemingly logical reasons for getting such user requests, about the large amounts of engineering challenges that fulfilling such requests can result in, and about the biggest challenge - those of the users who expect the 'traditional' way of doing things. We will also talk about the thought process that we have developed internally when trying to break such UI rules.