What was the rationale for creating a new GUI?

[GoogleCodeExporter]

What would you like to see documented?
Why does O2 have so many modules and what are the events that trigger the 
creation of new 
GUIs

This is a post from Rohit to the O2 Platform mailing list:

"...  What was the rationale for creating a new GUI? In particular, why
didn’t you just piggyback off an existing, pluggable IDE like Eclipse?
I'd guess the answer is because O2 is developed (I’m assuming) in .Net
and probably through Visual Studio in order to facilitate GUI widget
development. You’ve created a new look and feel which then requires
the end user to understand the new look and feel in order to make
sense of the application. Although I can appreciate the choice to go
use .Net instead of Java, I wonder if copying some of the GUI
conventions of Eclipse might be useful (more on this later). Note that
I’m no usability expert, but I’d like to share my thoughts anyway. I
would seriously suggest freezing new feature development for a while
and focus on improving usability; once the application is easier to
use, hopefully the user base will grow and so will the pool of
developers willing to pitch in. In general try to minimize the amount
of information in each dialogue box, and provide expandable, grouped
advanced options...."

Original issue reported on code.google.com by dinis.cr...@gmail.com on 25 Nov 2009 at 11:38

[GoogleCodeExporter]

Original comment by dinis.cr...@gmail.com on 25 Nov 2009 at 11:41

• Changed title: \ What was the rationale for creating a new GUI?**

[GoogleCodeExporter]

Relevant to previous version of O2

Original comment by dinis.cr...@gmail.com on 5 Jul 2010 at 3:33

• Changed state: WontFix

[GoogleCodeExporter]

Relevant to previous version of O2

Original comment by dinis.cr...@gmail.com on 5 Jul 2010 at 3:33