Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 698 of 806  Not logged in ELOG logo
 Find |  Login |  Help 
 Full | Summary | Threaded | Show attachments  Show only new entries    6445 Entries 
Goto page Previous  1, 2, 3 ... 697, 698, 699 ... 804, 805, 806   Next  
ID Date Icon Author Author Email Category OSdown ELOG Version Subject
  66839   Tue Jun 8 09:53:09 2010 Reply Stefan Rittstefan.ritt@psi.chRequestAll2.7.7Re: alphabetize Quick Filter items?

Dennis Seitz wrote:

Stefan Ritt wrote:

Dennis Seitz wrote:

Stefan Ritt wrote:

Dennis Seitz wrote:

 Hi Stefan,

I'd like to request a feature: automatic alphabetization of the items in the Quick Filter menus.

We track quite a few detector assemblies, which are produced with non-sequential designations. It would be useful if the Quick Filter list was automatically sorted alphabetically to make it more convenient for folks to find a particular item.

I know people can always search by designation but it would be handy to have this alpha sorting feature. Would it be possible to include that in a future release?

Thanks again for a *very* useful logging system!

Dennis

The order of items in a Quick Filter menu is exactly as in the configuration file. Like if you have items

Options Type = C, D, A, B

they are shown like that in the quick filter menu. If you want to sort them, just do the sorting yourself in the configuration file like

Options Type = A, B, C, D

I have not implemented automatic sorting since some people want a different order, like some main topics at top. So by following the order from the configuration file, everybody can be satisfied just by chaning the order in the config file.

- Stefan 

 Yes, I have been manually sorting and resorting. We have extendable attributes and the list keeps growing so I have to resort every so often. I thought perhaps a simple alphanumeric sort as an option would be popular with most users so I thought I'd ask for it. It would really simplify things for me. Users who want to sort manually could do so by disabling the option. It never hurts to ask!

 

Ok, I implemented

Sort attribute options = 1

in the current SVN revision. 

 I've tried adding this statement to my cfg file but the attributes are still unsorted in the QuickFilter menus. Was this implemented in 2.7.7?

Shouldn't an existing configuration file entry like
Options Type = C, D, A, B
be sorted in the QuickFilter menu as A B C D?

You need revision 2252 or later. So you have to upgrade to 2.7.8. 

  66841   Tue Jun 8 15:48:06 2010 Question Yoshio ImaiRequestAll2.7.8inline-code
Hi, Stefan!

Sometimes, it is annoying that the 
[code]
-Tag creates a line break, because there are situations where verbatim text inside the regular text flow is desirable (just like here). I would like to request an additional elcode-tag 
[ilcode]
(in-line code) which translates to 
<code>
instead of 
<pre>
.

Cheers

Yoshio
  66842   Tue Jun 8 16:33:07 2010 Reply Stefan Rittstefan.ritt@psi.chRequestAll2.7.8Re: inline-code

Yoshio Imai wrote:
Sometimes, it is annoying that the 
[code]
-Tag creates a line break, because there are situations where verbatim text inside the regular text flow is desirable (just like here). I would like to request an additional elcode-tag 
[ilcode]
(in-line code) which translates to 
<code>
instead of 
<pre>
.

Yoshio


The [code] tags produce <pre>...</pre> tags for multi-line listings, where several spaces should not be dropped to keep the formatting of some source code for example. I also want it sometimes in a single line, so what I do is to use a [FONT=Courier New] tag, which produces output very similar to <code>, but without line breaks.
  66854   Thu Jul 22 00:31:54 2010 Question David McKeedmckee@phys.ksu.eduQuestionAll2.7What *exactly* do "clone" and "mirror" do?

We have been hosting logbook far (geographically and in internet hops) from our experimental site. Recently we have (finally!) gotten reliable on-site internet, and would like to host the log book on-site.

I have a suspicion that some combination of the -C, -m, and -M flags will allow me to migrate the logbook automagically and with a minimum risk of trouble from concurrent operation on the logbook, and to maintain the existing version as a mirror of the new official on-site version. But documentation is not being very helpful. Can someone say a few more words about what these options do?

 

I've been experimenting as I compose this and have a suggestion for language that might be useful somewhere in the documentation:

