| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1760
|
Mon Mar 6 20:51:57 2006 |
 | Glenn Horton-Smith | gahs@phys.ksu.edu | Request | All | 2.6.1-1668 | Provide option to require smileys to be bracketed a la ELCode? |
| Stefan Ritt wrote: |
| Glenn Horton-Smith wrote: | It would be nice if elog would only interpret something as a smiley if it is surrounded by whitespace. It can be particularly annoying that an 8 followed by a right paren becomes a "cool" smiley -- e.g., a parenthetical reference to event eighteen (18) becomes mangled... [That was "18" inside the parens.] ...
|
Interpreting smileys only if they are surrounded by whitespace does not solve the problem completely. It will solve it for (1\8), but not if you have (1, \8) (1, 9) in your text. So it's not a good solution. If you have problems with simleys, I would post my text in plain mode, or surround your numbers with [code]...[/code] tags...
|
Hmm, you're right. But I like EL Code, and I don't want to give it up just because of the smileys! A better solution would be to provide an option, which when set, would require smileys to be in brackets, e.g., [\8)] would become the cool smiley [8)], rendered without surrounding brackets if the option was set.
I actually just spent some time I didn't really have and modified my copy of elogd to see if it could be done and would work as intended. Eureka, it works! The modification implements an option "use bracketed smileys" which, if set to 1, causes the editor smiley bar to insert smileys with the square brackets around them and causes rsputs_elcode() to only substitute for smileys if there are square brackets around them, suppressing the square brackets.
I like this feature. Maybe others would like it too. I have a patch file (diff -cbw) w.r.t. svn version 1663 if you're interested. |
|
1814
|
Wed May 3 00:16:42 2006 |
| Mark Bergman | mark.bergman@uphs.upenn.edu | Request | Linux | 2.6.1 | allow per-logfile attributes to be added/subtracted from the global settings | I think it would be a big enhancement to allow per-logbook attributes to be additions or subtractions from the global attributes, rather than replacing the global settings.
For example, the [global] section of my elogd.cfg reads:
Attributes = Author, Type, Category, Severity, Subject, Entry ID, Status
Extendable Attributes = Type, Category, Severity, Subject, Status
Options Category = Hardware, Software (OS and utilities), Software (Application), Network, Security, Other
Options Severity = None, Low, Medium, High, Critical
Options Status = Open, Closed, In-Progress, Suspended
Options Type = To-Do, Problem Report, Problem Fixed, Informational Note, Software Installation, Configuration, Other
Required Attributes = Type, Category, Subject, Status
I've also got an logbook for each server for hardware issues. Within those logbooks, I'd like to keep all the fields except the software fields, and add fields for memory and storage.
Adding 7 definitions to each server logbook makes the config file huge and difficult to edit, and it means that a future change to the global settings wouldn't propagate to the individual log files. I'd really like to do something like:
[server47]
-Options Category = Software (OS and utilities), Software (Application)
+Options Category = Storage, Memory
-Options Type = Software Installation
+Options Type = RAM Installation, Drive upgrade
As I see it, the initial "-" sign in front of an attribute or option would indicate that the fields listed should be deleted from the global set (if the field name is an exact match), and a leading "+" indicates that the given fields would be added to the global attribute of the same name, for that specific logbook.
The current behavior--without a leading "+" or "-" would be unchanged, so that existing config files don't change.
Thanks,
Mark |
|
1822
|
Sat May 6 02:12:10 2006 |
| Mark Bergman | mark.bergman@uphs.upenn.edu | Request | Linux | 2.6.1 | suggestion for "new user registration" page | I'm testing elog, and one user was having difficulty creating a new account for himself. This problem had three reasons:
1. the user expected a "submit" button or some other way to exit the account registration screen to appear near the password boxes, at the bottom of the page.
2. I'm using the "Bottom text" option, which has a URL to execute a "find" (search) within elog for all open tickets. The user simply entered the info for their new account, and then clicked on the button at the bottom of the page--which would be the expected behavior.
3. In our environment, there are many logbooks (~100), as each computing device has it's own logbook. This isn't a problem on the main page, since the logbooks are grouped into 7 categories. However, the account registration page combines two functions--setting up a new account, and selecting which logbooks to subscribe to for e-mail notification. The logbooks are presented in a list (rather than groups), which causes the "Save" button at the top left to scroll off the screen before the user enters their password.
Suggestions for improving the registration page:
Put a "submit" button after the password entry.
Possibly supress the local "bottom text", or allow the specification of a different file for the registration page.
After the user has registered, then show a page allowing them to subscribe for e-mail notifcation. That page should be organized the same way as the main page, with groups. Users should be allowed to subscribe to entire groups, or to expand each group to select or unsubscribe from individual logbooks.
Thanks,
Mark |
|
1827
|
Wed May 10 16:30:45 2006 |
| Kevin McCarty | kmccarty@princeton.edu | Request | All | 2.6.1 | Feature request - site-specific ELCode markup definitions | Hi,
Here's a suggestion that you may or may not want to apply. It would be nice if there existed a config file (or a syntax in the existing elog.cfg file) that permitted sites to define their own ELCode patterns.
Let me give you a usage case. I thought it would be nice to have LaTeX expressions show up automatically on my group's ELog installation if they entered them like this: [math]x^2 + y^2 = r_0^2[/math] So in the source code file elogd.c, I hacked in the following additions to the definition of pattern_list[]:
{"[math]", "<img src = \"http://borex.princeton.edu/mimetex?"},
{"[/math]", "\" border = \"0\" align = \"absmiddle\" />"},
and recompiled ELog.
What this does is convert the LaTeX expression into a URL that uses the "mimetex" CGI program installed on my server to output a GIF file of the equation. So my users can have inline math expressions in their log entries, like this:  . Obviously this is far too site-specific to be added to the official ELog code (unless you want to embed mimetex code into the server, which I kind of doubt  ). But it would be nice if I could specify these patterns in a config file without having to edit the source code and recompile each time I want to install a new ELog version!
Presumably others could find a use for site-specific ELCode markup too (logos, custom smilies, etc.)
Thanks for your time. |
|
1840
|
Thu May 25 19:41:51 2006 |
| Mark Bergman | mark.bergman@uphs.upenn.edu | Request | Linux | 2.6.1 | add field type to automatically email CC | I've got logbooks where I'm submitting entries on behalf of other users, or where other people should be notified of the ticket. This isn't a fixed list of people, and shouldn't be hard-coded into a config file. I've got a field to enter the user's e-mail address, but there's no action associated with that data.
I'd like to see a new field type that allows the entry of e-mail addresses, where each addresses supplied with the logfile entry would be automatically "CC'ed" in the notification e-mail. Ideally, people on the CC list would be (optionally) CC'ed when there are replies or edits to the original elog entry.
For example (snippet of fictional elogd.cfg):
-------------------------------
[web site]
Welcome Title = Issues regarding the web site
MOptions Category = Add links, Change content, Broken Link, Other
CCMailTo = Notification List
Attributes = Author, Category, Severity, Subject, Entry ID, Status, User, Login
Extendable Attributes = Category, Severity, Subject, Status, User, Login, Notification List
Required Attributes = Category, Subject, Status, User
------------------------------- |
|
1908
|
Tue Aug 22 10:41:42 2006 |
| Ben Shepherd | bjs54'at'dl.ac.uk | Request | Linux | Windows | 2.6.2-1714 | Append option for elog.exe | Hi,
Would it be possible to add an 'append' option to the elog.exe client program? I would like to be able to write a simple script for adding images into a logbook - i.e. right-click in Windows and click 'add to log', or click a button in LabVIEW or Matlab and have an image immediately added to the last log entry. There would also have to be an option to either return a list of entry IDs, or just append to the last entry. Is this possible/likely?
cheers
ben |
|
1972
|
Tue Oct 10 15:32:21 2006 |
| Ben Shepherd | bjs54@dl.ac.uk | Request | All | 2.6.2-1714 | 'Inline' button for attachments | Hi,
It would be good if when you uploaded an image as an attachment, there was a button next to it that pasted the code [img]elog:1972/1[/img] into the log entry. This way, it would be more easy to have inline images in a log entry.
cheers
ben |
|
1983
|
Wed Oct 11 19:37:10 2006 |
| Gregory M. Caughey | caugheygm@aol.com | Bug report | Windows | 2.6.2-1722 | Re: Elog v2.6.2-1722 appears to have broken "Suppress default [0|1|2|3]" option on Windows XP box |
| Stefan Ritt wrote: |
| Gregory M. Caughey wrote: | | 2.) However, email notifications will be sent under all circumstances regardless of which parameter selected. |
Thanks for reporting that problem. I just implemented Suppress email on edit and this could have had some side effect. I tried however to reproduce your problem and was not able to. Trying the "minimal" configuration file, the email notifications were suppressed if the check box was checked, or if Suppress default = 3. Can you check if it works with a minimal config file, and if yes, what option in your "full" config file causes this effect? |
OK, you're absolutely correct. When I run Elog-2.6.2-1722 with a minimal 'elogd.cfg' the "Suppress default [0|1|2|3]" flag does appear to behave as expected. Taking your advice I went through my local 'elogd.cfg' evaluating items to see where the problem starts and I found a problem. In my local config file I use conditional attributes to modify the "category" and "type" fields (in the posting form) and here is what I'm finding wrong. For this example I have set "Suppress default = 3" and the following actions take place:
1.) Select "New" to begin a post and the form displays correctly with NO "[] Suppress Email notification" checkbox showing.
2.) When selecting "Category" an choosing an appropriate menu item the form is then redrawn and now there is a problem, the "[] Suppress Email notification" checkbox is displaying. The checkbox does work correctly but the behavior I'm expecting is for no checkbox to display during the composition of this posting. Am I misunderstanding the behavior of the "Suppress default = 3" flag?
3.) Each of the other flag parameters appear to work as expected as used in the above example.
I have attached screenshots that demonstrate this behavior as well as a snippet of the 'elogd.cfg' file.
Hope this helps a little...
Thanks, Greg |
| Attachment 1: Capture10-11-2006-5.05.21_AM.jpg
|
|
| Attachment 2: Capture10-11-2006-5.06.40_AM.jpg
|
|
| Attachment 3: Capture10-11-2006-5.09.34_AM.jpg
|
|
|