Next up: EclipseCon EuropeSign in
Enter your EclipseCon 2013 username.
Enter the password that accompanies your username.

Pushing Eclipse to the extreme - lessons in breaking UI rules

Session Type: 
Standard [35 minutes]
Speakers

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.

Schedule info

Time slot: 
27 March 10:30 - 11:05
Status: 
Accepted

Audience

Track: 
Tools
Experience level: 
Beginner

Re: Re: "We" is Architexa

Great. Thanks for the point. I have updated the abstract.

-Vineet

Re: "We" is Architexa

Thanks that is helpful detail. In particular the four concrete examples you list help to clarify the talk for me, and might be helpful to work into the abstract. The original abstract is very general and it is hard to get a feel for what it is about. More detail helps an attendee figure out whether they should check the talk out.

"We" is Architexa

This is work done when building the core Architexa product, but the highlight is not our product. It is more about 'rethinking the user experience when building an Eclipse plugin'.

The talk is about us getting very valid requests from users to do things differently from the traditional way that Eclipse does things. 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 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 framework that we have developed internally when trying to break such UI rules.

I can update the session description to make this clearer.

Who is "we"

Can you provide some detail on who "we" is in this proposal. What kind of applications are you building with Eclipse, is it OSS or commercial, what is the name, etc. Since you are speaking from experience it would be useful to know something about what that experience is.

Copyright © 2013 The Eclipse Foundation. All Rights Reserved.