Hello Peter, All,
I am trying to give my opinion, from the pure perspective of a
newcome developer.
On Fri, Jan 22, 2021 at 09:40:47AM +0100, Peter Kovacs wrote:
> There is feedback from Jon Ha ojn Issues that are important from the support
> Forum perspective.
>
> Please look into the following Issues:
>
>
https://bz.apache.org/ooo/show_bug.cgi?id=126846>
> (additional Info:
>
https://forum.openoffice.org/en/forum/viewtopic.php?f=7&t=1532 )
I understand that this meta-bug is about frequent bad and frustrating
behavior of OpenOffice, but from a developer point of view, I would
need some information to replicate such a data loss, so I could
inspect the software in the moment the problem is happening. I could
not find this kind of information in the above report and in the other
reports its first comments refer to.
Is there anyone more knowledgeable about this problem, who could help
track this bit down?
>
https://bz.apache.org/ooo/show_bug.cgi?id=128356Reproduced with 4.1.9 and trunk. I can look into this one.
>
https://bz.apache.org/ooo/show_bug.cgi?id=126927I think that this issue can be generalized as a "lack of logging and
error reporting in AOO". This is one of my own pet peeves.
> plus Data loss on different occations see tutorials to:
>
>
https://forum.openoffice.org/en/forum/viewtopic.php?f=71&t=85038This is really TL;DR -- can you help me understand if it is worth
reading all? It does not seem to be an error report, but rather a
``trick'' to restore lost information from leftover temporary files.
>
https://forum.openoffice.org/en/forum/viewtopic.php?f=71&t=87180This seem to be a ``surgical'' (quoted) way to recover from certain
data corruption, again not an error report; am I right?
> Hopoe that sums it up. You can read the detailed statement with some
> critical feedback here:
>
>
https://forum.openoffice.org/en/forum/viewtopic.php?f=49&t=104234&p=505002#p505009>
> (hope the link works)
Yes, it does. But it is another very long form thread, with many links
to bug reports.
I believe you have got a better picture of the overall situation;
could you please help us split it into smaller problems?
From my humble point of view, bug 128356 shall be solved while working
on enhancing logging and error reporting at the same time; that would
be a great step towards solution of 126927.
I will start looking into the above, until someone with a better
overall picture will tell me otherwise.
Best regards,
--
Arrigo
http://rigo.altervista.org---------------------------------------------------------------------
To unsubscribe, e-mail:
[hidden email]
For additional commands, e-mail:
[hidden email]