I may have missed it when reading the logs, if so, sorry about that, but I would like to know if there is a way to set a field, let us call it "process run" Ok let me give you some details on this.
a process run may have several "work orders" or sets of parts/items in it, so it will have several separate entries in the log such as:
date##, run123, part 1, quantity, comment
date##, run123, part2, quantity, comment
date##, run123, part3, quantity, comment
date##, run123, part4, quantity, comment
I thought perhaps to have them use the reply function to add the other 3 items of the same run, and that would work if I could find a way to set 'process run' to auto increment, say perhaps, when the next 'New' entry was entered. Is there something in place that can already do this? If this is possible, I thought I would see if I can change the button for 'New' to something like 'New Run' and reply to 'Add Workorder' or something along that line so there is no confusion when entering the data.
Any suggestions you might provide are greatfully accepted.
Chuck |
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.
Bill |
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

|