In this context "to clone" means to copy the configuration file and all data files associated with a log book so that I can host an identical logbook on a new host (that is this is the command to migrate a logbook).  After cloning the two installation are identical, but no effort is made to keep them so: if you continue to run both copies post made to one will not be reflected in the other.

Is this correct?

I'm still not clear on what the -m and -M options do.

  66859   Tue Jul 27 10:46:27 2010 Warning Johan Schuringjohan.schuring@getronics.comQuestionAll2.7.5Mail when elog entry is expired

Hi,

 

Is it possible to set a timestamp on an elog entry say for about 5 days in the future, when it is expired and there are no modifications with the entry you will get a mail.

I cannot find it with search in this forum or is the guides.

It can be very handy when it is possible.

When it is not available, is it possible to make a feature request for it.

 

Thank you,

 

Johan

  66860   Tue Jul 27 11:35:40 2010 Reply Stefan Rittstefan.ritt@psi.chQuestionAll2.7.5Re: Mail when elog entry is expired

Johan Schuring wrote:

Hi,

 

Is it possible to set a timestamp on an elog entry say for about 5 days in the future, when it is expired and there are no modifications with the entry you will get a mail.

I cannot find it with search in this forum or is the guides.

It can be very handy when it is possible.

When it is not available, is it possible to make a feature request for it.

This is not possible at the moment. Sounds to me more like a calendar function. What you could do however is to define an attribute of type "datetime", which you can populate with the expiration date. Then you can do a search to look for entries which are past the expiration date. But you have to do that manually like once per day or so. 

  66861   Tue Jul 27 15:48:19 2010 Reply Johan Schuringjohan.schuring@getronics.comQuestionAll2.7.5Re: Mail when elog entry is expired

Stefan Ritt wrote:

Johan Schuring wrote:

Hi,

 

Is it possible to set a timestamp on an elog entry say for about 5 days in the future, when it is expired and there are no modifications with the entry you will get a mail.

I cannot find it with search in this forum or is the guides.

It can be very handy when it is possible.

When it is not available, is it possible to make a feature request for it.

This is not possible at the moment. Sounds to me more like a calendar function. What you could do however is to define an attribute of type "datetime", which you can populate with the expiration date. Then you can do a search to look for entries which are past the expiration date. But you have to do that manually like once per day or so. 

Thank you for your reply and the tip.

People can allways use another app (mail) for this, it would be nice,nothing more.

 

 

 

  66863   Wed Jul 28 16:55:32 2010 Reply Stefan Rittstefan.ritt@psi.chQuestionAll2.7Re: What *exactly* do "clone" and "mirror" do?

David McKee wrote:

We have been hosting logbook far (geographically and in internet hops) from our experimental site. Recently we have (finally!) gotten reliable on-site internet, and would like to host the log book on-site.

I have a suspicion that some combination of the -C, -m, and -M flags will allow me to migrate the logbook automagically and with a minimum risk of trouble from concurrent operation on the logbook, and to maintain the existing version as a mirror of the new official on-site version. But documentation is not being very helpful. Can someone say a few more words about what these options do?

 

I've been experimenting as I compose this and have a suggestion for language that might be useful somewhere in the documentation:

In this context "to clone" means to copy the configuration file and all data files associated with a log book so that I can host an identical logbook on a new host (that is this is the command to migrate a logbook).  After cloning the two installation are identical, but no effort is made to keep them so: if you continue to run both copies post made to one will not be reflected in the other.

Is this correct?

I'm still not clear on what the -m and -M options do.

Yes this is correct. But actually you do not necessarily need that. If you want to migrate a logbook to another server, you can just copy over the elog directory containing the configuration file and the logbooks. That's it. Mirroring now means manually triggered or periodic synchronization between two servers to keep the logbooks in sync. Like if an entry is entered on one server, it gets copied over to the other server automatically. That works in both directions. The periodic mirroring can be done using the options "Mirror server" and "Mirror cron" in the configuration files. It can be manually triggered using the "-m" and "-M" flags. But I guess in your case it's enough to copy over the elog tree just once. 

Goto page Previous  1, 2, 3 ... 697, 698, 699 ... 804, 805, 806   Next  
ELOG V3.1.5-3fb85fa6