Demo Discussion
Forum Config Examples Contributions Vulnerabilities
  Discussion forum about ELOG, Page 770 of 806  Not logged in ELOG logo
 Find |  Login |  Help 
New entries since:Thu Jan 1 01:00:00 1970
 Full | Summary | Threaded | Hide attachments  Show all entries    6445 Entries 
Goto page Previous  1, 2, 3 ... 769, 770, 771 ... 804, 805, 806   Next  
ID Date Icon Author Author Email Categoryup OS ELOG Version Subject
  65761   Thu Feb 28 19:07:19 2008 Idea Yoshio ImaiRequestLinux | All2.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
  65768   Thu Mar 6 14:03:17 2008 Reply Stefan Rittstefan.ritt@psi.chRequestLinux | All2.6.5Re: #include statements and attachment visibility

Yoshio Imai wrote:
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.


I made you something even better: I added a new option called Attachment lines. This number restricts the number of lines shown for any ASCII attachment. The default is 300, but you can set this to 10 maybe. This still shows you the first 10 lines of the attachment which might be handy. If you set this value to zero, no line at all is shown. The new feature is in SVN revision 2069.


Yoshio Imai wrote:
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.


I will put this feature on the wishlist.
  65771   Thu Mar 6 18:19:48 2008 Cool Yoshio ImaiRequestLinux | All2.7.3Re: #include statements and attachment visibility
Thanks you! I just installed the new revision, and it works.

However, it does not seem to work in list mode (with attach=1 option): elog still shows all the lines of attached text files there.

I also noticed that the images referenced inline are also shown in the attachment list in list mode, although this post gave me the impression that in list mode, too, inline images should only be displayed inside the elog entry and not in addition as attachment.

Might this be a bug, or is there a particular reason why it is like that?
  65772   Fri Mar 7 08:01:44 2008 Reply Stefan Rittstefan.ritt@psi.chRequestLinux | All2.7.3Re: #include statements and attachment visibility

Yoshio Imai wrote:
However, it does not seem to work in list mode (with attach=1 option): elog still shows all the lines of attached text files there.

I also noticed that the images referenced inline are also shown in the attachment list in list mode, although this post gave me the impression that in list mode, too, inline images should only be displayed inside the elog entry and not in addition as attachment.


I fixed both issues in revision #2072.
  65773   Fri Mar 7 13:07:34 2008 Agree Yoshio ImaiRequestLinux | All2.7.3Re: #include statements and attachment visibility
Thank you, works perfectly!
  65798   Fri Mar 28 13:48:41 2008 Question Franck Cfranck.c95@free.frRequestWindows Can u send me the configuration file for this logbook ?

Hi, I try to set up a logbook and i wanted to create something with icons (like this logbook) and it will be easier for me if i have ur config file

Thanks a lot

Franck

  65799   Tue Apr 1 02:04:35 2008 Idea Dennis Seitzdseitz@berkeley.eduRequestAll Duplicate entry suggestion

 We have configured several logbooks to allow users to duplicate an entry in another logbook, which is very useful for entries which apply to more than one category.

However, once the entry is duplicated, subsequent revisions to the original entry are not copied to the duplicate entries.

I can see where implementing that would add a lot of code to ELOG.  Rather than do that, would it be possible to add a configuration option to duplicate only the attributes, and place a link to the original entry in the body of the duplicated entry instead of the full text?

Thanks,

Dennis

  65800   Tue Apr 1 08:01:02 2008 Reply Stefan Rittstefan.ritt@psi.chRequestAll Re: Duplicate entry suggestion

Dennis Seitz wrote:

 We have configured several logbooks to allow users to duplicate an entry in another logbook, which is very useful for entries which apply to more than one category.

However, once the entry is duplicated, subsequent revisions to the original entry are not copied to the duplicate entries.

I can see where implementing that would add a lot of code to ELOG.  Rather than do that, would it be possible to add a configuration option to duplicate only the attributes, and place a link to the original entry in the body of the duplicated entry instead of the full text?

I don't know if you are aware, but you can put links to other entries manually into the text. Just enter them in the form elog:65799. You can click on that link which takes you the entry you reference. Unfortunately there is at the moment no automatic way to generate this back link automatically.

Goto page Previous  1, 2, 3 ... 769, 770, 771 ... 804, 805, 806   Next  
ELOG V3.1.5-3fb85fa6