Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 128 of 808  Not logged in ELOG logo
ID Date Icon Author Author Email Category OS ELOG Version Subjectdown
  66396   Mon Jun 15 12:56:32 2009 Reply Stefan Rittstefan.ritt@psi.chQuestionWindowsV2.7.6-219Re: search and datetime

Arno Teunisse wrote:

Hello

I have the following in elog.cfg :

Attributes = Author, Author Email, Category, Customer, server, Subject ,  Change Window Begin , Change Window End
List display = ID,Author, Author Email, Category, Customer, server,  Subject , 
Change Window Begin , Change Window End

Type Change Window Begin = datetime
Type Change Window End = datetime

So I want to be able to give a start and end date to the user.  However : If I open a find/Search I see this :

  Clipboard01.jpg

There are for each  Change Window <item>   we get  Start: and End: time entries. Was expecting only one date entrie .

Why is this ? Seems to be a feature of datetime  or am i missing something.

 

 

Right, that's a feature. Many people want to specify a range when doing a query on a date. Like Change Window Begin after Jan 1st, 2009 and before Jan 5th, 2009. If you just want a single date, set both Start: and End: to the same date, or actually the End: to Start+1 Day to cover all 24 hours of the Start: date. Otherwise when you have data + time, you would have to match the exact second to retrieve a certain entry. So having a range there is more powerful.

  65847   Wed Apr 23 07:46:56 2008 Reply Stefan Rittstefan.ritt@psi.chQuestionAll2.7.3Re: scrollable text section only when viewing a log entry

Bill Pier wrote:

Is there a way, option, feature to setup the text section only to be scrollable when viewing a log entry, such that the header (meta info) section stays fixed?

Unfortunately no.

  65853   Thu Apr 24 23:52:45 2008 Idea Bill Pierbpier@clove.orgQuestionAll2.7.3Re: scrollable text section only when viewing a log entry

Stefan Ritt wrote:

Bill Pier wrote:

Is there a way, option, feature to setup the text section only to be scrollable when viewing a log entry, such that the header (meta info) section stays fixed?

Unfortunately no.

Well, I tinkered a bit with a journal entry display page and found that without having to suggest the flavor-of-the-month web design mantra of "replace table layout with CSS only",  just a few CSS tweaks can enable exactly what I am desiring.

For your consideration, here are the tweaks I made to get a fixed header and footer section with a scrollable journal entry section in the middle:

  1. moved the journal entry content and footer line (elog version info) out of the layout table structure, into their own div sections;
  2. in the style sheet, added attribute "position:fixed" to the "frame table" section;
  3. in the style sheet, added attribute sections for journal entry content and footer div sections:
    1. #content: overflow:auto;position:fixed;top:230px;bottom:30px;width:100%;
    2. #footer:  text-align:center;bottom:0;position:fixed;width:100%;

Now as I'm not a web designer by trade and not intimately familiar with CSS nuances, I used the time honored method of documentation lookup with trial and error.

In any case, it worked and displays exactly the way I wanted; please do consider this for a future elog release.

 

Bill

  65861   Mon Apr 28 08:00:18 2008 Reply Stefan Rittstefan.ritt@psi.chQuestionAll2.7.3Re: scrollable text section only when viewing a log entry

Bill Pier wrote:

Stefan Ritt wrote:

Bill Pier wrote:

Is there a way, option, feature to setup the text section only to be scrollable when viewing a log entry, such that the header (meta info) section stays fixed?

Unfortunately no.

Well, I tinkered a bit with a journal entry display page and found that without having to suggest the flavor-of-the-month web design mantra of "replace table layout with CSS only",  just a few CSS tweaks can enable exactly what I am desiring.

For your consideration, here are the tweaks I made to get a fixed header and footer section with a scrollable journal entry section in the middle:

  1. moved the journal entry content and footer line (elog version info) out of the layout table structure, into their own div sections;
  2. in the style sheet, added attribute "position:fixed" to the "frame table" section;
  3. in the style sheet, added attribute sections for journal entry content and footer div sections:
    1. #content: overflow:auto;position:fixed;top:230px;bottom:30px;width:100%;
    2. #footer:  text-align:center;bottom:0;position:fixed;width:100%;

Now as I'm not a web designer by trade and not intimately familiar with CSS nuances, I used the time honored method of documentation lookup with trial and error.

In any case, it worked and displays exactly the way I wanted; please do consider this for a future elog release. 

