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 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.

Oops, I frogot to document this, thank you for reminding me. You have to add the
"CSV Import" command manually to the list of menu commands, like:

Find menu commands = New, Find, Select, Config, CSV Import, Help

I was wondering if I should make this as the default, but many people maybe do not
have the demand of having CSV Import, so it might be annoying for them. What do
you think?

> 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-

> The only part that does not work is -l "Log Book" the -l variable has to stay as 
> one word. If I submit 2 words (in quotes) it only looks for a logbook of the first 
> word and fails.

I fixed that as well, please obtain the updated version at

http://midas.psi.ch/cgi-bin/cvsweb/elog/src/elog.c?rev=1.20

Let me know if you cannot compile the C file and need an executable.

> > a) Cannot get elog utility to speak to elogd on port 8080. Even though I 
> > use the -p 8080 option with elog. I was able to get it to work when I 
> > moved my server to port 80.
> 
> That problem has been fixed in revision 1.16 from Feb. 19th. Please get the
> newest version from release 2.5.2 issued today.
> 
> > b) I cannot get elog to work with and attributes or logbooks that contain 
> > spaces. Please refer the the following example:
> > 
> > elog -v -h scotland.ccs.yorku.ca -p 80 -a "Station Number"="CC001" -a "Mac 
> > Address"="000874fdc895" -a "Hostname"="cc001.cnscommons.yorku.ca" -a "IP 
> > Address"="10.6.10.52" -a "Manufacturer"="Dell" -a "Model Line"="Optiplex" -
> > a "Model Number"="GX270" -a "Monitor Manufacturer"="Dell" -a "Monitor 
> > Model"="E151FP" -a "Memory"="512MB" -a "CPU Speed"="2.6GHz" -a "Hard 
> > Drive"="40GB" -a "Service Count"="-" -l WSC2 -u charles xxxxx "DD/MM/YY: 
> > Change Description"
> 
> There was also some bug which has been fixed, plus you need following syntax:
> 
> elog -h ... -p 8080 -a "Station Number=CC001" ...
> 
> note the "" are around the whole attribute=value string, not only the attribute.

Steve,

Thank you for the updates!!!

everything works great... -p 8080 and all my attribs get set. 

The only part that does not work is -l "Log Book" the -l variable has to stay as 
one word. If I submit 2 words (in quotes) it only looks for a logbook of the first 
word and fails.

-Charles-

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.

> a) Cannot get elog utility to speak to elogd on port 8080. Even though I 
> use the -p 8080 option with elog. I was able to get it to work when I 
> moved my server to port 80.

That problem has been fixed in revision 1.16 from Feb. 19th. Please get the
newest version from release 2.5.2 issued today.

> b) I cannot get elog to work with and attributes or logbooks that contain 
> spaces. Please refer the the following example:
> 
> elog -v -h scotland.ccs.yorku.ca -p 80 -a "Station Number"="CC001" -a "Mac 
> Address"="000874fdc895" -a "Hostname"="cc001.cnscommons.yorku.ca" -a "IP 
> Address"="10.6.10.52" -a "Manufacturer"="Dell" -a "Model Line"="Optiplex" -
> a "Model Number"="GX270" -a "Monitor Manufacturer"="Dell" -a "Monitor 
> Model"="E151FP" -a "Memory"="512MB" -a "CPU Speed"="2.6GHz" -a "Hard 
> Drive"="40GB" -a "Service Count"="-" -l WSC2 -u charles xxxxx "DD/MM/YY: 
> Change Description"

There was also some bug which has been fixed, plus you need following syntax:

elog -h ... -p 8080 -a "Station Number=CC001" ...

note the "" are around the whole attribute=value string, not only the attribute.

> I am trying to use the Elog Utility to import a few thousand entries. So 
> far I have run into a few problems.
> 
> a) Cannot get elog utility to speak to elogd on port 8080. Even though I 
> use the -p 8080 option with elog. I was able to get it to work when I 
> moved my server to port 80.
> 
> b) I cannot get elog to work with and attributes or logbooks that contain 
> spaces. Please refer the the following example:
> 
> elog -v -h scotland.ccs.yorku.ca -p 80 -a "Station Number"="CC001" -a "Mac 
> Address"="000874fdc895" -a "Hostname"="cc001.cnscommons.yorku.ca" -a "IP 
> Address"="10.6.10.52" -a "Manufacturer"="Dell" -a "Model Line"="Optiplex" -
> a "Model Number"="GX270" -a "Monitor Manufacturer"="Dell" -a "Monitor 
> Model"="E151FP" -a "Memory"="512MB" -a "CPU Speed"="2.6GHz" -a "Hard 
> Drive"="40GB" -a "Service Count"="-" -l WSC2 -u charles xxxxx "DD/MM/YY: 
> Change Description"
> 
> This line executes fine. Except only Hostname, Manufacturer, Memory and 
> text are populated in the record. All the rest of the fields are blank.
> 
> c) the only way I was able to get the transaction to work was by reducing 
> the size of the log book to a single word (ie WSC2).
> 
> Do I have to reduce all my attributes to single words? Or am I missing 
> something simple to use as a delimiter for entry??
> 
> Thanks in advance
> 
> -Charles-

As a followup, this occurs not only in the Linux environment, but also under 
Windows XP. I get the same results...

-Charles-