Thanks for the feedback Michael.
Landon
2010/9/7 Michaël Michaud michael.mich...@free.fr:
Hi,
Of course, I agree with Martin's solution to report bad features in a
dedicated layer.
Ede also reminded us about the HTMLFrame, which may not be well suited
to report geometry problems, but
Stefan,
Do you have a problem with letting Kevin apply his patches to the
ImageFactory classes?
Would it be possible to set-up a simple log-to-file mechanism that
could be accessed from the plug-in context? I have used Log4j before,
and it seemed a little complicated. I wonder if just having the
On 9/7/2010 7:38 AM, Sunburned Surveyor wrote:
Stefan,
... I have used Log4j before,
and it seemed a little complicated.
I find the log4j.properties variant complicated as well. But the
log4j.xml [1] configuration variant I find fairly straight forward [2].
I can include/exclude log
I'll have to take a look at log4J again. Did you imagine exposing a
method to access the logging functionality through the plug-in
context, or through some other mechanism?
The Sunburned Surveyor
On Tue, Sep 7, 2010 at 8:29 AM, Kevin Neufeld kneuf...@refractions.net wrote:
On 9/7/2010 7:38 AM,
Hi,
Of course, I agree with Martin's solution to report bad features in a
dedicated layer.
Ede also reminded us about the HTMLFrame, which may not be well suited
to report geometry problems, but which is the way to go for other
information messages directed to the user (ex. statistics,
I agree that calls to System.out are not the best thing. Did we decide
that log4J is the best way to handle error messages?
Here are a couple of questions:
(1) Are the calls to System.out in plug-ins or the core?
(2) Does the information sent to System.out need to be reported to the
user, and if
Hei,
Here are a couple of questions:
(1) Are the calls to System.out in plug-ins or the core?
was the core
(2) Does the information sent to System.out need to be reported to the
user, and if not, what is the purpose of the logging?
was needed because I wanted to see if the image drivers
My I suggest that System.out lines be replaced with appropriate log4j
statements in OpenJUMP?
One of the purposes/advantages of using log4j is that I can filter
output generated by other people's plugins that don't pertain to my own
development.
Attached is a couple of example patches that
