Twitter github

Platform UI has been busy…

There is a proposal / some prototyping going on for something called Platform UI Error Handling. The concept here is to be able to provide a way for the end-users to a) see what the error is b) understand what it means within their domain knowledge and c) how they can act on the error (if possible). I think this is a pretty nifty concept… An example would be say an RCP product vendor now has the ability to notify the user of an error in a polite way and possibly have a webpage launch to their support webpage with some details automatically filled in regarding the error.

  • Eugene

    They are making BIG mistake by doing this stuff in a dialog! It is against Eclipse ideology to not bring up modal dialogs.

  • Eugene

    They are making BIG mistake by doing this stuff in a dialog! It is against Eclipse ideology to not bring up modal dialogs.

  • papapapashan

    can you leave your email? I want to ask you a question.

    Thanks a lot!!!

  • papapapashan

    can you leave your email? I want to ask you a question.Thanks a lot!!!

  • Boris

    Eugene – we are still working on that and are aware of the problems caused by spinning the event loop in random places.

  • Boris

    Eugene – we are still working on that and are aware of the problems caused by spinning the event loop in random places.

  • Marcelo Paternostro

    wow… this is very interesting. I would love to know more about how complete this is and also share some ideas. Quickly glancing through the wiki, I could see that there are similar concepts implemented in EMF.

    In 2005, we’ve committed this class ConverterUtil. It pretty much defines a way to “encode” in an IStatus how the UI should handle an exception. Also, in January this year, we’ve committed the ProblemEditorPart which is an Editor page that “magically” appears when something is wrong with the model. Depending on the problem, this page allows the user to create a marker or open the text editor.

  • Marcelo Paternostro

    wow… this is very interesting. I would love to know more about how complete this is and also share some ideas. Quickly glancing through the wiki, I could see that there are similar concepts implemented in EMF.In 2005, we’ve committed this class ConverterUtil. It pretty much defines a way to “encode” in an IStatus how the UI should handle an exception. Also, in January this year, we’ve committed the ProblemEditorPart which is an Editor page that “magically” appears when something is wrong with the model. Depending on the problem, this page allows the user to create a marker or open the text editor.