ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
66215
|
Fri Feb 20 07:58:52 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | All | 2.7.3 | Re: 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:
- moved the journal entry content and footer line (elog version info) out of the layout table structure, into their own div sections;
- in the style sheet, added attribute "position:fixed" to the "frame table" section;
- in the style sheet, added attribute sections for journal entry content and footer div sections:
- #content: overflow:auto;position:fixed;top:230px;bottom:30px;width:100%;
- #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. |
66236
|
Wed Mar 4 22:47:46 2009 |
| Val Schmidt | vschmidt@ldeo.columbia.edu | Question | All | 2.7.5 | Email authentication with SSL/TLS |
Hi,
I'm curious is it possible to send email notificaitons from elog through an smtp server that requires SSL/TLS authentication? I think it's not but I thought I'd ask.
-Val
ps. sorry for the initial blank post... |
66239
|
Fri Mar 6 21:51:48 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | All | 2.7.5 | Re: Email authentication with SSL/TLS |
Val Schmidt wrote: |
Hi,
I'm curious is it possible to send email notificaitons from elog through an smtp server that requires SSL/TLS authentication? I think it's not but I thought I'd ask.
-Val
|
This is currently not implemented and will probably not implemented in the next time, but it's on my (very long) to-do list. |
66257
|
Thu Mar 19 02:50:16 2009 |
| Erik Iverson | eiverson@ornl.gov | Question | All | 2.7.4 | "Full" view formatting |
I have a logbook I use to capture machine settings. There are many (~30) different attributes defined. I've defined the "Summary" view via "List display" in such a way that not all the attributes are displayed in the summary list, because there's no practical way to fit the 30 different attributes in 30 rows across the screen, and there's no need to have every attribute shown in the summary view. I would like to define something for the "Full" view that lets me put one (or more, but not all) attributes per line; much like the single-entry view does now, just with multiple entries. So a "Full" listing would look like
ID: 1
Attribute1: Value1
Attribute2: Value2
Attribute3: Value3
Text...
ID: 2
Attribute1: Value1
Attribute2: Value2
Attribute3: Value3
Text...
rather than
ID Attribute1 Attribute2 Attribute3
1 Value1 Value2 Value3
Text...
2 Value1 Value2 Value3
Text...
etc.
Any suggestions?
Thanks as always for a wonderful piece of software! |
66258
|
Fri Mar 20 14:33:53 2009 |
| Gernot Buselmeier | Gernot.Buselmeier@gefanuc.com | Question | All | 2.7.3 | Escape emoticons in ELCODE |
Hi,
I want to write a text like "John:Doe" in ELCODE. However the ":D" is converted to a LOL emoticon. I tried various ways to escape this. One solution I found was entering "John\:Doe". However, the upper-case D is converted to lower-case: the result reads "John:doe".
Thanks for an answer and many thanks for providing ELOG.
Gernot |
66263
|
Tue Mar 24 10:34:14 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | All | 2.7.3 | Re: Escape emoticons in ELCODE |
Gernot Buselmeier wrote: |
Hi,
I want to write a text like "John:Doe" in ELCODE. However the ":D" is converted to a LOL emoticon. I tried various ways to escape this. One solution I found was entering "John\:Doe". However, the upper-case D is converted to lower-case: the result reads "John:doe".
Thanks for an answer and many thanks for providing ELOG.
Gernot
|
Thanks for reporting this bug. I fixed it in revision #2180. |
66264
|
Tue Mar 24 10:42:25 2009 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | All | 2.7.4 | Re: "Full" view formatting |
Erik Iverson wrote: | I have a logbook I use to capture machine settings. There are many (~30) different attributes defined. I've defined the "Summary" view via "List display" in such a way that not all the attributes are displayed in the summary list, because there's no practical way to fit the 30 different attributes in 30 rows across the screen, and there's no need to have every attribute shown in the summary view. I would like to define something for the "Full" view that lets me put one (or more, but not all) attributes per line; much like the single-entry view does now, just with multiple entries. So a "Full" listing would look like
ID: 1
Attribute1: Value1
Attribute2: Value2
Attribute3: Value3
Text...
ID: 2
Attribute1: Value1
Attribute2: Value2
Attribute3: Value3
Text...
rather than
ID Attribute1 Attribute2 Attribute3
1 Value1 Value2 Value3
Text...
2 Value1 Value2 Value3
Text...
etc.
Any suggestions?
Thanks as always for a wonderful piece of software! |
This is not implemented, but I will consider it for a future version. |
66273
|
Wed Mar 25 14:16:21 2009 |
| Tero Suominen | tero.suominen73@gmail.com | Question | All | 2.7.5-2168 | How to configure eLog to send an e-mail notification when new logbook entry time is reached? |
Hello!
First I would like to thank you for making such a good free software available:). Then right back into the busness. I have a question to developers. I used the following Options to get the logbook entry which defines the licences expiration date (See the attachement). Now I would like to ask on how to configure eLog to send an e-mail notification when this date is reached?
Attributes = Licence Expiration date
Type Licence Expiration date = date
Date format = %A, %B %d, %Y
The ideal solution would be to have configurable variable which would automatically send a notification X days before the expiration date is reached. Do you think this would be possible feature request to this Forum into eLog wishlist?
BR,
Tero Suominen
|
Attachment 1: Expiration_field.GIF
|
|