Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [platform-ui-dev] Recombine Problems and Tasks Views


I was referring to code which open a view programatically via ID, and also persisted workbench state and user-customized perspectives which refer to the view.

The feedback we are getting from users is that they are frustrated when they can't find compile errors, and that there are too many views in Eclipse.  Some users had customized the default perspective in 2.1 and do not see the new Problems view.  So they were frustrated when they tried to launch their java application and found out there were classpath problems in their projects.

-Randy



Tod Creasey <Tod_Creasey@xxxxxxxxxx>
Sent by: platform-ui-dev-admin@xxxxxxxxxxx

04/19/2004 02:14 PM
Please respond to platform-ui-dev

       
        To:        platform-ui-dev@xxxxxxxxxxx
        cc:        platform-ui-dev@xxxxxxxxxxx, platform-ui-dev-admin@xxxxxxxxxxx
        Subject:        Re: [platform-ui-dev] Recombine Problems and Tasks Views



Randy

Both of these views are internal so there are no compatibility issues to
worry about in upcoming releases. The feedback we are getting from many
users is that they prefer the split so we will be leaving it as is for
3.0. I personally prefer the split as I find the tasks to be unneccessary
clutter.

We may consider revisiting this in 3.1 and promoting some of the classes
to API then but not in the 3.0 timeframe.

Tod




Randy Hudson <hudsonr@xxxxxxxxxx>
Sent by: platform-ui-dev-admin@xxxxxxxxxxx
04/19/2004 01:46 PM
Please respond to
platform-ui-dev


To
platform-ui-dev@xxxxxxxxxxx
cc

Subject
[platform-ui-dev] Recombine Problems and Tasks Views







Several developers commented on their disappointment that a new View
(Tasks) has been introduced in 3.0, which increases clutter. It does not
make working with problems/tasks easier than the 2.1 solution.  I
suggested an alternative solution which is obviously much better and
scalable, but would have to wait until the next release to be implemented.
So why hasn't the current attempt been backed out of 3.0?  Once these two
views are released, it will be impossible to implement the better solution
in a future compatible release.

https://bugs.eclipse.org/bugs/show_bug.cgi?id=37974
https://bugs.eclipse.org/bugs/show_bug.cgi?id=59006

reduce clutter:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=36954

_______________________________________________
platform-ui-dev mailing list
platform-ui-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/platform-ui-dev


Back to the top