| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
65859
|
Fri Apr 25 19:56:48 2008 |
 | svrmarty | svrmarty@gmx.net | Question | | | Re: how to set locale for date/time |
| Stefan Ritt wrote: |
|
| svrmarty wrote: |
|
| Stefan Ritt wrote: |
|
| svrmarty wrote: |
|
is there any new option i can use/configure ?
i still get the english datetime
Eingabezeit: Thu Mar 27 09:27:41 2008
|
As I told you, you have to upgrade to SVN revision 2098 or later.
|
i've updated to ELOG V2.7.3-2104
|
Well, then you should get German locale. I just tried with the same version and following elogd.cfg, so I don't know what you are doing wrong:
[global]
port = 8080
language = german
[demo]
Attributes = Author, Type, Category, Subject
|
great, works now
thx a lot
i had to create de_DE locales, we only use de_AT, this is for austria, where we live
|
|
65860
|
Sat Apr 26 09:26:53 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | 2.7.3 | Re: Increment a field automatically on a new thread vs every entry |
| Chuck Brost wrote: |
|
Ok, nevermind that one, Dumb Question I think, now that I have figured out that the field I was concerned with does not increment in a reply already. So.. that only leaves my one question, is there somewhere that I can change the text, not the action, on the menu so that I can do a reply, but have the link list as something like "New Item".?
|
Unfortunately this is not possible at the moment. |
|
65861
|
Mon Apr 28 08:00:18 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | All | 2.7.3 | Re: 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:
- 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..) |
|
65862
|
Mon Apr 28 13:37:01 2008 |
| W.Koster | W.Koster@rug.nl | Question | | | Re: configuration of rss feeds | > Have you tried the RSS Title option?
doh ... thanks, works perfectly (well apart from the lost end-of-lines in the text portion) |
|
65863
|
Tue Apr 29 02:00:03 2008 |
| Dennis Seitz | dseitz@cosmology.berkeley.edu | Question | | 2.7.0 | Re: Possible to sort attribute chronologically? | > > The only caveat is that
> > when you edit an entry, the "Last Edit" is displayed really in seconds since 1970, but I will
> > fix this in the next release.
>
> I just fixed this in SVN revision #2010. If you would have filled out which operating system you use
> with elog, I could tell you how to upgrade.
Thank you for pointing out the method to identify Last Edit as a datetime type so that it will sort properly. I now have created Last Edit in several
preexisting logbooks.
I want to use
Start page = ?rsort=Last Edit
to set the default sorting of each logbook to be by Last Edit.
However, all of the entries made before I added Last Edit have no value for that field, so they are all grouped together at the end of the sort. So I
decided to go through the older entries and set Last Edit equal to the original entry date, as a starting value.
I tried to use the command
Subst on edit Last Edit = $entry time
but it gives a "-" for the Last Edit value when I edit an entry.
I think this is because $entry time is not a variable supported by Subst. Can you add that support, or else tell me if you know a better way to go about
doing what I'm attempting? Is there perhaps a way to globally process a group of entries in a logbook and set one attribute's value to be equal to
another's?
Thanks |
|
65865
|
Sat May 3 14:59:14 2008 |
 | mike cianci | mike2.cianci@comcast.net | Question | Windows | | Mass postings | I am setting this up as instrument log in a multi-hospital system, where there will be multiple instruments, in multiple departments, at multiple facilities.
I am using the "Top Group" function to keep the books separate so operators from one instrument/department/facility don't contaminate another instrument/department/facility's logbook.
What I am wondering is there someway to set it up so that a system wide manager could post a message to 5 individual logbooks for 5 identical instruments at 5 different locations all at once (one ELOG server)?
I hope this made sense. Thank you for your help. |
|
65866
|
Mon May 5 08:44:03 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Windows | | Re: Mass postings |
| mike cianci wrote: |
|
I am setting this up as instrument log in a multi-hospital system, where there will be multiple instruments, in multiple departments, at multiple facilities.
I am using the "Top Group" function to keep the books separate so operators from one instrument/department/facility don't contaminate another instrument/department/facility's logbook.
What I am wondering is there someway to set it up so that a system wide manager could post a message to 5 individual logbooks for 5 identical instruments at 5 different locations all at once (one ELOG server)?
I hope this made sense. Thank you for your help.
|
Unfortunately this is not possible at the moment. You would have to use the menu command "copy to" and enable it for the admin user. Then you create your entry, and click on "copy to" once for each location you want to copy this entry. |
|
65870
|
Tue May 6 21:28:18 2008 |
 | Bill Pier | bpier@clove.org | Question | All | 2.7.3 | Re: 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:
- 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. |
| 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
|
|
| Attachment 4: first.png
|
|
| Attachment 5: elog.png
|
|
| Attachment 6: previous.png
|
|
| Attachment 7: next.png
|
|
|