Apparently you downloaded an ELOG page and modified it manually. Can you send me the modified page, it then would be easier for me to implement it (I can shorten "my" trial and error phase..)

  65870   Tue May 6 21:28:18 2008 Idea Bill Pierbpier@clove.orgQuestionAll2.7.3Re: scrollable text section only when viewing a log entry

IStefan Ritt wrote:

Bill Pier wrote:

Stefan Ritt wrote:

Bill Pier wrote:

Is there a way, option, feature to setup the text section only to be scrollable when viewing a log entry, such that the header (meta info) section stays fixed?

Unfortunately no.

Well, I tinkered a bit with a journal entry display page and found that without having to suggest the flavor-of-the-month web design mantra of "replace table layout with CSS only",  just a few CSS tweaks can enable exactly what I am desiring.

For your consideration, here are the tweaks I made to get a fixed header and footer section with a scrollable journal entry section in the middle:

  1. moved the journal entry content and footer line (elog version info) out of the layout table structure, into their own div sections;
  2. in the style sheet, added attribute "position:fixed" to the "frame table" section;
  3. in the style sheet, added attribute sections for journal entry content and footer div sections:
    1. #content: overflow:auto;position:fixed;top:230px;bottom:30px;width:100%;
    2. #footer:  text-align:center;bottom:0;position:fixed;width:100%;

Now as I'm not a web designer by trade and not intimately familiar with CSS nuances, I used the time honored method of documentation lookup with trial and error.

In any case, it worked and displays exactly the way I wanted; please do consider this for a future elog release. 

Apparently you downloaded an ELOG page and modified it manually. Can you send me the modified page, it then would be easier for me to implement it (I can shorten "my" trial and error phase..)

Yes, you are correct, I did simply take a sample page from logs and tinker with the html and css file, with the changes enumerated previously.  I have attached the tweaked sample html elog log page and css file, along with a few of the standard elog png files to complete the page with some semblance of the normal display.

Attachment 1: elog-test.html
Attachment 2: elog-test.css
/* default formatting */
body {
  margin:3px;
  color:black;
  background-color:white;
  font-family:trebuc,verdana,tahoma,sans-serif;
  /* background-image:url(elog.gif); */
}

