Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 721 of 808  Not logged in ELOG logo
ID Date Icondown Author Author Email Category OS ELOG Version Subject
  65740   Fri Feb 15 03:16:45 2008 Idea Jeff Stonerjstoner@opsource.netRequestLinux2.7.2move mxml code into elog's src directory

The mxml source code should be moved into the elog-*/src directory. This requires changing the Makefile to:

MXMLDIR = src/mxml

Reason for change: if you want to build several versions of elog and you unpack the distributions in the same top-level directory, the most recently unpackaged version will overwrite the mxml directory contents, possibly introducing bugs.

 

  65761   Thu Feb 28 19:07:19 2008 Idea Yoshio ImaiRequestLinux | All2.6.5#include statements and attachment visibility
Hi!

First of all, thank you again for the great software and all the support.

Recently, one collaborator here noted that it would be helpful if the preview of attached files could be disabled on a file-by-file basis (via a checkbutton next to the "Upload" button maybe?). This applies e.g. to cases where someone performs a measurement outside of routine operations and attaches the ASCII data file (preview not wanted, in particular if it contains many lines) and the graph representing the evaluation (preview wanted). The disabling should apply to both single-entry view and list view with "Show attachments" option.


Another "fancy" idea of ours would be to allow #include-like statements in the ELOG config file. E.g. if the number of logbooks gets large, people might choose to put old logbooks to an archive disk which is then stored on some shelf. If a user then wants to access these, the disk could be mounted again (say, under /elog-archive). But since we don't know which archive disk has been mounted, and in order to keep the main config file small, the best would be to have the configurations for the logbooks of each disk on the disk itself (say, in a file called additional.config). We could then have a line like
#include /elog-archive/additional.config
in the main config file. When the elogd is (re)started, it would try to include that file. If it finds none (because no archive disk is mounted) it would silently ignore this. But if it finds such a file, it would include the logbook definitions found therein.


Do you think it is possible (and preferable) to implement this?

Cheers

Y
  65799   Tue Apr 1 02:04:35 2008 Idea Dennis Seitzdseitz@berkeley.eduRequestAll 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 Idea Dennis Seitzdseitz@berkeley.eduRequestAll 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 Idea Arno TeunisseA.teeling3@chello.nlInfoWindows 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 Idea Willem KosterW.Koster@rug.nlRequest  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 Idea Jochen Krempelkrempel(at)ill.frRequestAll2.7.3LaTeX 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 Idea Bill Pierbpier@clove.orgQuestionAll2.7.3Re: 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:

  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

ELOG V3.1.5-3fb85fa6