ELOG repository moved from CVS to Subversion, posted by Stefan Ritt on Fri Oct 7 17:18:32 2005
|
The elog repository has been moved from CVS to Subversion for various reasons. Those people who accessed the CVS repository in the past now have to do it in one of two different ways:
- Use the new ViewCVS gateway. This gateway now can also directly produce tarballs for the current repository snapshot
- Use anonymous Subversion access:
svn checkout svn+ssh://svn@savannah.psi.ch/afs/psi.ch/project/meg/svn/elog/trunk elog
svn@midas.psi.ch's password: svn
(you might have to enter the password several times...)
svn checkout svn+ssh://svn@savannah.psi.ch/afs/psi.ch/project/meg/svn/mxml/trunk mxml
svn@midas.psi.ch's password: svn
(you might have to enter the password several times...)
If there is any problem accessing the new repository, please let me know. |
|
Re: Logbook aliases, posted by Yoshio Imai on Wed Dec 14 11:40:54 2005
|
Ok, we will try this.
In our case, the "symlink"-type logbook might have been nice because of our daily backup routines. If we move the data of the old logbook to the newly created one, the backup process would first need to upload all logbook data to the backup server under the new directory name and then delete those under the old name.
In our case this is not so much of a problem, because the logbooks are small (100MB), but maybe you can add this to the wishlist if others request the same... (We could try to adjust the backup procedure, but I don't know how well this would work).
Anyway, thanks for the work!
P.S. What do you think about the idea of a "Go to page"-button for the single entry view? |
New ELOG version 2.6.0, posted by Stefan Ritt on Thu Dec 15 13:08:35 2005 
|
Dear ELOG users,
I'm happy to announce the release of ELOG version 2.6.0. After a long period of beta testing, all functions are now sufficiently stable for a public release. The major new feature is the introduction of the ELCode tags. They are similar to the well known BBCode tags, and let you format an elog entry. It is now also possible to embed inline images in an elog entry  , which are even sent in email notifications.
So have fun,
Stefan |
|
Shell substitution, especially interesting for running online experiments, posted by Stefan Ritt on Tue Dec 20 09:18:19 2005
|
Shell substitution has been introduced in an experimental state of the current SVN version of ELOG. It woks such that the subsititution list can contain $shell(<argument>) commands. The <argument> is passed to the shell of the operating system and the result is captured and subsituted. This is handy for online experiments, where one wants to pass information automatically to elog. Assume that there is a file /tmp/runnumber containing the current run number of the experiment. All one needs to put the current run number in an attribute "Run number" is the following line in the configuration file:
Preset Run number = $shell(cat /tmp/runnumber)
This subsitution works also for the main text body. Following option will put a calendar of the current month into the text body:
Preset text = $shell(cal)
note that shell subsitution works both on Windows and Unix, the "cat" and "cal" commands are however only present under Unix, but "cat" can be replaced with its Windows counterpart "type". |
|
Howto insert screen dumps into an elog entry, posted by Stefan Ritt on Tue Dec 20 11:17:17 2005
|
With the new ELCode tags, one can insert screen dumps pretty easy into elog entries. I personally use HoverSnap 0.8 under Windows, there are similar tools under Linux. HoverSnap puts a "Capture.jpg" file in a selectable directoy when you press PrintScreen, then you can instert this file with the  button. Here is such a screendump example:
 |
|
Suggestion additional ElCodes, posted by T. Ribbrock on Tue Jan 24 14:43:19 2006
|
I have to say, now that I'm finally on 2.6.x, I grew really fond of the ElCode stuff - great addition! It saves a lot of straight HTML typing for me... THANKS!
However, there are two things I'm missing:
- Headings
It would be great to have a range of , , ... tags that map directly to their HTML counterparts (and have buttons, of course...  ). That makes structuring an entry much easier in my opinion (and the output is easier to deal with for tools like html2ps) and I'm really missing those.
- Tables
This one is probably more difficult to add, but support for simple tables would be enough. But this is more a "nice to have"...
|
|
[SOLVED] Re: list view mode remembert - Bug?, posted by Holger Mundhahs on Wed Mar 1 12:27:36 2006
|
> > As default http://<hostname>/<LOGBOOK> shows the Summary View.
> > Clicking in "Full" changes the URL to http://<hostname>/<LOGBOOK>/?mode=full.
> > But now the URL http://<hostname>/<LOGBOOK> show the Full view as default.
> > I think the URL without ?mode=... should show every time the same result,
> > regardless the view used before. Or maybe I can configure, which view I want to
> > see if I use the URL w/o ?mode=... The option to hide/show attachments is affected too.
>
> Sure, that's a feature :D
>
> It was requested by several people that the view mode is stored in a cookie. So if you switch modes, it should be
> persistent. If I now add additional default flags, people will have hard time to understand what this is all
> about, since there might then be conflicting settings between the flags and the cookies. So for what exact purpose
> do you want what you requested? Why does it bother you that you have to click "Summary" again to get the summary
> view? Of course you can delete the local cookies and get the default behaviour (they are named [b]elmode[/b] and
> [b]elattach[/b]), but that might be a bit cumbersome.
Thank you for your explanation. My situation was, that I've played around with "Mode commands = 0". In normal case I
use the Summary view, but on one logbook I've changed it to Full before, and after setting the parameter I can't
revert it to Summary. But now I know how it works and can use it like intended.
Regards
Holger |
|
require smileys to have whitespace on either side?, posted by Glenn Horton-Smith on Sat Mar 4 05:17:14 2006
|
It would be nice if elog would only interpret something as a smiley if it is surrounded by whitespace. It can be particularly annoying that an 8 followed by a right paren becomes a "cool" smiley -- e.g., a parenthetical reference to event eighteen (18) becomes mangled... [That was "18" inside the parens.]
Is there already a way to solve this issue (other than always previewing your entries and adding spaces before parans)? Is the feature hard to implement? |