| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1718
|
Thu Feb 23 09:19:27 2006 |
 | Stefan Ritt | stefan.ritt@psi.ch | Request | Windows | V2.6.1-165 | Re: How to setup Change attributes in detail view/edit mode ? |
> I've changed the category to "Request" because I think it would be practical
> if I can hide the attributes which are build on values of other attributes with
> "Change".
Have you tried
Show Attributes = Admin, Hostname, IP-Adresse, Funktion, RIB Hostname, RIB IP
???
Does it bother you if then the attributes are also hidden in the detailed view? |
|
1719
|
Thu Feb 23 09:45:54 2006 |
| Holger Mundhahs | holger.mundhahs@vtg-rail.com | Request | Windows | V2.6.1-165 | Re: How to setup Change attributes in detail view/edit mode ? |
No, I havn't tried it, because it's the only way where I can see ALL attributes, and
I belief, that it works to hide the attributes on all views.
Here an Example:
I have 5 attributes where I can enter values, and 5 addtitional attributes build on them.
I can't see all of them in list view, so the only way to see/use them is the detailed view.
But because there is no value to insert/change these attributes should be hidden in NEW/EDIT mode.
As an workaround I LOCK/FIX these attributes so I can't insert values, but there are now many empty lines.
So if you can implement this functionality it would be great, but if not it's not so bad,
I can "live" with it ;)
Regards
Holger
> > I've changed the category to "Request" because I think it would be practical
> > if I can hide the attributes which are build on values of other attributes with
> > "Change".
>
> Have you tried
>
> Show Attributes = Admin, Hostname, IP-Adresse, Funktion, RIB Hostname, RIB IP
>
> ???
>
> Does it bother you if then the attributes are also hidden in the detailed view? |
|
1736
|
Wed Mar 1 10:30:51 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Windows | V2.6.1-165 | Re: How to setup Change attributes in detail view/edit mode ? |
I implemented a "Hide attributes = ..." option, with which you can do what you requested, but unfortunately I'm
sitting here in Siberia and have only limited internet access, so I can only submit the modification next weekend.
- Stefan |
|
1743
|
Thu Mar 2 23:32:25 2006 |
 | Steve Jones | steve.jones@freescale.com | Request | All | 2.6.1 | Top Groups and logbook directorys |
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! |
|
1745
|
Fri Mar 3 18:02:59 2006 |
| Steve Jones | steve.jones@freescale.com | Request | All | 2.6.1 | Allow $attributes in "Comment = " option |
| Is it possible to allow $attribute substitutions in the "Comment =" option for logbooks? |
|
1746
|
Sat Mar 4 05:17:14 2006 |
 | Glenn Horton-Smith | gahs@phys.ksu.edu | Request | All | 2.6.1-1668 | require smileys to have whitespace on either side? |
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? |
|
1747
|
Sat Mar 4 06:04:53 2006 |
| Steve Jones | steve.jones@freescale.com | Request | All | 2.6.1 | Re: Top Groups and logbook directorys |
| 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. |
|
|
1750
|
Mon Mar 6 13:40:40 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | All | 2.6.1 | Re: Allow $attributes in "Comment = " option |
| Steve Jones wrote: | | Is it possible to allow $attribute substitutions in the "Comment =" option for logbooks? |
The "Comment =" option for logbooks gives a general comment, like Discussion forum about ELOG for this forum. Since this comment is global, it does not make sense to have $attribute substitution. |