| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1331
|
Tue Jul 26 17:28:31 2005 |
 | Juliana Peng | jpeng@yorku.ca | Request | Linux | V2.6.0 | Re: hide attributes when view the logbook |
| Stefan Ritt wrote: |
| Juliana Peng wrote: | | Thanks. But what I want is to hide the unwanted attributes at summary view, not just hide them when I click on entry. |
No you can't do that.
Assume that you have different types of entries, ones where your unwanted attributes are missing and ones where they are present. If you would hide them, they would be missing even for the entries where you want them. Or you would change the table layout for every line, meaning that attributes which are common in all entries do not line up nicely below each other.
An other approach would be to make elog hide those columns which do not contain any value in the whole page, but that is not (yet) implemented. |
I may have all the attributes in logbook to keep a full record of all the machine. But for daily use, some of the attibutes we are not using so often. Too many attributes will make the window so big that can not be hold in one screen which is the reason why I want to hide some of them. Of course the hidden attributes have data, but those data are rarely used so we'd rather hide them.
Since "show attributes" prevent from inputing attributes, may not be suitable in this case. We appreciate if you can impletement a new feature like "view attibutes" which do not affect adding new entry, just hide attributes at summary view. |
|
1337
|
Tue Jul 26 20:35:45 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Linux | V2.6.0 | Re: hide attributes when view the logbook |
| Juliana Peng wrote: | I may have all the attributes in logbook to keep a full record of all the machine. But for daily use, some of the attibutes we are not using so often. Too many attributes will make the window so big that can not be hold in one screen which is the reason why I want to hide some of them. Of course the hidden attributes have data, but those data are rarely used so we'd rather hide them.
Since "show attributes" prevent from inputing attributes, may not be suitable in this case. We appreciate if you can impletement a new feature like "view attibutes" which do not affect adding new entry, just hide attributes at summary view. |
Use "list display = <attribute list>" to specify which attributes to show in the listing page. RTFM. |
|
1342
|
Tue Jul 26 22:05:24 2005 |
| Juliana Peng | jpeng@yorku.ca | Request | Linux | V2.6.0 | Re: hide attributes when view the logbook |
| Stefan Ritt wrote: |
Use "list display = <attribute list>" to specify which attributes to show in the listing page. RTFM. |
Thanks. "List display" is what we need.
But is there a way to control to hide or view the attributes? so that we don't need to change the elog.conf file each time.
For example, add a menu "expend" in "Find menu commands", we can click to view all the attributes or just view the attributes defined in "List Display"
Or use "{1} List Display = ....", we can view all the attributes at list page, but if selecting SunOS, only show attributes in List Display |
|
1344
|
Wed Jul 27 09:07:17 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Linux | V2.6.0 | Re: hide attributes when view the logbook |
| Juliana Peng wrote: | But is there a way to control to hide or view the attributes? so that we don't need to change the elog.conf file each time.
For example, add a menu "expend" in "Find menu commands", we can click to view all the attributes or just view the attributes defined in "List Display"
Or use "{1} List Display = ....", we can view all the attributes at list page, but if selecting SunOS, only show attributes in List Display |
In that case I would suggest two separate logbooks, for for SunOS and one for others. This way you can manage two separate sets of attributes. |
|
1346
|
Wed Jul 27 15:49:16 2005 |
| Juliana Peng | jpeng@yorku.ca | Request | Linux | V2.6.0 | Re: hide attributes when view the logbook |
| Stefan Ritt wrote: |
In that case I would suggest two separate logbooks, for for SunOS and one for others. This way you can manage two separate sets of attributes. |
We don't want separate logbooks, sorry for the misleading. I was trying to put two request together.
1. We have several user using the logbook. Is there a way each one has his own "List Display". In our case the user also is an attribute(SysAdmin) in logbook:
Attributes = Name, SysAdmin, Manufacturer, Model, Serial Number, Description, ENV, Main Function, Location, Memory, CPU Speed, Num CPU, Owner, Contact Name, Contact Phone, Contact Email, Bought From, Bought Date, Maintenance, Network Drop,Console Drop
Options SysAdmin = user1{1}, user2{2}, user3{3}
so one way we can think of is using "{1} List Display = ...."
"{2} List Display = ...."
"{3} List Display = ...."
because most of the time the user is interested in his own machine. Maybe you have better suggestion.
2. We need to change elog.conf file to use or not use "List Display". Is there a way to control it through web? If this is not applicable. It's fine, we won't change the view frequently. |
|
1347
|
Wed Jul 27 15:56:53 2005 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Linux | V2.6.0 | Re: hide attributes when view the logbook |
| Juliana Peng wrote: | | We don't want separate logbooks, sorry for the misleading. I was trying to put two request together. |
I understood you correctly. What I was trying to say is that what you currently request possible with the current version and will not be implemented soon. But you can partly obtain what you want by having two logbooks. Make one logbook which has fewer attributes, and which will receive all SunOS entries. Make another one with all the attributes. Although this will become separate logooks, you can "think" of them as one logbook with two different sections. There is even the trick of forcing the data directory to be the same (via the "data dir") option, so both logbooks will "look" at the same database. Make one logbook the "master" having all the attributes. That's where you enter your information. Them make one or more logbooks looking at the same data, but make them read-only. Each logbook can have a separate set of attributes, access rights etc, but all of them show the same data.
I know this is not the perfect solution, but at least something which can be done already now. |
|
1348
|
Wed Jul 27 16:31:33 2005 |
 | Juliana Peng | jpeng@yorku.ca | Request | Linux | V2.6.0 | Re: hide attributes when view the logbook |
| Stefan Ritt wrote: |
I understood you correctly. What I was trying to say is that what you currently request possible with the current version and will not be implemented soon. But you can partly obtain what you want by having two logbooks. Make one logbook which has fewer attributes, and which will receive all SunOS entries. Make another one with all the attributes. Although this will become separate logooks, you can "think" of them as one logbook with two different sections. There is even the trick of forcing the data directory to be the same (via the "data dir") option, so both logbooks will "look" at the same database. Make one logbook the "master" having all the attributes. That's where you enter your information. Them make one or more logbooks looking at the same data, but make them read-only. Each logbook can have a separate set of attributes, access rights etc, but all of them show the same data.
I know this is not the perfect solution, but at least something which can be done already now. |
Thank you so much. We'll try it. Waiting for your next version. |
|
1571
|
Tue Jan 3 17:20:16 2006 |
 | Mike | mlmoore@pella.com | Bug report | | V2.6.0 | elogd 2.6.0 crash on password Forgot? | I have been having a repeatable crash on V2.6.0 everytime someone tries to recover a password using the option from the login screen. See attachment for a jpg of the message.
This is occuring on windows 2003. But I have also tested it on windows XP and it occurs there as well. In addition on XP I did a generic installtion and added the password option to the DEMO application and it fails there as well.
Mike |
|