uwestoehr wrote: ↑Sun Mar 26, 2023 3:02 pm
You do: on every warning the user gets a popup.
No, I do not, for the report view does not jump intrusively on the window.
It is a matter of perspective.
uwestoehr wrote: ↑Sun Mar 26, 2023 3:02 pm
This is not a good example. The default must cover the majority of cases, not every special one. A popup for _every_ warning is a no-go for any kind of application in an enterprise:
That you do not like the example does not make it a bad example.
We should have the warnings we should have. We should invest time to curate them, rather than procrastinate.
uwestoehr wrote: ↑Sun Mar 26, 2023 3:02 pm
often untranslated, many users are non-natives or don't know the special English words used or have not the CAD background to understand.
This stops being a problem, because now we can translate any message, no matter where in the source code, even in places where we do not want a dependency on QT. Example:
Code: Select all
Base::Console().Critical(this->getFullName(),QT_TRANSLATE_NOOP("Notifications","Parabolas were migrated. Migrated files won't open in previous versions of FreeCAD!!\n"));
An attempt is made by NotificationArea to translate any message arriving to it, except for a TranslatedNotification, which as the name says, it is already translated.
Adding the macro is also an opportunity to review whether we need the warning, or even, could be, we need yet another category of messages (which I do not rule out).
uwestoehr wrote: ↑Sun Mar 26, 2023 3:02 pm
Please consider why people founded e.g. the OpenToolchain foundation (non-profit, I am not part of it or a founder). They invest their spare time to make FC a proper tool for toolchains for small enterprises (especially in countries with a low economy where enterprises cannot afford a payed CAD). They could convince the EU to sponsor e.g. my recent FEM development, so also the EU officers share the opinion that FC should be improved to make it a proper tool. The goal here is to move FC from a "focus for hobbyists and devs to "just users". This is not my wording, but I think that describes it well.
You and me, we invest our spare time for free into making FC a proper tool. With higher or lower success, I have been doing this for a couple of years.
You are actually arguing that a software that does not warn its users on potential problems is better enterprise oriented, and that only hobbyists care about warnings. Perhaps that the UE only sponsors software that does not show warnings. I am looking where the hidden camera is.
uwestoehr wrote: ↑Sun Mar 26, 2023 3:02 pm
And here we are, I think Chris works at a university, I work in a company. I have FC users working with my models or sending me their models to print from 3 different countries, different levels of knowledge and education.
You starting assumption is that despite warnings everything works well. If that is true, we do not need those warnings.
You appear to argue that higher educated people love seeing meaningless warnings on their screens. I must not be educated enough, because I do not appreciate seeing them. Perhaps Chris can confirm he enjoys staring at them.
What would happen if there were a warning indicating that an input model may be in inches instead of millimeters (please to check)? Should we bury this warning or show it to the user? Perhaps the developers of the software used for the Hubble telescope, or in input specs to a certain mars mission also thought warnings should be buried... I think you know how those two stories ended up.
uwestoehr wrote: ↑Sun Mar 26, 2023 3:02 pm
Take for example the "objects go out of scope" warning. This assumes everybody understands English, which is not the case. Then those who understand but are non-natives don't know what this sentence could mean, in the sense of the wording. Even I had first to consult a dictionary about the word "scope" (but nevertheless did not understood it for months).
I can agree with you.
First we need to understand what it means and why it is there. What are the consequences. Then, if it stays, we should reword it. We should also use the macro to provide translations.
We need to handle these situations, rather to ignore them.
uwestoehr wrote: ↑Sun Mar 26, 2023 3:02 pm
OK, but this is exactly the point where I have a different opinion for the reasons given above and in previous posts. We tried to cleanup the warnings for years now but there are still a lot of irrelevant ones.
Which means we need to try harder. Ignoring them is not going to make them go.
uwestoehr wrote: ↑Sun Mar 26, 2023 3:02 pm
But interested users can get them either by setting a notification preferences option or by simply having the reports panel up.
What I do not know yet is if we need another category of message or not. This we have to see. I have added the translations and the critical messages on this iteration. These have a very specific scope. It may be that we need two category of warnings. For getting to know this, we need to identify which warnings we have that are not meaningful and see if they can become logs.
This is now just the start of a journey that we need to walk.
uwestoehr wrote: ↑Sun Mar 26, 2023 3:02 pm
Speaking in your words: we had another color and got complaints, now we changed it and got no complaints, so the new color fits better. And our users are not "blind" but see well, otherwise they would not have been complained.
Not really my words. You just took it out of context.