Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 652 of 808  Not logged in ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown
  66013   Thu Oct 23 11:45:51 2008 Disagree T. Ribbrockemgaron+elog@ribbrock.orgQuestionAll2.7.5-2130Re: (How) can I hide columns in List view?

T. Ribbrock wrote:
[...]

One thing I don't understand for example is how does elog decide in List view which entry sets the condition? If all entries are set to the same value (in this example e.g. "Type1")? The first entry? Or am I missing something altogether?

[...]

 By now, I'm one step further. List conditions = 1 does have some effect in some cases - the following works:

Options Type = Type1{10}, Type2{11}
Options StatusA = Status-A-red, Status-A-orange, Status-A
{10}Style StatusA Status-A-red = background-color:red
{11}Style StatusA Status-A-red = background-color:green

This seems to get evaluated "top-down", i.e. the value of "Type" in the first row in the list sets the handling of StatusA and the background-color, the second row for the third and so on. Unfortunately, this really only depends on the order of the rows on the screen - if I sort the list differently, I get a different result.

I am also quite certain that List conditions = 1 has no effect whatsover on List display - which is what I was hoping for.

Hence, I'd like to repeat my question: Is there any way to hide columns in List view (short of editing the conf file...) - and if so, how?

Regards,

Thomas

  66024   Thu Oct 30 04:17:09 2008 Reply Stefan Rittstefan.ritt@psi.chQuestionAll2.7.5-2130Re: (How) can I hide columns in List view?

 

T. Ribbrock wrote:

Originally, all information about our machines was stored in a spreadsheet with one sheet for the hardware of the machines and one for the software. By now, I've sucessfully moved the software part to an elog logbook and am now looking at transferring the hardware part as well.

As both lists are machine-name based, one of the options would be to merge both lists, as this would place all machine-related info into one logbook. The downside of this is that I get so many columns in list view that the result is quite unwieldy. Hence, I would like to hide some columns - ideally creating a "hardware view" and a "software view".

From the documentation, the only option I could find that seemed suitable was "List conditions". Unfortunately, I do not quite understand from the manual how this is supposed to work, so I'm quite possibly doing something wrong. I've tried this:

; General settings
List conditions = 1

; Attributes
Attributes = Type, Created, StatusA, StatusB, Archived

; Options & Tooltips
Options Type = Type1{10}, Type2{11}

; Conditionals
{10}List display = Edit, Type, Created, Status
{11}List display = Edit, Type, Created, StatusA, StatusB, Archived

but no matter how I set "Type", it does not seem to have any effect on the List display. One thing I don't understand for example is how does elog decide in List view which entry sets the condition? If all entries are set to the same value (in this example e.g. "Type1")? The first entry? Or am I missing something altogether?

Also, if there are alternative ways how I could accomplish my goal, I'd also be most grateful for suggestions.

Thanks in advance,

Thomas

 

 Indeed you got something wrong. The conditional attributes are meant for the input form, so you can turn some attributes on and off or choose different options for an attribute depending on the value of another attribute.

The only way I see how you can achieve what you want is to define two separate logbooks, but serve them from the same directory (via the "Data dir" option). Both logbooks should share the same attribute definition, but use different "List display" options.

  66028   Thu Oct 30 09:44:25 2008 Idea T. Ribbrockemgaron+elog@ribbrock.orgQuestionAll2.7.5-2130Re: (How) can I hide columns in List view?

Thanks for the response! BTW: I did get a notification - but thanks for the "personal heads-up"!

Stefan Ritt wrote:

 Indeed you got something wrong. The conditional attributes are meant for the input form, so you can turn some attributes on and off or choose different options for an attribute depending on the value of another attribute.

[...]

 I see. In that case, could you maybe please give a quick explanation what "List conditions" is supposed to do? In conjunction with your statement above I'm now thoroughly confused as to what it should/could be used for...

Stefan Ritt wrote:

[...]

The only way I see how you can achieve what you want is to define two separate logbooks, but serve them from the same directory (via the "Data dir" option). Both logbooks should share the same attribute definition, but use different "List display" options.

 Ah, that's an idea - I'll look into that. Thanks a mil for the suggestion!

Regards,

Thomas

  66029   Thu Oct 30 11:05:11 2008 Agree T. Ribbrockemgaron+elog@ribbrock.orgQuestionAll2.7.5-2130Re: (How) can I hide columns in List view?

Stefan Ritt wrote:

[...]

