ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
1786
|
Mon Apr 3 16:32:52 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | All | 2.6 | Re: Numerous questions that I am hoping to get a response on |
Steve Jones wrote: | Stefan, I have several issues/questions that I am still hoping to get an answer on. Any chance? If you would rather you can send email to me directly. |
I'm pretty busy these days, since we have a deadline on April 18th. I started already working weekends, so not much time is left for ELOG. But I hope it will get better by the end of this month. |
1787
|
Mon Apr 3 16:39:33 2006 |
| Steve Jones | steve.jones@freescale.com | Question | All | 2.6 | Re: Numerous questions that I am hoping to get a response on |
Steve Jones wrote: |
Stefan Ritt wrote: |
Steve Jones wrote: | Stefan, I have several issues/questions that I am still hoping to get an answer on. Any chance? If you would rather you can send email to me directly. |
I'm pretty busy these days, since we have a deadline on April 18th. I started already working weekends, so not much time is left for ELOG. But I hope it will get better by the end of this month. |
I fully understand and appreciate your response! |
|
1788
|
Mon Apr 3 17:09:19 2006 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | All | 2.6.1-1668 | Re: elogd 2.6.1 program Crash is repeatable under Windows |
Steve Jones wrote: | BTW, Stefan, unless you can make the most recent version of a Windows eLog available I cannot test the most recent -- I do not have access to a Windows development environment. Solaris-Yes, Linux-Yes, Windoze-No. |
There is a 2.6.1-4 version for Windows for download, which contains the most recent code. |
1796
|
Wed Apr 5 20:25:42 2006 |
| Steve Jones | steve.jones@freescale.com | Question | All | 2.6.1-1684 | Triggering $shell question | Should this work? rev1684 now allows $shell to pass attribute contents to the shell command and whenever a new entry is submitted or when one Edits/Replys the Subst is triggered, but I would like to be able to trigger this whenever a new value in the options pulldown is selected (assume Risk2 and Risk3 are identical to Risk1). Being able to trigger a regular Preset works fine (like {1} preset Date = $date ) but I would like to trigger the Subst. Maybe a better question, what actions (Subst, Preset, Change, Execute, etc.) I've tried Subst and Preset but not much luck.
##################################################
# Define Risk1
#
Options Risk1 = 10{30}, 20{31}, 30{32}, 40{33}, 50{34}, 60{35}, 70{36}, 80{37}, 90{38}, 100{39}
{30,31,32,33,34,35,36,37,38,39} Subst TotalRisk = $shell(gawk 'BEGIN{ print $Risk1 + $Risk2 + $Risk3 }' )
|
1797
|
Wed Apr 5 22:48:49 2006 |
| Steve Jones | steve.jones@freescale.com | Question | All | 2.6.1-1684 | Re: Triggering Re: Triggering $shell question |
Steve Jones wrote: | Should this work? rev1684 now allows $shell to pass attribute contents to the shell command and whenever a new entry is submitted or when one Edits/Replys the Subst is triggered, but I would like to be able to trigger this whenever a new value in the options pulldown is selected (assume Risk2 and Risk3 are identical to Risk1). Being able to trigger a regular Preset works fine (like {1} preset Date = $date ) but I would like to trigger the Subst. Maybe a better question, what actions (Subst, Preset, Change, Execute, etc.) I've tried Subst and Preset but not much luck.
##################################################
# Define Risk1
#
Options Risk1 = 10{30}, 20{31}, 30{32}, 40{33}, 50{34}, 60{35}, 70{36}, 80{37}, 90{38}, 100{39}
{30,31,32,33,34,35,36,37,38,39} Subst TotalRisk = $shell(gawk 'BEGIN{ print $Risk1 + $Risk2 + $Risk3 }' )
|
Hmm, maybe I can answer my own question - until the form is saved with the new value selected the old values still exist. I guess what I really need is to trigger the $shell anytime a save happens or logentry is pulled in for edit. I think I do the latter with Subst on edit/Subst on Reply, but how on any save?
. . . Except that when I change an options field that has a dependencies, doesn't the javascript force a server-side revalidation? |
1800
|
Fri Apr 7 05:07:20 2006 |
| Steve Jones | steve.jones@freescale.com | Bug report | All | 2.6.1-1668 | Re: elogd 2.6.1 program Crash is repeatable under Windows |
Stefan Ritt wrote: |
Steve Jones wrote: | BTW, Stefan, unless you can make the most recent version of a Windows eLog available I cannot test the most recent -- I do not have access to a Windows development environment. Solaris-Yes, Linux-Yes, Windoze-No. |
There is a 2.6.1-4 version for Windows for download, which contains the most recent code. |
Quote: | Ok, I loaded the new Windows version ELOG V2.6.1-1681. The new version has the same behavior and it is entirely related to Top Group. With a simple Top Group setup things appear to work fine until one attempts to either create or delete a new logbook. There are other quirky things - I don't think Top Group is ready for really complex setups. In fact, this URL that is constructed by elog (http://localhost:8080/Engineering%20Compute%20Change%20Logs/Test/?cmd=Config) will cause elog to coredump but only with a very complex configfile. If I simply remove the "Top" from the "Group" directive I get the expected message "Error: logbook "Engineering Compute Change Logs" not defined in elogd.cfg
Please use your browser's back button to go back".
Another interesting point of reference - I went back to 2.5.9-4 (windows) and get the same behavior.
Now, making things really simple I added Top Group support to the demo that comes with the Windows install. This configfile:
[global]
port = 8080
Show top groups = 1
Top Group Demo Groups = demo, test7
[global Demo Groups]
Theme = default
Comment = General linux tips & tricks
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Extendable Options = Category
Required Attributes = Author, Type
Page Title = ELOG - $subject
Reverse sort = 1
Quick filter = Date, Type
[demo]
results in this redisplay after a new logbook create I have included in an attached screenshot. Please note that everything is generally not correct. So, even though eLog does not crash with this simple config it does support my observation that as I render the congfile more complex I corrupt eLog more until it finally crashes. Stefan, I would be interested in seeing how the above config runs on one of your windows systems. |
1802
|
Mon Apr 10 05:34:40 2006 |
| Steve Jones | steve.jones@freescale.com | Request | All | 2.6.1-1684 | TIMEZONE modifier? | We host eLog for a number of global sites. Our logbooks use datetime attributes but the timezones are wrong attributes that are either preset (like when a logentry is created) or if we fill in an attribute from an action (like when a logentry is closed). Any possibility of adding a timezone designator to FORMAT or does one already exist?
Thanks! |
1806
|
Wed Apr 12 19:22:34 2006 |
| Sridhar Anandakrishnan | sak@essc.psu.edu | Question | All | | Can a field value be calculated during display? | I have a logbook which is a Calendar/Appointment book with Attributes: "Appointment DateTime", Place, etc.
I would like another Attribute called "When" whose value is calculated from Today's Date - Appointment date (so for example I could display today's appointments in red...). This calculation has to take place each time the logbook is displayed...
Possible? Useful?
Thanks,
Sridhar. |
|
ELOG V3.1.5-3fb85fa6 |