Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [4diac-dev] GSoC milestone
Hi!

Thank you for your feedback. The first prototype of the improved UI can be found here. Currently, the error messages of the constraints are stored in the constraints.properties file and they are displayed in the Description column. 

image.png

Adding a longer explanation to the violated constraints is a good idea. I think it would nice to extend the Problems View with an additional "Hint" column. At first sight, it looks like we can do this by using the org.eclipse.ui.ide.markerSupport extension point to define a new markerField, which will correspond to a new Hint column in the Problems View. 

BR,
Sándor

Jörg Walter <joerg.walter@xxxxxxxx> ezt írta (időpont: 2020. aug. 5., Sze, 12:57):
On 29.07.20 21:13, Sándor Bácsi wrote:
> Hi!
>
> Here is a new update on my GSoC project. We have collected a set of
> constraints, which can be found here
> <https://docs.google.com/spreadsheets/d/1JFpQhYCTBrei3QrgTYtS0RLJ0daLuESjP0bE87VRZas/edit?usp=sharing>.
> Feedback and support are warmly welcome on the list of constraints, feel
> free to add your comments to the constraints. I have finished the
> implementation of constraints on the ECC level
> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=564852> and there are
> several constraints on the Application level
> <https://bugs.eclipse.org/bugs/show_bug.cgi?id=565065> as well.
> Currently, there is a simple dialog window for displaying the results of
> the validation. The next step is to improve the UI, by displaying the
> Error, Warning and Info elements in the Problems View. Initial prototype:

Wow, this looks great! I'm happy that this works out.

I have one suggestion to make, in order to skip the problems that many
C++ compilers had until recently: There will always be users that read
these error messages for the first time (e.g. GSOC students using the
tool for the first time ^^). They won't necessarily understand what that
violated constraint means.

Can you add an annotation which allows constraint authors to add a
longer explanation, i.e. don't just output "don't do this", but also
"this is a typical example of how it's done right". And of course, make
this easily discoverable, maybe just append it to the error message.

Thanks for the great work.

Regards,
--
Dipl.-Inform. Jörg Walter
Senior Researcher
R&D Group Distributed Computation and Communication

OFFIS e.V. - Institut für Informatik
FuE Bereich Produktion | R&D Division Manufacturing
Escherweg 2, 26121 Oldenburg - Germany
Phone/Fax.: +49 441 9722-729 / -282
E-Mail: joerg.walter@xxxxxxxx
URL: http://www.offis.de

Registergericht: Amtsgericht Oldenburg VR 1956
Vorstand: Prof. Dr. Sebastian Lehnhoff (Vorsitzender),
    Prof. Dr. techn. Susanne Boll-Westermann, Prof. Dr.-Ing. Axel Hahn,
    Prof. Dr.-Ing. Andreas Hein, Prof. Dr.-Ing. Wolfgang H. Nebel
_______________________________________________
4diac-dev mailing list
4diac-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/4diac-dev

Back to the top