Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 689 of 806  Not logged in ELOG logo
ID Date Icon Author Author Email Category OSdown ELOG Version Subject
  65944   Fri Aug 8 00:44:26 2008 Question dale cooperagentdcooper@gmail.comQuestionAll2.7.4x2 questions :: different colors in list view based on "type" + change verbage of "type"

hello all,

#1 i love ELOG : excellent app! i would like to ask/present a question here -- I have a couple of TYPE's defined as;

       Options Type = Day Shift, Swing Shift, Night Shift
What I'd love to be able to do, is depending on what TYPE was selected during the creation of a NEW ENTRY in the ELOG "shift log" I'd love to display in the LIST VIEW (full, summary, or threaded views) different color's based on which TYPE was selected...

for example, if someone chose "Day Shift" that would be listed with a GREEN background, if someone chooses "Swing Shift" that gets a BLUE background, and so forth... I am wondering how one would go about implementing this?

second question... instead of listing the column named TYPE, can I just change it somewhere in the config to "SHIFT" so that in the list view, and even when in the NEW ENTRY form, I'd like it to show "Shift" instead of TYPE --- really I am just wondering if I can change the verbage that ELOG is using for the term TYPE? Is that doable?

 

Thanks for the app, I look forward to any reponses! I been editing the CSS, and once done think I'll add it to yr Config Examples, as I don't see many CSS themes there...

-peace-

  65945   Fri Aug 8 14:20:27 2008 Reply Yoshio ImaiQuestionAll2.7.4xRe: 2 questions :: different colors in list view based on "type" + change verbage of "type"

dale cooper wrote:
I'd love to display in the LIST VIEW (full, summary, or threaded views) different color's based on which TYPE was selected...

You can achieve this by using a "style" directive for this attribute. E.g. if your attribute is called "Shift" and entries with value "Day" should be green, value "Swing" should be blue, you should add
Style Shift Day = background-color:green
Style Shift Swing = background-color:blue
(and so on) to the config file.



Quote:
really I am just wondering if I can change the verbage that ELOG is using for the term TYPE? Is that doable?

As long as I am not missing a key point in your problem, you should be able to define the names of your logbook attributes simply with the "Attribute" directive. So, if you want the users to enter the shift and the name of the shift leader, you would put a line
Attributes = Shift, Shift leader
Options Shift = Day, Swing, ... <and so on>
Options Shift leader = Mike, Edward, John, ... <and so on>
and the logbook display should correctly show "Shift" and "Shift leader" in the header line of each entry ...
  65948   Mon Aug 11 06:56:56 2008 Reply dale cooperagentdcooper@gmail.comQuestionAll2.7.4xRe: 2 questions :: different colors in list view based on "type" + change verbage of "type"
PERFECT, you answered my questions EXACTLY with what I am looking for! thanks soo much!
agentdcooper


Yoshio Imai wrote:

dale cooper wrote:
I'd love to display in the LIST VIEW (full, summary, or threaded views) different color's based on which TYPE was selected...

You can achieve this by using a "style" directive for this attribute. E.g. if your attribute is called "Shift" and entries with value "Day" should be green, value "Swing" should be blue, you should add
Style Shift Day = background-color:green
Style Shift Swing = background-color:blue
(and so on) to the config file.



Quote:
really I am just wondering if I can change the verbage that ELOG is using for the term TYPE? Is that doable?

As long as I am not missing a key point in your problem, you should be able to define the names of your logbook attributes simply with the "Attribute" directive. So, if you want the users to enter the shift and the name of the shift leader, you would put a line
Attributes = Shift, Shift leader
Options Shift = Day, Swing, ... <and so on>
Options Shift leader = Mike, Edward, John, ... <and so on>
and the logbook display should correctly show "Shift" and "Shift leader" in the header line of each entry ...
  65989   Wed Oct 8 15:10:25 2008 Question NeoNeo.X@web.deQuestionAll Deny Wildcards
Ist there a possibility to use wildcards specifiing the users who are allowed to use a command, like ... Allow New = admin1, admin2, admin3 Allow Edit = admin1, admin2, admin3 Deny New = * Deny Edit = *
  65990   Wed Oct 8 15:23:56 2008 Reply Stefan Rittstefan.ritt@psi.chQuestionAll Re: Deny Wildcards

 

Neo wrote:
Ist there a possibility to use wildcards specifiing the users who are allowed to use a command, like ... Allow New = admin1, admin2, admin3 Allow Edit = admin1, admin2, admin3 Deny New = * Deny Edit = *

 

 Wildcards are not implemented for that purpose. But a "Allow New = admin1, admin2" implicitly denies this command for all other users, I guess that's what you want. There is also the possibility to use "Guest Menu Commands" to allow everybody to read entries, but only logged in users to write and modify them.

  65991   Wed Oct 8 15:31:49 2008 Reply NeoNeo.X@web.deQuestionAll Re: Deny Wildcards

Stefan Ritt wrote:

 

Neo wrote:
Ist there a possibility to use wildcards specifiing the users who are allowed to use a command, like ... Allow New = admin1, admin2, admin3 Allow Edit = admin1, admin2, admin3 Deny New = * Deny Edit = *

 

 Wildcards are not implemented for that purpose. But a "Allow New = admin1, admin2" implicitly denies this command for all other users, I guess that's what you want. There is also the possibility to use "Guest Menu Commands" to allow everybody to read entries, but only logged in users to write and modify them.

 

I tried it in a global group configuration

[global monitoring]
Allow Edit = admin1, admin2
Allow New = admin1

But I as admin2 am still able to create new entries in the corresponding log books.

Is this configuration only for logbooks?

  65992   Wed Oct 8 21:37:32 2008 Reply Stefan Rittstefan.ritt@psi.chQuestionAll Re: Deny Wildcards

Neo wrote:

 

I tried it in a global group configuration

[global monitoring]
Allow Edit = admin1, admin2
Allow New = admin1

But I as admin2 am still able to create new entries in the corresponding log books.

Is this configuration only for logbooks?

 I just tried myself with following config:

[global]
port = 8080
password file = passwd
Allow New = joe

[demo1]
Theme = default
Attributes = Author, Subject

and it jus worked fine. When I'm not logged on as "joe", the "New" command even does not appear. If you would have supplied your correct ELOG version, I could have checked if you have an old version. In that case you could upgrade.

  66008   Mon Oct 20 15:32:19 2008 Question T. Ribbrockemgaron+elog@ribbrock.orgQuestionAll2.7.5-2130(How) can I hide columns in List view?

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

ELOG V3.1.5-3fb85fa6