> currently writing lots of entries to the error log can cause UI freezes.
I think I want to take a look at that. Flushing the SWT event queue during
writing to our error log has helped our application get rid of those
freezes.
Do you happen to know the bug number?
On Thu, Sep 12, 2019 at 5:44
I'd be unhappy to see yet more deprecated "APIs", i.e., would
org.eclipse.core.runtime.ILog be deprecated? Consumers might start to
feel as if no API is really API anymore. Everything is just potentially
in a transient state on the path to ultimate perfection, along with the
ever-present
+1
Dirk Fauth schrieb am Do., 12. Sep. 2019, 18:07:
> Actually I would like to get rid of the multiple facades (FrameworkLog,
> RuntimeLog, etc. are all forwarding to the OSGi LogService. And with OSGi
> R7 it has improved and probably makes all the facades unnecessary. Why
> reinventing the
On Thu, Sep 12, 2019 at 5:22 PM Lars Vogel wrote:
> Having one logging solution would be great, as you pointed out it must
> be simple for the IDE case and the e4 RCP case.
>
As mentioned in the previous thread, there are already N ways of logging,
so adding one more way won't make N+1 == 1.
