ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
65799
|
Tue Apr 1 02:04:35 2008 |
| Dennis Seitz | dseitz@berkeley.edu | Request | All | | Duplicate entry suggestion | We have configured several logbooks to allow users to duplicate an entry in another logbook, which is very useful for entries which apply to more than one category.
However, once the entry is duplicated, subsequent revisions to the original entry are not copied to the duplicate entries.
I can see where implementing that would add a lot of code to ELOG. Rather than do that, would it be possible to add a configuration option to duplicate only the attributes, and place a link to the original entry in the body of the duplicated entry instead of the full text?
Thanks,
Dennis |
65804
|
Tue Apr 1 21:24:17 2008 |
| Dennis Seitz | dseitz@berkeley.edu | Request | All | | attachment indicator in summary view | It would be nice to have the option of including an attachment indicator column in summary view to show if an entry has any attachments.
Thanks. |
65827
|
Sat Apr 12 16:37:44 2008 |
| Arno Teunisse | A.teeling3@chello.nl | Info | Windows | | Manual installing elog as service on Windows | Hello
Sometimes it can come in handy to start a temporary elog service on the Windows platform. ( Maybe for testing purposes )
You can use the SC.exe utility to do that. If it is not on you're system you may download it from : ftp://ftp.microsoft.com/reskit/win2000/sc.zip
For this you can use the following procedure ( from the dos prompt ) :
sc.exe create AIX-elog binPath= "\"c:\ELOG2.7.3\elogd.exe\" -D -c c:\ELOG2.7.3\security.cfg" DisPlayname= "AIX Elog Security" start= auto
If all went well the system answers :
[SC] CreateService SUCCESS
Please notice the strange way the double quotes are used and the space after the = in the above command.
Now open the windows services ( from the prompt ) : services.msc
In the window that opens you will see the just created service with the DisPlayname you gave in the above command.
You see it is not started. You could click start, but there is an other way.
Now you can start the service from the prompt using the DisPlayname :
net start "AIX elog security"
Press F5 ( refresh ) in the services window and you will see that the service is started.
Or stop the service :
net stop "AIX elog security"
To remove the service ( from the registry ) :
sc.exe delete AIX-elog
The system gives back :
[SC] DeleteService SUCCESS
The other option is to start elogd.exe from the prompt :
elogd.exe -c
This is all for now
|
65848
|
Wed Apr 23 10:53:58 2008 |
| Willem Koster | W.Koster@rug.nl | Request | | | Request: elog as a "web service" ? (xml / soap) | We're using elog as our CMDB, but now management wants us to employ "web services" and I fear going to another tool (elog is fitting the admins like a glove, so we'd rather keep it)
Is it possible to configure elog to be able to run as a web-service ? (basically getting xml-output according to a specific (SOAP) schema instead of html output)
http://en.wikipedia.org/wiki/Web_services
A 'Web service' (also Web Service) is defined by the W3C as "a software system designed to support interoperable Machine to Machine interaction over a network." Web services are frequently just Web APIs that can be accessed over a network, such as the Internet, and executed on a remote system hosting the requested services.
The W3C Web service definition encompasses many different systems, but in common usage the term refers to clients and servers that communicate using XML messages that follow the SOAP standard. Common in both the field and the terminology is the assumption that there is also a machine readable description of the operations supported by the server written in the Web Services Description Language (WSDL). The latter is not a requirement of a SOAP endpoint, but it is a prerequisite for automated client-side code generation in many Java and .NET SOAP frameworks (frameworks such as Spring and Apache CXF being notable exceptions). Some industry organizations, such as the WS-I, mandate both SOAP and WSDL in their definition of a Web service. |
65850
|
Wed Apr 23 18:59:30 2008 |
| Jochen Krempel | krempel(at)ill.fr | Request | All | 2.7.3 | LaTeX support | I would appreciate if elog could provide a simple support for mathematical expressions.
A solution similar to wikimedia should be easy to implement and would help a lot.
http://www.mediawiki.org/wiki/Manual:Running_MediaWiki_on_Windows#Alternative_Solution
The idea is to parse the elog entry for a tag (e.g. <math></math>), extract the code, wrap it into a latex file, and pass this to latex, GhostScript, and ImageMagic. (The latter are already used by Elog, therefore the changes should not be too big.) The resulting image file would then be referenced by the elog html code.
Of course, the FCKeditor would not support LaTeX. However, the majority of elog-useres should be scientists and rather familiar with LaTeX. Therefore it should be fine if the original LaTeX code is saved (e.g. in the ALT-tag of the image) and the replacement "code to image" is undone for editing.
Kind regards,
Jochen |
65853
|
Thu Apr 24 23:52:45 2008 |
| Bill Pier | bpier@clove.org | Question | All | 2.7.3 | Re: 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:
- 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 |
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
|
|
65878
|
Mon May 12 10:16:21 2008 |
| Grant Jeffcote | grant@jeffcote.org | Question | | 2.7.3-1024 | Access Control | Hi Stefan,
We have a configuration where different sites have their own logbooks all under the same server, these are accessed by relevant parties as you might expect by selecting the appropriate tab at the top of the page.
Everyone has visibility of everyone elses logbook as a guest but we have purposely limited the 'Guest' users view (hiding the text portion etc) for various reasons.
We would now like to allow certain parties to view certain logbooks in their entirety but with a 'Read Only' view, I see this can be done but only using a common password. (Read password = <encoded password>)
At present we can give others a full view by adding them to the 'Users' list for each individual logbook, this unfortunately also gives them 'write' access. Also if they click on the tab for a logbook that they are not a 'User' for they are logged out of their existing logbook forcing them to have to log back on. If they are designated in a 'Read Only' viewers list for that logbook then their existing password would presumably be read from the global password file and they wouldn't be logged out?
I would like to be able to implement a 'Read' access view for some parties but not have a common password (use the password file?) and not force the other party to re-logon to view the other logbook.
Something like the ability to add a "Read user = <user list>" in each logbook as can be done with 'Login User' and 'Admin User' at present would be great.
Could you let me know if this is feasible please?
Many thanks in advance. |
|