I must have misunderstood what you meant. That aside, I don't know how to compile 
the elogd.c so any help would be appreciated. I would like to learn how to also.
Thanks.

> > I even upgraded to the 2.5.1 version. Then I placed the elogd.c in the SRC 
> > folder. Also placed the images in the themes folder.
> 
> As I wrote, you have to get the latest elogd.c, revision 1.272 and *COMPILE* it 
> (or wait for the next official release). If you cannot compile elogd.c, let me 
> know and I can send you the executable.

> Run into the same error on a windows XP & 2000 machine. Totally shuts down the elogd.exe 
> when THREADED is selected. Have not tried your modified version after reading the posted 
> results. Will run with summary view until fixed. Wish I could help but I'm not a 
> programmer. Let me know if you want to test any new elogd.exe's.

This problem has been fixed now, it was a programming bug. New version under

http://midas.psi.ch/elog/download/windows/elogd.exe

The elog daemon uses cascading style sheets (CSS) to format its output, such
as font family, size and color. Some people started to develop new themes
(skins) and posted them at the contributions logbook (such as
http://midas.psi.ch/elogs/Contributions/7).

From my onw experience, I know that this can be a difficult job, since it
means to change the "default.css" file and reloading a page over and over
again. I recently discovered a way to do this much easier: The Mozilla based
browsers (such as firefox, http://www.mozilla.org/products/firefox/) have an
extension called EditCSS (http://texturizer.net/firefox/extensions/#editcss)
which shows the CSS file on the left side of the browser and the web page on
the right side. Changes in the CSS editor are immediately reflected in the
browser window. This way one can change certain entries in the CSS file and
immediately see its consequences. Development of new skins should therefore
become much more easier.

It is not usual for me to pester people with tips around elog, but this
one was so helpful for me that I would like to share it.

The Mozilla based browsers, such as Netscape or Firefox
(http://www.mozilla.org/products/firefox/) offer the possibility of
so-called "keymarks" or "bookmark keywords". This are bookmarks to which a
keywork can be added, making them a very powerful search tool for elog. This
can be explained most easily in an example:

Add following bookmark to your Browser:

Name: ELOG search
Location: http://midas.psi.ch/elogs/forum/?mode=full&sall=1&subtext=%s
Keyword: el

I attached a screendump of how this looks under Firefox. Now you can type

el <keyword>

in your URL address bar, and the elog forum is automatically searched for
that keyword (see second attachment), since the "%s" in the URL is
automatically replaced with your keyword. This works of course also with
your personal logbooks. The switch "sall=1" causes elog to search for the
string in the main text body and in all attributes.

The URL bar can be activated with CTRL-L, so the key sequence

CTRL-L el <keyword>

is all you need to search a ELOG logbook, even without touching the mouse.

Version 2.5.2 of ELOG has been released today. It contains CSV (comma
separated values) import and export, as well as XML export (through the
"Find" page). Since these features are new, I would appreciate some feedback
on how this works in different environments. I made sure I can import data
from Excel and Outlook (like my address book), but I have no experience with
other applications.

As with the XML export, I'm not sure if the format I chose is a good one.
People working more with XML should tell me if it should be changed.

> Version 2.5.2 of ELOG has been released today. It contains CSV (comma
> separated values) import and export, as well as XML export (through the
> "Find" page). Since these features are new, I would appreciate some feedback
> on how this works in different environments. I made sure I can import data
> from Excel and Outlook (like my address book), but I have no experience with
> other applications.
> 
> As with the XML export, I'm not sure if the format I chose is a good one.
> People working more with XML should tell me if it should be changed.

I was able to find the export feature under find. Could you let me know where 
the import feature is? Or how I turn it on.

-Charles-

I develop multiple client server apps and web apps deployed on intranets. I
need my users to send me bugs with screenshots attached.

So I'm interested in auto opening a new elog page in an embedded browser and
automatically doing an attachment. I've seen a couple messages about
recently added Javascript hooks (message 465). The message specified a URL
that would fire off javascript(http://localhost/demo/?cmd=New&js=test.js).
Now apparently that wasn't fully working or at least you couldn't bring up
multiple alerts. Has that been fixed, or is it just a problem with alerts?
Can I write a url that has my attributes, plus a short js script that just
adds an attachment?

Anyhow, any info on where this functionality is would be appreciated. I'm
going back to my mgmt for signoff on using this, and if I get it (fairly
high probability), then I'll have a coder start implementing it. :-)

BTW, great tool! Very clean design.

Cheers,
Robin

I implemented the feature to import the main entry text body from a CSV column labeled
"text". Please see the newest release
(http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elogd.c?rev=1.319) and let me know if this
works for you.

I had to add code to break apart long text bodies after 78 characters in order not to
get too long lines. Please note that the maximum body size in the CSV import is limited
to 500 characters.