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:

1. moved the journal entry content and footer line (elog version info) out of the layout table structure, into their own div sections;
2. in the style sheet, added attribute "position:fixed" to the "frame table" section;
3. in the style sheet, added attribute sections for journal entry content and footer div sections:
   1. #content: overflow:auto;position:fixed;top:230px;bottom:30px;width:100%;
   2. #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

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

We had already some time ago a request to integrate mimetex (elog:1827). I will see what I can do there.

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

At the moment no support for a Web Service is planned.

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.

Unfortunately no.

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?