I'm (ab)using elog as a database and would like to use conditional attributes, like:
Attributes = PC Name, Operating System, Version, Distribution
Options Operating System = Linux{1}, Windows{2}
{1} Show Attributes Edit = Operating System, Distribution, PC Name
{2} Show Attributes Edit = Operating System, PC Name, Version
Problem is that there are several conditions and the list of attributes is rather long. Also, since it's a
rather dynamic environment I have to make new attributes all the time, and adding them to all "show attributes"
lists is not only tedious, but bound to cause errors as well.
So...
I was thinking, would it be an idea to make the list of attributes to be shown or hidden on a per attribute base.
Like:
Attributes = PC Name, Operating System, Version, Distribution
# hide specific attributes
Hide attributes = Distribution, PC Name
# or configure which fields should be shown allways
Show Attributes = Operating System, Version
# add attributes based on OS
Options Operating System = Linux{1}, Windows{2}
{1} Show Attribute Edit = Distribution
{2} Show Attribute Edit = PC Name
(just thinking out loud here). |
Greetings,
I was wondering, is it possible to wrap lines in the config file ?
I have to add a dropdown lost which is kinda long and typing everything on one line will make ik kinda unreadable.
Somehow wrapping the line so each entry will get on a separate line would make it much better readable. (which
makes less errors).
W.
|
I noticed a long url got hard-wrapped when I entered a long one, I patched
the source code. I don't know if this was done intentionally, otherwise you
might want to change this also.
diff elogd.c elogd.c.org
4468c4468
< rsprintf("<textarea rows=20 cols=%d wrap=soft name=Text>", width);
---
> rsprintf("<textarea rows=20 cols=%d wrap=hard name=Text>", width);
BTW, why is the editor window 20 rows by 76 columns ?
(20 is fixed in the source code, but 76 is the width-variable that is set
hard to:
/* set textarea width */
width = 76;
Now I don't like both parameters. 20 is too long for my display (1024x768)
and 76 is too short. Something dynamically would be cool, but a parameter
somewhere in a config file would also be acceptable. (just a thought, makes
it easier to upgrade) |