| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
2177
|
Tue Mar 27 13:57:44 2007 |
 | Fergus Lynch | flynch@alternativenetworks.com | Request | Windows | ELOG V2.6. | Re: Global "MOptions" |
| Stefan Ritt wrote: |
| Fergus Lynch wrote: | | Would it be an option to have Global "MOptions" - perhaps configured in the 'global options' file - which can be called up and referenced in all logbooks? |
Sure, that's possible already with the current version. Just put your MOptions statement under [global] and it will be used in all logbooks. If a specific logbook uses different MOptions, put the a second MOptions list under that logbook's section and it will overwrite the global setting. |
Perfect! Works a treat (I promise to read the manual next time!)
Cheers
Fergus |
|
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! |
|
2184
|
Tue Apr 3 14:26:09 2007 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Linux | 2.6.4-1795 | Re: Multiple ideas for multiple logbooks |
| Yoshio Imai wrote: | | 1. Multiple login |
Well, restructuring the cookies would be rather work intensive. Right now we have one user name cookie unm
used for all logbooks. To distinguish betwen logbooks, one would need cookies in the form <logbook name>_unm and <logbook name>_upwd. Let me think about.
| Yoshio Imai wrote: | | 2. <Ctrl-T> |
Well, you didn't realize, but you were my beta-tester for the keyboard shortcuts  . I didn't yet publish it, so you must have gotten this brand new feature from SVN. I'm still fine-tuning shortcuts. I realized that CTRL-C which I used for CODE is normally used for Copy/Paste, so I changed that already to CTRL-O to free up CTRL-C. Since tables are not so often used, I removed it now completely. There is also CTRL-P for Preview and CTRL-ENTER for Submit. While this works now nice on Mozilla based browsers, I cannot intercept CTRL keys on IE. I know you and I don't care, but many people unfortunately do. So get the SVN update, and let me know what you think, if there is still something to be modified before I make the official release. |
|
2185
|
Tue Apr 3 15:19:00 2007 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Linux | 2.6.4-1795 | Re: Multiple ideas for multiple logbooks |
| Stefan Ritt wrote: | | To distinguish betwen logbooks, one would need cookies in the form <logbook name>_unm and <logbook name>_upwd. |
Actually this is not a good idea. Most people I know have several logbooks, but a common password file. Access control is then fine-tuned via 'Login user = ...'. Now if I implement a per-logbook cookie, these people would have to log in once for each logbook. If the go to a new browser which does not contain their old cookies, or if the cookies expire, they would have to log in again once for each logbook. On installations with 20 and more logbooks this can be cumbersome. So all these people would complain. |
|
2190
|
Wed Apr 4 08:38:30 2007 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Linux | 2.6.4-1795 | Re: Multiple ideas for multiple logbooks |
| Yoshio Imai wrote: | 1. Multiple login
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? |
Actually there is a way, but I completely forgot about that. The manual says:
| ELOG manual wrote: |
If any of the password statements are in the [global] area of the configuration files, they are used for all logbooks. If one logs in at one logbook, access is automaticlly granted to all logbooks. If the password statements are in the individual logbook sections, one has to log in to each logbook separately. |
That should help. Just put the password file = ... into the individual logbook sections, and you should get what you want. You can check this by inspecting the cookies (first you have to delete all cookies in your browser). With passoword files for individual logbooks you should see an associated Path for each logbook, so the login cookie only gets submitted to that logbook, allowing differnt user names/passwords for different logbooks. |
|
2191
|
Wed Apr 4 11:37:56 2007 |
 | Yoshio Imai | | Request | Linux | 2.6.4-1795 | Re: Multiple ideas for multiple logbooks |
| Stefan Ritt wrote: | | Actually there is a way |
... and it works! Thank you!
| Stefan Ritt wrote: | | I fixed that now in the updated elcode.js. |
That works now, too!
| Stefan Ritt wrote: | | Your other problem of ignoring the control keys at all I could not reproduce. Try to reproduce it in a well-defined way and let me know. |
I will try to do that (new beamtime, new occasions ...  ).
| Stefan Ritt wrote: | | Maybe you used a userlist attribute for the author? |
No, I didn't. I will try to investigate this further and let you know if I find anything.
So for the moment ... thanks for the help! |
|
2218
|
Thu Apr 26 16:43:45 2007 |
 | Kevin McCarty | kmccarty@princeton.edu | Request | Linux | 2.6.3-1764 | Is there (planned) support for <A NAME> and <HR /> in ELCODE? |
Hello,
I am wondering if there is any support (or if not, if it is planned) for inserting HTML <a name> and <hr /> tags via ELCODE. This would be useful for long log messages in order to provide a table of contents and divide them into clear sections. If this support already exists, I'm afraid it is not obvious to me how to access it in ELCODE. If it does not yet exist, would you consider a patch for it?
As a related issue, to support <a name> usefully, it will also be necessary for ELCODE to support things like [url=#tag], which it currently converts to <a href = "http:///#tag"> instead the expected result of <a href = "#tag">.
(Please send me replies also by email at kmccarty AT princeton DOT edu, as I don't check this forum often.)
Thanks for writing ELOG; our group has been using it very productively on our server for the last few weeks.
best regards,
-- Kevin McCarty |
|
2221
|
Fri Apr 27 08:38:58 2007 |
| Stefan Ritt | stefan.ritt@psi.ch | Request | Linux | 2.6.3-1764 | Re: Is there (planned) support for <A NAME> and <HR /> in ELCODE? |
| Kevin McCarty wrote: | | I am wondering if there is any support (or if not, if it is planned) for inserting HTML <a name> and <hr /> tags via ELCODE. |
Very good idea. The horizontal line
is already implemented via [LINE] and the anchor tag will soon follow. |