| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
2183
|
Tue Apr 3 13:17:27 2007 |
 | Yoshio Imai | | Request | Linux | 2.6.4-1795 | Multiple ideas for multiple logbooks |
Hi!
After a long pause, here we are again with a bunch of new ideas (and problems ...;) )
1. Multiple login
Since we are using the elog system now for most aspects of our work, we are more and more often confronted with the need to work with different logbooks open in parallel (e.g. the shift logbook as well as the personal analysis logbook, via tabbed browsing). These logbooks do not always have the same users allowed to access them, so when having logged on to one logbook and then opening another one in a different browser tab, I have to log on as a different user, thereby losing the login on the first logbook. Is there any way to change the cookie structure so as to allow one (physical) user to be logged on as more than one elog user at a time?
2. <Ctrl-T>
While using this logbook (and tabbed browsing), I noticed that the keyboard shortcut <Ctrl-T> now leads to the creation of a table (great thing, btw). However, many of our users are accustomed to this shortcut opening a new browser Tab. Is there any way to disable these elog shortcuts or otherwise disentangle these functions (by using <Alt> instead of <Ctrl> or something similar, since the functionality itself is very good)?
Thanks for any idea on these issues, and thanks for the great software! |
|
2224
|
Fri Apr 27 14:06:34 2007 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | All | SVN 1857+ | How to make a table of contents |
For those people who have not fully understood the discussion of elog:2218, here is an example table of contents.
First Chapter
The table of contents consists of a set of [url] tags like this:
[url=#first]First chapter[/url]
[url=#second]Second chapter[/url]
[url=#thirs]Third chapter[/url]
Then the chapter header contains a tag like this:
[ANCHOR]first[/ANCHOR]
to which the browser ups if you click the corresponding entry in the table of contents.
... empty lines to full up some space ...
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Second chapter
You should jump here if you click on Second chapter at the table of contents.
Third chapter
You should jump here if you click on Third chapter at the table of contents. |
|
2302
|
Fri Aug 3 15:49:05 2007 |
| Grant Jeffcote | grant@jeffcote.org | Question | Windows | 2.6.5-1903 | Boolean |
Stefan,
I've noticed in the latest release when using the 'Find' page that any boolean expression (tick box) is now shown as '0,1 or unspecified'. Is this intentional? My colleagues are finding it hard to get their heads around what to choose and preferred the old 'Tick Box' option. Have there been changes to the configuration arguments used for Boolean that I've missed?
Thanks |
|
65638
|
Fri Oct 26 14:00:48 2007 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | All | 2.7.0 | New ELOG version with HTML Editor |
I'm pleased to announce the release of ELOG version 2.7.0 which contains the HTML editor FCKeditor. This allows the formatting of ELOG entries just as one is used from a word processor. I tried to make all functionality working as one is used from the ELCode system (like replies quote the original text in a yellow text box), but I'm not sure if I covered everything. So if you experience problems with the new editor, please report it and I will try to fix it. Anyhow it is always possible to switch back to the old ELCode encoding.
One warning for site administrators: Since it is possible to enter HTML code directly into a web page, one risks a XSS vulnerability. If someone knows how to protect the FCKeditor against submission of JavaScript, please let me know and I will add it. If this is an issue, you can turn off HTML encoding completely for public ELOG sites with allowed encoding = 3 in elogd.cfg.
Finally I would like to give credits to An Thai who proposed this editor.
|
|
65674
|
Wed Dec 5 13:10:52 2007 |
| Adam Blandford | adamhblandford@hotmail.com | Request | Windows | 2.7.0-1964 | Print Function |
While it is possible to print a logbook using the standard web browser print command in the Full or Summary view, a dedicated print function allowing the user to print out a hardcopy of a particular logbook would be very helpful.
Cheers
Adam
P.S. Thankyou for the response in elog:65671 |
|
65715
|
Mon Jan 28 09:26:26 2008 |
| Stefan Ritt | stefan.ritt@psi.ch | Info | All | 2.7.1 | Update of FCKeditor inside ELOG requires browser cache cleaning |
Between the ELOG versions 2.7.0 and 2.7.1 the internal HTML editor FCKedit has been upgraded from version 2.4.3 to 2.5beta. The new version has a few more options and supports more browsers. People however reported some errors popping up like Unknown toolbar item "ELOGSubmit". This happens because some browsers cache the JavaScript from the old version of the editor in their cache. To fix this problem, simple clear the browser's cache. In Firefox, do a Tools -> Options -> Advanced -> Cache -> Clear now. Other browsers have similar ways to clear the cache. |
|
65740
|
Fri Feb 15 03:16:45 2008 |
| Jeff Stoner | jstoner@opsource.net | Request | Linux | 2.7.2 | move mxml code into elog's src directory |
The mxml source code should be moved into the elog-*/src directory. This requires changing the Makefile to:
MXMLDIR = src/mxml
Reason for change: if you want to build several versions of elog and you unpack the distributions in the same top-level directory, the most recently unpackaged version will overwrite the mxml directory contents, possibly introducing bugs.
|
|
65761
|
Thu Feb 28 19:07:19 2008 |
| Yoshio Imai | | Request | Linux | All | 2.6.5 | #include statements and attachment visibility |
Hi!
First of all, thank you again for the great software and all the support.
Recently, one collaborator here noted that it would be helpful if the preview of attached files could be disabled on a file-by-file basis (via a checkbutton next to the "Upload" button maybe?). This applies e.g. to cases where someone performs a measurement outside of routine operations and attaches the ASCII data file (preview not wanted, in particular if it contains many lines) and the graph representing the evaluation (preview wanted). The disabling should apply to both single-entry view and list view with "Show attachments" option.
Another "fancy" idea of ours would be to allow #include-like statements in the ELOG config file. E.g. if the number of logbooks gets large, people might choose to put old logbooks to an archive disk which is then stored on some shelf. If a user then wants to access these, the disk could be mounted again (say, under /elog-archive). But since we don't know which archive disk has been mounted, and in order to keep the main config file small, the best would be to have the configurations for the logbooks of each disk on the disk itself (say, in a file called additional.config). We could then have a line like#include /elog-archive/additional.config in the main config file. When the elogd is (re)started, it would try to include that file. If it finds none (because no archive disk is mounted) it would silently ignore this. But if it finds such a file, it would include the logbook definitions found therein.
Do you think it is possible (and preferable) to implement this?
Cheers
Y |