The only way I see how you can achieve what you want is to define two separate logbooks, but serve them from the same directory (via the "Data dir" option). Both logbooks should share the same attribute definition, but use different "List display" options.

 I take it you mean the "Subdir" option (the manual mentions "Data dir" as obsolete)? I tried it with that and it works like a charm - gives me now two logbooks, i.e. two tabs with the same data and two different views - which is precisely what we need. Thanks!

Regards,

Thomas

  194   Sat Jan 11 19:26:24 2003 Question Etienne Van Caillieetienne.vancaillie@mba.beBug report  Re: 'group' option in conflict with 'guest logic' and 'LogBook Tabs' option
> From Version 2.2.5 on, the configuration file entries
> 
> User = ...
> Group = ...
> 
> have been changed to
> 
> Usr = ...
> Grp = ...
> 
> in order not to conflict with the new "Group = ..." option which is used by 
> hierarchical logbooks.

not really a bug
works very fine just remarks : with this example
Group Phone & Adress = Whois, Qui_est_Qui
Group Extranet = Aide, Promos_Clients, Qui_est_Qui, Joke

[whois] is a intranet section for us : [qui_est_qui] is public
I add   'copy to = Qui_est_qui' 
so extranet or public can acces to limited information
just remove the attributes and guest user can see only limited info
see example below

small problem : 
****************
Logbook Tabs = 0  in the guest logbook will close the group header
may be create a parameter to solve ?
GroupGuest Extranet = ....

;--------------------  intranet info----------------
[Whois]
Comment = MBA & his Partner all your personal info must be here
Subdir = whoiswho
Menu commands = Back, New, Edit, Find, Help, Copy to
Attributes = Partner, AsTo, YourName, SurName, email1, email2, hotmail,Yahoo, 
GSMmail, Nickname, phone, fax, portable , home , adress, Remarks, birthday, 
QuadroUser, Function, Division
MOptions Partner = Mba, MbaCZ, BusinessCom, Edipax, Ibi, Other
Required Attributes = Parner, CodeName, YourName, email1, phone, birthday
Preset GSMmail = ???@proximus.be
Preset portable = 00 32
Copy to = Qui_est_Qui

Quick filter = Partner, Date, AsTo

;------------------------------------
[Qui_est_Qui]
Comment = MBA et ses collaborateurs à votre service 
Subdir = logbooks/whoiswho/public
Attributes = Partner, YourName, SurName, phone, fax ,portable ,email1 , 
hotmail, GSMmail, Nickname,  Remarks,Function, Division
MOptions Partner = Mba
Date format = %d/%m/%y
Quick filter = Date

;--------------------pas d'acces au autre menu no acces to main menu
Logbook Tabs = 0
Guest menu commands = Find
Guest find menu commands = Find
;-------------- rectriction on edit if not put  1  
Restrict edit = 1
Display mode = full
Help URL = http://www.mba.be







 
  196   Mon Jan 13 11:43:37 2003 Reply Stefan Rittstefan.ritt@psi.chBug report  Re: 'group' option in conflict with 'guest logic' and 'LogBook Tabs' option
> small problem : 
> ****************
> Logbook Tabs = 0  in the guest logbook will close the group header
> may be create a parameter to solve ?
> GroupGuest Extranet = ....

What I would recommend in that case is to run two copies of elogd in 
parallel, one for the public and one for the private section. They can even 
run on differnt ports so the firewall can block the private section. If the 
private logbooks are not defined in the public elogd, they don't show up in 
the logbook tabs, so only the publick logbook tabs are seen. Please note 
that two elogd daemons should not have concurrent write access to the same 
logbook, since there is not locking and the logbook could get messed up that 
way. So only one elogd should have write access to any logbook.

- Stefan
  294   Tue Apr 22 17:16:31 2003 Reply Stefan Rittstefan.ritt@psi.chBug report  Re: 'Reply' removes attachments from the original message
> It seems when I use "reply" with an attachments, the original attachments of
> the message are removed.
> 
> I use elog-2.3.5
> 
> Alexander.

Please see elog:280 . I will releae 2.3.6 with this bugfix somewhen during 
this week.

- Stefan
  296   Tue Apr 22 17:20:19 2003 Reply Alexander ZVYAGINAlexander.Zviagine@cern.chBug report  Re: 'Reply' removes attachments from the original message
> > It seems when I use "reply" with an attachments, the original attachments of
> > the message are removed.
> > 
> > I use elog-2.3.5
> > 
> > Alexander.
> 
> Please see elog:280 . I will releae 2.3.6 with this bugfix somewhen during 
> this week.
> 
> - Stefan

Wow! Fast reply!!! Thanks a lot!
ELOG V3.1.5-3fb85fa6