| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
1556
|
Tue Dec 20 11:17:17 2005 |
 | Stefan Ritt | stefan.ritt@psi.ch | Info | | 2.6.0 | Howto insert screen dumps into an elog entry | With the new ELCode tags, one can insert screen dumps pretty easy into elog entries. I personally use HoverSnap 0.8 under Windows, there are similar tools under Linux. HoverSnap puts a "Capture.jpg" file in a selectable directoy when you press PrintScreen, then you can instert this file with the  button. Here is such a screendump example:
 |
|
1624
|
Tue Jan 24 14:43:19 2006 |
| T. Ribbrock | emgaron@gmx.net | Request | Linux | 2.6.1 | Suggestion additional ElCodes | I have to say, now that I'm finally on 2.6.x, I grew really fond of the ElCode stuff - great addition! It saves a lot of straight HTML typing for me... THANKS!
However, there are two things I'm missing:
- Headings
It would be great to have a range of , , ... tags that map directly to their HTML counterparts (and have buttons, of course...  ). That makes structuring an entry much easier in my opinion (and the output is easier to deal with for tools like html2ps) and I'm really missing those.
- Tables
This one is probably more difficult to add, but support for simple tables would be enough. But this is more a "nice to have"...
|
|
1738
|
Wed Mar 1 12:27:36 2006 |
| Holger Mundhahs | holger.mundhahs@vtg-rail.com | Question | Windows | 2.6.1-1653 | [SOLVED] Re: list view mode remembert - Bug? | > > As default http://<hostname>/<LOGBOOK> shows the Summary View.
> > Clicking in "Full" changes the URL to http://<hostname>/<LOGBOOK>/?mode=full.
> > But now the URL http://<hostname>/<LOGBOOK> show the Full view as default.
> > I think the URL without ?mode=... should show every time the same result,
> > regardless the view used before. Or maybe I can configure, which view I want to
> > see if I use the URL w/o ?mode=... The option to hide/show attachments is affected too.
>
> Sure, that's a feature :D
>
> It was requested by several people that the view mode is stored in a cookie. So if you switch modes, it should be
> persistent. If I now add additional default flags, people will have hard time to understand what this is all
> about, since there might then be conflicting settings between the flags and the cookies. So for what exact purpose
> do you want what you requested? Why does it bother you that you have to click "Summary" again to get the summary
> view? Of course you can delete the local cookies and get the default behaviour (they are named [b]elmode[/b] and
> [b]elattach[/b]), but that might be a bit cumbersome.
Thank you for your explanation. My situation was, that I've played around with "Mode commands = 0". In normal case I
use the Summary view, but on one logbook I've changed it to Full before, and after setting the parameter I can't
revert it to Summary. But now I know how it works and can use it like intended.
Regards
Holger |
|
1746
|
Sat Mar 4 05:17:14 2006 |
| Glenn Horton-Smith | gahs@phys.ksu.edu | Request | All | 2.6.1-1668 | require smileys to have whitespace on either side? | 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.]
Is there already a way to solve this issue (other than always previewing your entries and adding spaces before parans)? Is the feature hard to implement? |
|
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. |
|