ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
517
|
Wed Mar 31 04:22:57 2004 |
| Robin Peterson | robin.h.peterson@state.or.us | Info | Windows | 2.5.2 | Using Javascript files |
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 |
533
|
Sat May 1 00:21:20 2004 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | Other | 2.5.2 | Re: CSV importing |
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. |
579
|
Fri Jul 9 19:17:03 2004 |
| Ulrich Trüssel | ulrich.truessel@familienhund.ch | Request | All | 2.5.3 | Re: Formatting parameters for attributes |
Thank you Stefan! Just was out of the office for some days.
There ar 2 questions in addition:
1. Is there a possiblity to fix the position of the attribut fields if they are in
the same line? As. ex. if one attribute is empty or contain a very short value it may
be possible that the position of the following atrributes in the line are moving to
the left, if the value is very long, they move to the right side. This make it
sometime not easy to read the informations, specially if the user browses trough some
entries, the picture the eyes are scanning is changing.
2. Did I understand you right, that tis will not work while editing? I would like to
put this to the wish list for a uppcoming version (not very importand, but VERY nice
to have), that it may be possible to use Format in the new and edit mode too, because
it is somtimes more comfortable to have some attributes grouped locically in one line
or to have a overview over all attributes on one screen without scrolling while editing.
ELOG has e very big flexibility and I'm amazed how fast and stable it's running under
Linu xas well as under Windows! - I love it! :-)
Ueli
> > I have some problems of understanding how the "Format <attribute>" parameter
> > is working. It may be, that there was a similar question in the forum, but I
> > didn't find it. I'm sorry if I come back with an old question.
> >
> > I would like to have 2two attributes in the same line. As ex. PersonName,
> > PersonCity.
> >
> > If I understand the handbook correctly, it should be posslible with "Format
> > <attribute> = 1". However, I'm not able to use the "Format <attribute>"
> > correctly because I do not understand how to use it correctly in the cfg file.
> >
> > Is there a possibilty of an example by Stafan or does anybody else already
> > use this feature successfuly and is able to post a example here?
>
> This forum uses that feature. As you can see, if you display a single entry, the
> author, subject etc. are on a single line. This is achieved with
>
> Format Author = 1
> Format Author email = 1
> Format Category = 1
> Format OS = 1
> Format ELOG Version = 1
>
> Note that in the entry form, each attribute is on a separate line no matter what
> the format specifiers are. The single line option only works for the display page. |
596
|
Wed Jul 14 13:58:26 2004 |
| Bartjan Wattel | watt0006@mail.hzeeland.nl | Request | Linux | Windows | 2.5.3. | Request: limit size of attachments |
hi again,
we have been doing a bit of stress testing for Elog. The most important
thing we found is that Elog stops responding when a user uploads a large
attachment (we used a 240 Mb attachment).
Is it possible to add a flag in the configuration file, to specify the
maximum size of an attachment?
Bartjan Wattel |
600
|
Wed Jul 14 21:47:47 2004 |
| Steve Jones | steve.jones@freescale.com | Request | All | 2.5.3 | Wishlist: TOOLTIP for ATTRIBUTES |
Using the COMMENT feature to add guidance to an ATTRIBUTE works great, but
is it possible to add a TOOLTIP <ATTRIBUTE> = so as to save screen space?
For a complex entry form it is desireable to try and have everything in a
single window and this, I think, would help.
Thanks |
601
|
Wed Jul 14 21:53:02 2004 |
| Stefan Ritt | stefan.ritt@psi.ch | Question | All | 2.5.3 | Re: Question on how "Format <attribute> = " works |
Just have a look at elog:571 which should answer your question. Also look at
elog:Config+Examples/4 which is the configuration of this Forum (which as you can
see has all attributes in a single line, even using different fonts). |
605
|
Wed Jul 14 22:59:05 2004 |
| Steve Jones | steve.jones@freescale.com | Question | All | 2.5.3 | Re: Question on how "Format <attribute> = " works |
> Just have a look at elog:571 which should answer your question. Also look at
> elog:Config+Examples/4 which is the configuration of this Forum (which as you can
> see has all attributes in a single line, even using different fonts).
Ok, I think I see now. I was assuming it applied to the entry form as well.
Thanks! |
614
|
Fri Jul 16 17:51:52 2004 |
| Steve Jones | steve.jones@freescale.com | Request | All | 2.5.3 | WISHLIST: Type <attribute> = user |
Something to add to the wishlist:
- Type <attribute> = user
This would define an attribute as being of the type "user" which is a list
of login id's as defined in a password file or on the "Login user =" line.
In a dataentry form the presence of this ATTRIBUTE would result in a
picklist of loginid's and/or fullnames. |