/* standard link colors and decorations */
a:link { color:#0000FF; text-decoration:none }
a:visited { color:#800080; text-decoration:none }
a:hover { color:#0000FF; text-decoration:underline }
a:active { color:#0000FF; text-decoration:underline }
a:focus { color:#0000FF; text-decoration:underline }

td {
  color:black;
  font-size:14px;
}

/* frame table */
.frame {
  width:100%;position:fixed;
}

/* printable frame table */
.pframe {
  width:600px;
}

/* standard formatting for logbook tabs */
.tabs {
  font-family:sans-serif;
  font-size:12pt;
  background-color:white;
}

/* logbook selection page */
.selframe {
  width:60%;
  background-color:#486090; 
  border:1px solid #486090;
  font-size:14pt;
}

.seltitle {
  border:1px solid #0000FF;
  border-top:1px solid white;
  border-left:1px solid white;
  background-color:#CCCCFF;
  color:#486090;
  text-align:center;
}

.selexp {
  border:1px solid #0000FF;
  border-top:1px solid white;
  border-left:1px solid white;
  background-color:#CCCCFF;
  color:#486090;
  text-align:left;
  font-size:10pt;
}

.selspace {
  width:2%;
  border:1px solid #308000;
  border-top:1px solid white;
  border-left:1px solid white;
  background-color:#EEEEEE;
}

.selgroup {
  border:1px solid #308000;
  border-top:1px solid white;
  border-left:1px solid white;
  background-color:#FFCCFF;
  padding:3px;
  text-align:left;
  font-weight:bold;
  font-size:14pt;
}

.sellogbook {
  border:1px solid #308000;
  border-top:1px solid white;
  border-left:1px solid white;
  background-color:#DDEEBB;
  padding:3px;
  text-align:left;
  font-weight:bold;
}

.selcomment {
  font-size:10pt;
}

.selentries {
  background-color:#E0E0A0;
  border:1px solid #0000FF;
  border-top:1px solid white;
  border-left:1px solid white;
  text-align:center;
  font-size:12pt;
}

/* unselected and selected group tabs */

.gtab a {
  background-color:#B0E0B0;
  padding-left:5px;
  padding-right:5px;
}

.gtab {
  background-color:#B0E0B0;
  border-right:1px solid #409040;
}

.sgtab a {
  color:white;
  padding-left:5px;
  padding-right:5px;
}

.sgtab {
  background-color:#486090;
  color:white;
  border-right:1px solid #084070;
}

.sgtab a:visited { color:white; } /* bug for IE */

/* unselected and selected logbook tabs */

.ltab a {
  background-color:#E0E0E0;
  padding-left:5px;
  padding-right:5px;
}

.ltab {
  background-color:#E0E0E0;
  border-top:1px solid white;
  border-left:1px solid white;
  border-right:1px solid gray;
}

.sltab a {
  background-color:#486090;
  color:white;
  padding-left:5px;
  padding-right:5px;
}

.sltab {
  background-color:#486090;
  color:white;
  border-left:1px solid #E0E0E0;
  border-right:1px solid #084070;
}

.sltab a:visited { color:white; } /* bug for IE */

/* logbook title, left, middle and right cell */

.title1 {
  padding:5px;
  background-color:#486090;
  border-bottom:1px solid black;
  border-left:1px solid #E0E0E0;
  color:white;
  font-size:medium;
  font-family:sans-serif;
  text-align:left;
}

.title1 a:visited { color:#A0FFA0; }
.title1 a:link { color:#A0FFA0; }

.title2 {
  background-color:#486090;
  border-bottom:1px solid black;
  color:white;
  font-size:medium;
  font-family:sans-serif;
  text-align:center;
}

.title3 {
  border-bottom:1px solid black;
  border-right:1px solid black;
  background-color:#486090;
  text-align:right;
  width:100px;
}

/* main menu row */

.menuframe {
  border:1px solid #486090;
  border-top:1px solid white;
  border-left:1px solid white;
  background-color:#E0E0E0;
}

.menu1 {
  text-align:left;
  font-size:12pt;
}

.menu1a {
  text-align:right;
  font-size:10pt;
  font-weight:bold;
}

.menu2a {
  text-align:left;
  font-size:10pt;
}

.menu2b {
  text-align:right;
  font-size:10pt;
}

.menu3 {
  text-align:left;
  font-size:8pt;
  font-weight:bold;
}

.menu4 {
  text-align:right;
  font-size:10pt;
  vertical-align:middle;
}

.menucenter {
  border:1px solid #486090;
  border-top:1px solid white;
  border-left:1px solid white;
  background-color:#E0E0E0;
  text-align:center;
  font-size:10pt;
}

.toolframe {
  border:1px solid #486090;
  border-top:1px solid white;
  border-left:1px solid white;
  background-color:#E0E0E0;
  padding:2px;
}

/* frame table in listings */
.listframe {
  border:1px solid #0000FF;
  border-top:1px solid white;
  border-left:1pc solid white;
  background-color:#486090;
  border:0px;
}

/* title row in listing */
.listtitle {
  border:1px solid #0000FF;
  border-top:1px solid white;
  border-left:1px solid white;
  background-color:#CCCCFF;
  text-align:center;
}

/* odd and even lines in message listing */

.list1 {
  border:1px solid #308000;
  border-top:1px solid white;
  border-left:1px solid white;
  background-color:#DDEEBB;
  text-align:center;
}

.list2 {
  border:1px solid #808040;
  border-top:1px solid white;
  border-left:1px solid white;
  background-color:#FFFFB0;
  text-align:center;
}

.list1h {
  border:1px solid #308000;
  border-top:1px solid white;
  border-left:1px solid white;
  background-color:#DDEEBB;
  text-align:center;
  font-weight:bold;
... 360 more lines ...
Attachment 3: last.png
last.png
Attachment 4: first.png
first.png
Attachment 5: elog.png
elog.png
Attachment 6: previous.png
previous.png
Attachment 7: next.png
next.png
  66213   Thu Feb 19 18:19:12 2009 Question Bill Pierbpier@clove.orgQuestionAll2.7.3Re: scrollable text section only when viewing a log entry

Bill Pier wrote:

IStefan Ritt wrote:

Bill Pier wrote:

Stefan Ritt wrote:

Bill Pier wrote:

Is there a way, option, feature to setup the text section only to be scrollable when viewing a log entry, such that the header (meta info) section stays fixed?

Unfortunately no.

Well, I tinkered a bit with a journal entry display page and found that without having to suggest the flavor-of-the-month web design mantra of "replace table layout with CSS only",  just a few CSS tweaks can enable exactly what I am desiring.

For your consideration, here are the tweaks I made to get a fixed header and footer section with a scrollable journal entry section in the middle:

  1. moved the journal entry content and footer line (elog version info) out of the layout table structure, into their own div sections;
  2. in the style sheet, added attribute "position:fixed" to the "frame table" section;
  3. in the style sheet, added attribute sections for journal entry content and footer div sections:
    1. #content: overflow:auto;position:fixed;top:230px;bottom:30px;width:100%;
    2. #footer:  text-align:center;bottom:0;position:fixed;width:100%;

Now as I'm not a web designer by trade and not intimately familiar with CSS nuances, I used the time honored method of documentation lookup with trial and error.

In any case, it worked and displays exactly the way I wanted; please do consider this for a future elog release. 

Apparently you downloaded an ELOG page and modified it manually. Can you send me the modified page, it then would be easier for me to implement it (I can shorten "my" trial and error phase..)

Yes, you are correct, I did simply take a sample page from logs and tinker with the html and css file, with the changes enumerated previously.  I have attached the tweaked sample html elog log page and css file, along with a few of the standard elog png files to complete the page with some semblance of the normal display.

 

 

Thu Feb 19 18:18:20 2009  Did this suggestion ever get considered for implementation?

 

 

  66215   Fri Feb 20 07:58:52 2009 Reply Stefan Rittstefan.ritt@psi.chQuestionAll2.7.3Re: scrollable text section only when viewing a log entry

 

Bill Pier wrote:

 

Bill Pier wrote:

 

IStefan Ritt wrote:

 

Bill Pier wrote:

 

Stefan Ritt wrote:

 

Bill Pier wrote:

Is there a way, option, feature to setup the text section only to be scrollable when viewing a log entry, such that the header (meta info) section stays fixed?

 

Unfortunately no.

 

Well, I tinkered a bit with a journal entry display page and found that without having to suggest the flavor-of-the-month web design mantra of "replace table layout with CSS only",  just a few CSS tweaks can enable exactly what I am desiring.

For your consideration, here are the tweaks I made to get a fixed header and footer section with a scrollable journal entry section in the middle:

  1. moved the journal entry content and footer line (elog version info) out of the layout table structure, into their own div sections;
  2. in the style sheet, added attribute "position:fixed" to the "frame table" section;
  3. in the style sheet, added attribute sections for journal entry content and footer div sections:
    1. #content: overflow:auto;position:fixed;top:230px;bottom:30px;width:100%;
    2. #footer:  text-align:center;bottom:0;position:fixed;width:100%;

Now as I'm not a web designer by trade and not intimately familiar with CSS nuances, I used the time honored method of documentation lookup with trial and error.

In any case, it worked and displays exactly the way I wanted; please do consider this for a future elog release. 

 

Apparently you downloaded an ELOG page and modified it manually. Can you send me the modified page, it then would be easier for me to implement it (I can shorten "my" trial and error phase..)

 

Yes, you are correct, I did simply take a sample page from logs and tinker with the html and css file, with the changes enumerated previously.  I have attached the tweaked sample html elog log page and css file, along with a few of the standard elog png files to complete the page with some semblance of the normal display.

 

 

Thu Feb 19 18:18:20 2009  Did this suggestion ever get considered for implementation?

 

 

 

 

 Yes it's on my personal to-do list, but don't know when I will find some time.

  534   Wed May 5 17:38:12 2004 Reply Stefan Rittstefan.ritt@psi.ch Linux2.5.2Re: safari browser issue
> we've experienced a problem when using the safari browser to do a search in
> our elog. whenever you do a search, the logbook returns an error and the
> elog deamon crashes. when we first experienced this problem we were running
> version 2.3.9. however, an upgrade to version 2.5.2 doesn't seem to fix the
> problem. searches with other browsers (mozilla, internet explorer, ...) go
> off without a hitch.
> has anyone else observed a similar problem or have any ideas on how to
> resolve this issue.
> thanks for the help.

I finally found some time to address this problem. It was related to the way I
do the page redirection. The "Location:" in the HTTP header used a relative
path, although the standard requires an absolute (full) path, which I just
discovered. Although most browsers accept a relative path, the safari browser
obviously does not. 

I changed the redirection to absolute paths, the new version can be obtained
via CVS.
ELOG V3.1.5-3fb85fa6