the question might be: Is it really neccessary to know Java concepts and type structures to change just some minor things?
It is somehow a question of leveling. How deep do I need to dig? In case I want to improve logging for bindings, debugg sessions and so on I obviously need to know everything, indeed. But I bet 80% of OH users just need to be able to change some parameters from time to time (usually called “increase loglevel”).
You guys know what a GUI is for? To make the use of the software easier for everybody. Someone who knows a piece of software very well does not need a nice GUI because he understands the concept of the software. But what about the majority of the others?
So to all who say: hey, read the docs, get known to the concepts, get used to Java: Please ask yourself the question for which target audience is the software designed for? Java developer? System administrators? Code guys? Should we set a minimum level of knowledge (i.e. aware of object oriented programming) before giving the allowance to use OH?
Try to see our point: I was looking to MODIFY (I did not want to re-code it all!) the log settings. As I am in Linux since 1990’s my first attempt was “
logrotate” and “
rsyslog”. Well, both has been a dead end (unfortunately this is very often the case for Java implementing all of it’s own instead using what is already there…). So I asked for help (and no, this has not been documented anywhere) and was pointed to some futher docs which pointed to log4j. Really? This did not help at all! (Sorry @stefan.oh).
@savoiringfaire posted some code sniplets- but where to put them?
I was happy once I found the file (not in this thread!) where to configure it (I expected it to be somewhere under
/etc/, but no!
/var/lib… was it). Oh, and the name of the file was “really” self-explaining. I should have guessed
org.ops4j.pax.logging.cfg. Makes sens for all people…
Ok, usually all Linux configuration files are well documented an more or less at a minimum level to have the possibility to change items quickly. The comments to the related log entries in the files with 151 lines (!) make such self-explaining statements like:
log4j2.appender.out.policies.type = Policies
log4j2 - is the library used here (why should I know???)
appender - seems to be the word for logger? What else might this mean?
out - writing data out. Ok. question: is there an in for appender?
policies - So I am dealing with policies which are usually somehow globally…
type - Why do I need a policy type?
Policies - So I have a ploicy of type Policies… well, absolutely clear, indeed.
And I have some double expressions “
size.size” yeah. Of course…
Guys, either hide all these items from the users by installing some easy filter (I am not talking about a GUI, a simple text configuration file could be parsed to write all these Java files…) or at least do not tell the guys seeking for help to “read the docs” and get used to Java concepts.
Anyway; I guess my question is answered so I guess we can close it here…