OpenLog - Feature Request: Add a profile document
If there was a profile document in this application, there a couple of things that would make it easier/more powerful to use. This profile document would be something that would be copied into the DB's actually using OpenLog (just like the OpenLogFunctions script library). It could be called something like OpenLogProfile so it would almost be assured of being unique, but still identifiable with this application.
The first thing I see would be a place to store the default location of the openlog DB. The default behaviour in the script libvrary could be :
1) check to see if the profile document exists and use the path specified there
2) if not, use the default in the script library itself.
This would allow either multiple different OpenLog DB's to exists (for differnet groups of applications and/or users. It would also mean that if my "default" path is not in the root data directory (personally, I try not to put anything of mine there, I use folders for everything), then when a new version of OpenLog comes out, I don't have to remember to go in and modify the library before using it.
Another thing that could be in the profile document is a logging level identifier. This would work with the LogEvent routine to allow me to put these calls all over in my code, but not to have them all fire all the time. By going in to the profile document on an individual DB, I could turn logging high severity items all the time, but low severity items on only when I turn it on.