| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
65875
|
Wed May 7 19:55:30 2008 |
 | Stefan Ritt | stefan.ritt@psi.ch | Request | Windows | 2.7.3 | Re: Extending attribute list |
I can get my hand on a C compiler. What the process involved?
Sorry, but teaching you how to compile C programs is beyond the scope of this forum. Please buy a book for that. Most C compilers also comes with some decent documentation. You might try gcc under cygwin or Visual C++. |
|
65874
|
Wed May 7 17:33:54 2008 |
| Paul O'Shaughnessy | paul_o'shaughnessy@inmarsat.com | Request | Windows | 2.7.3 | Re: Extending attribute list |
| Stefan Ritt wrote: |
|
| Paul O'Shaughnessy wrote: |
|
| Stefan Ritt wrote: |
|
| Paul O'Shaughnessy wrote: |
|
Hello everyone, I am new to the forum.
I currently have an attribute which is a list. From this drop down menu, I can only access around 100 options (ELog restriction I think). How can I extend my drop down list to say 200?
Example:
Attributes = RB
Options RB = a, b, c, ...,etc.
|
The number of 100 options is defined in elogd.c with
#define MAX_N_LIST 100
You could try to increase this to 200, but I have no idea if you will hit some other memory limit then. So what about conditional attributes? You subdivide your list into several smaller lists, like
Attributes = Category, RB
Options Category = Cat1{1}, Cat2{2}
{1}Options RB = a,b,c,d...
{2}Options RB = e,f,g,h,...
this is then also easier to handle, as compared to select a value from a very long list.
|
Stefan,
Thanks for that advice. I have made that change to the elogd.c file, but the only problem I don't know how to compile Elog to make that change take effect. I did the stop and restart of the elog service in windows, but that made no difference. How do I compile ELog? Sorry for my ignorance, but I am fairly new to Elog.
|
You need a C compiler to compile Elog under Windows. If you don't have one, I would suggest to follow the advice to use conditional attributes. This does not require a recompilation of Elog.
Stefan,
I can get my hand on a C compiler. What the process involved?
Thanks,
Paul
|
|
|
65873
|
Wed May 7 17:10:07 2008 |
 | Dennis Seitz | dseitz@berkeley.edu | Question | All | latest | $entry time not readable by Subst, else not datetime type? | I posted this on the end of an earlier thread but I thought it might be better to repost as a separate thread:
Thank you for pointing out the method to identify an attribute as a datetime type so that it will sort properly. I now have created my "Last Edit" attribute 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? To reiterate, I want to initialize Last Edit = $entrytime for all entries that have not been re-edited.
Thanks |
|
65872
|
Tue May 6 21:47:32 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Linux | 2.7.3-2058 | Re: any support of encrypted logfiles? |
| Bill Pier wrote: |
|
I'm sure this topic has been visited previously, but a search of this forum didn't show any results.
Is there are support or already proven method of encrypting the logfiles that Elog serves up?
|
There is no native support for encryption inside ELOG, but you can use some external tool to achieve encryption. You can for example use TrueCrypt to mount a virtual encrypted drive, where you store your log files. |
|
65871
|
Tue May 6 21:40:05 2008 |
| Bill Pier | bpier@clove.org | Question | Linux | 2.7.3-2058 | any support of encrypted logfiles? | I'm sure this topic has been visited previously, but a search of this forum didn't show any results.
Is there are support or already proven method of encrypting the logfiles that Elog serves up?
thanks,
Bill
|
|
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. |
|
65869
|
Tue May 6 15:17:52 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Windows | 2.7.3 | Re: Extending attribute list |
| Paul O'Shaughnessy wrote: |
|
| Stefan Ritt wrote: |
|
| Paul O'Shaughnessy wrote: |
|
Hello everyone, I am new to the forum.
I currently have an attribute which is a list. From this drop down menu, I can only access around 100 options (ELog restriction I think). How can I extend my drop down list to say 200?
Example:
Attributes = RB
Options RB = a, b, c, ...,etc.
|
The number of 100 options is defined in elogd.c with
#define MAX_N_LIST 100
You could try to increase this to 200, but I have no idea if you will hit some other memory limit then. So what about conditional attributes? You subdivide your list into several smaller lists, like
Attributes = Category, RB
Options Category = Cat1{1}, Cat2{2}
{1}Options RB = a,b,c,d...
{2}Options RB = e,f,g,h,...
this is then also easier to handle, as compared to select a value from a very long list.
|
Stefan,
Thanks for that advice. I have made that change to the elogd.c file, but the only problem I don't know how to compile Elog to make that change take effect. I did the stop and restart of the elog service in windows, but that made no difference. How do I compile ELog? Sorry for my ignorance, but I am fairly new to Elog.
|
You need a C compiler to compile Elog under Windows. If you don't have one, I would suggest to follow the advice to use conditional attributes. This does not require a recompilation of Elog. |
|
65868
|
Tue May 6 14:49:54 2008 |
| Paul O'Shaughnessy | paul_o'shaughnessy@inmarsat.com | Request | Windows | 2.7.3 | Re: Extending attribute list |
| Stefan Ritt wrote: |
|
| Paul O'Shaughnessy wrote: |
|
Hello everyone, I am new to the forum.
I currently have an attribute which is a list. From this drop down menu, I can only access around 100 options (ELog restriction I think). How can I extend my drop down list to say 200?
Example:
Attributes = RB
Options RB = a, b, c, ...,etc.
|
The number of 100 options is defined in elogd.c with
#define MAX_N_LIST 100
You could try to increase this to 200, but I have no idea if you will hit some other memory limit then. So what about conditional attributes? You subdivide your list into several smaller lists, like
Attributes = Category, RB
Options Category = Cat1{1}, Cat2{2}
{1}Options RB = a,b,c,d...
{2}Options RB = e,f,g,h,...
this is then also easier to handle, as compared to select a value from a very long list.
|
Stefan,
Thanks for that advice. I have made that change to the elogd.c file, but the only problem I don't know how to compile Elog to make that change take effect. I did the stop and restart of the elog service in windows, but that made no difference. How do I compile ELog? Sorry for my ignorance, but I am fairly new to Elog. |
|