eLog Version number as eLog attribute?, posted by Steve Jones on Fri Feb 24 16:40:38 2006
|
When a footer is used (via Bottom text = <filename>) eLog no longer displays the eLog version number at the bottom. Is it possible to somehow expose the version/revision as an eLog attribute or have the version still display even when a replacement footer is specified?
Thanks! |
Re: eLog Version number as eLog attribute?, posted by Stefan Ritt on Wed Mar 1 10:31:33 2006
|
| Steve Jones wrote: | When a footer is used (via Bottom text = <filename>) eLog no longer displays the eLog version number at the bottom. Is it possible to somehow expose the version/revision as an eLog attribute or have the version still display even when a replacement footer is specified?
Thanks! |
I added that feature, but will not be able to commit it before the next weekend. |
Re: eLog Version number as eLog attribute?, posted by Steve Jones on Wed Mar 1 20:22:28 2006
|
| Stefan Ritt wrote: |
| Steve Jones wrote: | When a footer is used (via Bottom text = <filename>) eLog no longer displays the eLog version number at the bottom. Is it possible to somehow expose the version/revision as an eLog attribute or have the version still display even when a replacement footer is specified?
Thanks! |
I added that feature, but will not be able to commit it before the next weekend. |
| Quote: | | Not a problem! Thanks |
|
|
Top Groups and logbook directorys, posted by Steve Jones on Thu Mar 2 23:32:25 2006
|
I am re-working our elog setup and am seriously looking at using the "Top Group" feature. What I like best is the ability to create [global] configurations for a group (or type) of logbook when I host multiple types on the same server. I also like being able to specify a different password file, etc.
A limitation that I run into is I would really like the actual directory names used for storing the logbooks for the different types to be identical - which isn't possible when all logbooks (regardless of context) exist at the same directory level. For example, I might have:
3 physical locations: ABC, DEF, GHI
For each location I want to maintain two *groups* of logbooks - CircuitTests and BoardTests. What I would like to end up with is:
- CircuitTests
----ABC
----DEF
----GHI
- BoardTests
----ABC
----DEF
----GHI
Under current elog this is not possble as far as I know. Since each logbook is a physical directory, each logbook requires a unique name. The concept of a named [global] area fills the bill for all things but it would be nifty if one could do:
[global circuittests]
Logbook dir = circuittestlogbooks
[global boardtests]
Logbook dir = boardtestlogbooks
I suppose the poorman's way of doing this is for each logbook to do the following:
[ABC]
Subdir = boardtestlogbooks/ABC
[DEF]
Subdir = boardtestlogbooks/DEF
[GHI]
Subdir = boardtestlogbooks/GHI
or something like that, but I was hopic for something a little more integrated - like creating the hierarchical stuff via the GUI. Anyway, this probably sounds like a major overhaul, which definitely wouldn't be worth it unless I have completely missed something glaringly obvious.
Thanks! |
|
Allow $attributes in "Comment = " option, posted by Steve Jones on Fri Mar 3 18:02:59 2006
|
| Is it possible to allow $attribute substitutions in the "Comment =" option for logbooks? |
require smileys to have whitespace on either side?, posted by Glenn Horton-Smith on Sat Mar 4 05:17:14 2006
|
It would be nice if elog would only interpret something as a smiley if it is surrounded by whitespace. It can be particularly annoying that an 8 followed by a right paren becomes a "cool" smiley -- e.g., a parenthetical reference to event eighteen (18) becomes mangled... [That was "18" inside the parens.]
Is there already a way to solve this issue (other than always previewing your entries and adding spaces before parans)? Is the feature hard to implement? |
|
Re: Top Groups and logbook directorys, posted by Steve Jones on Sat Mar 4 06:04:53 2006
|
| Steve Jones wrote: | I am re-working our elog setup and am seriously looking at using the "Top Group" feature. What I like best is the ability to create [global] configurations for a group (or type) of logbook when I host multiple types on the same server. I also like being able to specify a different password file, etc.
A limitation that I run into is I would really like the actual directory names used for storing the logbooks for the different types to be identical - which isn't possible when all logbooks (regardless of context) exist at the same directory level. For example, I might have:
3 physical locations: ABC, DEF, GHI
For each location I want to maintain two *groups* of logbooks - CircuitTests and BoardTests. What I would like to end up with is:
- CircuitTests
----ABC
----DEF
----GHI
- BoardTests
----ABC
----DEF
----GHI
Under current elog this is not possble as far as I know. Since each logbook is a physical directory, each logbook requires a unique name. The concept of a named [global] area fills the bill for all things but it would be nifty if one could do:
[global circuittests]
Logbook dir = circuittestlogbooks
[global boardtests]
Logbook dir = boardtestlogbooks
I suppose the poorman's way of doing this is for each logbook to do the following:
[ABC]
Subdir = boardtestlogbooks/ABC
[DEF]
Subdir = boardtestlogbooks/DEF
[GHI]
Subdir = boardtestlogbooks/GHI
or something like that, but I was hopic for something a little more integrated - like creating the hierarchical stuff via the GUI. Anyway, this probably sounds like a major overhaul, which definitely wouldn't be worth it unless I have completely missed something glaringly obvious.
Thanks! |
| Steve Jones wrote: | | Perhaps it is best to ignore this -- I went for a workaround that I like. I am running into a few quirky things with Top Group but it is likely due to the fact that I have never used it. |
|
Crafted URL causes elog to coredump, posted by Steve Jones on Sat Mar 4 06:08:29 2006
|
While playing with TOP GROUP I managed to get elog 2.6.1 1660 on Solaris 9 to coredump. Since I didn't really understand TOP GROUP I tried a URL where I had http://elog.server.com/topgroupname/logbookname. Putting that logbookname at the end caused elog to dump.
Can this be reproduced by others? |