| ID |
Date |
Icon |
Author |
Author Email |
Category |
OS |
ELOG Version |
Subject |
|
2189
|
Tue Apr 3 22:10:56 2007 |
 | Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.6.4-1826 | Re: Multiple ideas for multiple logbooks |
| Yoshio Imai wrote: | BTW, there are (of course  ) two other issues. They are still present in -1826
- one bug was reported by a logbook user: when using the "find" function in a logbook, and selecting one value from the "Author" drop-down list and another from the "Category" drop-down list, the elogd reports no entries found, but when specifying only the "Author" and leaving "Category" blank, many entries are found, including those with the "Category" being looked for. When specifying only the "Category" and leaving the "Author" blank, the elogd also reports no entries found. Has anyone reported a similar behaviour? |
I tried to reproduce this, but without success. I made a very simple config file like:
Attributes = Author, Type, Category, Subject
Options Type = Routine, Software Installation, Problem Fixed, Configuration, Other
Options Category = General, Hardware, Software, Network, Other
Quick filter = Type, Category
And produced some entries with various attribute values. But when selecting them from the quick filter, or selecting them from the find page, both gave correct results. Maybe you used a userlist attribute for the author? |
|
2188
|
Tue Apr 3 21:09:47 2007 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | Linux | 2.6.4-1826 | Re: Multiple ideas for multiple logbooks |
| Yoshio Imai wrote: | | When using the shortcuts and/or the ELCode buttons, sometimes the code is generated and the cursor in between the [XX] and [/XX] directive, but sometimes, the whole code directive is selected as if for editing |
I found at least that problem. If you select one or more words and press CTRL-B for example, your selection is surrounded by the [B]...[/B] tags. If you double click with your mouse on a word, usually the space between this word and the next word is selected as well. I modified the code such that if there is a blank at the end of a selection, it gets stipped off before placing the tags. This had the side-effect that if there was no selection at all, you got the reported mis-behaviour if there was a blank at your cursor position. I fixed that now in the updated elcode.js.
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. |
|
2187
|
Tue Apr 3 17:55:21 2007 |
 | Yoshio Imai | | Bug report | Linux | 2.6.4-1826 | Re: Multiple ideas for multiple logbooks |
| Stefan Ritt wrote: | | 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. |
You should really have told me  . Actually, I found out about the <Ctrl-C> issue while using this logbook.
| Stefan Ritt wrote: | | So get the SVN update, and let me know what you think |
Did so, we are running now -1826. I think it is very usable, with maybe one exception (this might be a browser issue, however): When using the shortcuts and/or the ELCode buttons, sometimes the code is generated and the cursor in between the [XX] and [/XX] directive, but sometimes, the whole code directive is selected as if for editing
which prevents from immediately continuing to type (which, I guess, was the idea behind the shortcuts). The behaviour is not completely reproducible, and I have even seen it change during one and the same browser (=firefox) session while working on the same entry (*). I also had it once that the browser out of a sudden completely ignored the ELCode meaning, and instead used <Ctrl-I> for page info and <Ctrl-B> for the history.
(*) It just happened again!
BTW, there are (of course ) two other issues. They are still present in -1826
- one bug was reported by a logbook user: when using the "find" function in a logbook, and selecting one value from the "Author" drop-down list and another from the "Category" drop-down list, the elogd reports no entries found, but when specifying only the "Author" and leaving "Category" blank, many entries are found, including those with the "Category" being looked for. When specifying only the "Category" and leaving the "Author" blank, the elogd also reports no entries found. Has anyone reported a similar behaviour?
- We have one logbook top group for the beamtimes. Under certain conditions, a preset text is to be displayed.
{2&a} Preset Text = resource/text_1.txt
{2&b} Preset Text = resource/text_2.txt
However, the definitions of these conditions have to be repeated for every logbook in the group (putting it only under [global beamtimes] doesn't do it), otherwise they are ignored.
Any idea on these? |
|
2186
|
Tue Apr 3 17:16:23 2007 |
| Stefan Ritt | stefan.ritt@psi.ch | Bug report | All | Other | 2.6.2-1739 | Re: "Guest menu commands" not changing the menu line |
| Steve Jones wrote: | BTW, WebSVN no longer provides a means of downloading a tar of your code trunk. I had to go to http://midas.psi.ch/elog/download/tar/ in order to get your 2.6.4-1 revision.
|
That should be fixed now.
| Steve Jones wrote: | Ok, here is what I found. Apparently in the past there was a "Find Menu Commands = " option? Because I had this in my config and elog was not barfing on it being there. So, I changed the word "Find" with "List" and things seems to now work. Stefan, was there an old command called "Find Menu Commands"?
|
Yes. Indeed this was changes some time ago. Have a look at elog:880. Unfortunately I did not announce this change clearly. |
|
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. |
|
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. |
|
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! |
|
2182
|
Fri Mar 30 16:42:35 2007 |
| Steve Jones | steve.jones@freescale.com | Bug report | All | Other | 2.6.2-1739 | Re: "Guest menu commands" not changing the menu line |
| Steve Jones wrote: |
| Stefan Ritt wrote: |
| Steve Jones wrote: | | Am I doing something wrong or was this a problem in the past? |
I can't remember any problem of that type.
| Steve Jones wrote: | | Suggestions on where to look? Start from scratch? |
Might not be a bad idea. Use the little config file from the distribution, then just add the guest menu lines, and try it. If it works, modify it gradually until it equals to your full config file, to see where the problem is. Stupid quiestion: After you added your guest menu, did you log out to become a "guest"? If you are logged in with your user name (stored in a cookie), you never will see the guest menu. |
| Quote: |
To answer your last question - yes, i logged out and the menu line never changed. I even put it into debug mode but the output reflects exactly what I see -- a non-changing menu line. I'll start with the simple config and see what happens.
BTW, WebSVN no longer provides a means of downloading a tar of your code trunk. I had to go to http://midas.psi.ch/elog/download/tar/ in order to get your 2.6.4-1 revision.
|
|
| Quote: |
Ok, here is what I found. Apparently in the past there was a "Find Menu Commands = " option? Because I had this in my config and elog was not barfing on it being there. So, I changed the word "Find" with "List" and things seems to now work. Stefan, was there an old command called "Find Menu Commands"?
|
|
|