Re: Locking entries, posted by Stefan Ritt on Wed Sep 8 15:48:47 2004
|
One possibility is to use the option "Restrict edit time = <hours>". This way
an entry can only be edited let's say 8 hours after it has been created.
Another way is to maintain two logbooks, a "scratch" logbook and an "archive"
logbook. Users would put their entries into the scratch logbook, the staff
would examine it and move them to the archive logbook, where all users only
have read access to. To move entries between logbooks, you have to put the
"Move to" command in the configuration file like:
Menu commands = Back, New, Edit, Delete, Reply, Find, Move to, Config, Help |
Re: URL bug in elogd.cfg, posted by Steve Jones on Wed Sep 8 17:39:43 2004
|
> This problem has been fixed in revision 1.462
Thank you! |
Enhanced "eLog Version" Variable, posted by Steve Jones on Fri Sep 24 19:17:52 2004
|
Stefan, would it be ok to add the "minor" revision level to the VERSION
constant? I've been doing this after I download source just so I can keep
things straight, you keep cranking out versions ;->
EX:
#define VERSION "2.5.4-4"
BECOMES
#define VERSION "2.5.4-4-1.483" or something like that?
Just a thought.
Thanks |
|
Re: Enhanced "eLog Version" Variable, posted by Stefan Ritt on Fri Sep 24 22:37:01 2004
|
Sorry for that. The idea is that the -4 is the minor number between releases
(mainly for bug fixes and impatient users (;-) ). I accidently overwrote the
-4 version several times when testing a new RPM building scheme, but I promise
to take more care in the future (:-)))
Having the CVS revision in the executable is however a good idea and I will
put it in.
> Stefan, would it be ok to add the "minor" revision level to the VERSION
> constant? I've been doing this after I download source just so I can keep
> things straight, you keep cranking out versions ;->
>
> EX:
> #define VERSION "2.5.4-4"
> BECOMES
> #define VERSION "2.5.4-4-1.483" or something like that?
>
> Just a thought.
>
> Thanks |
|
Re: Enhanced "eLog Version" Variable, posted by Steve Jones on Wed Oct 6 06:14:36 2004
|
No big deal - I looked at the code and you did a much more thorough job than I
would have done. Appreciate all of the hard work -- this product is masterful!
> Sorry for that. The idea is that the -4 is the minor number between releases
> (mainly for bug fixes and impatient users (;-) ). I accidently overwrote the
> -4 version several times when testing a new RPM building scheme, but I promise
> to take more care in the future (:-)))
>
> Having the CVS revision in the executable is however a good idea and I will
> put it in.
>
> > Stefan, would it be ok to add the "minor" revision level to the VERSION
> > constant? I've been doing this after I download source just so I can keep
> > things straight, you keep cranking out versions ;->
> >
> > EX:
> > #define VERSION "2.5.4-4"
> > BECOMES
> > #define VERSION "2.5.4-4-1.483" or something like that?
> >
> > Just a thought.
> >
> > Thanks |
|
Re: URL Parsing Problem, posted by Stefan Ritt on Wed Oct 13 20:28:02 2004
|
Has been fixed in revision 1.492. |
Re: URL Parsing Problem, posted by RB on Thu Oct 14 11:37:18 2004
|
> Has been fixed in revision 1.492.
Thanks, Stefan. |
Implementation of RSS feeds, posted by Stefan Ritt on Mon Oct 25 23:16:39 2004 
|
I implemented experimentally RSS feeds into Elog. Before releasing this new
addition, I would like to collect some experience with it. This forum now
supports RSS feeds, for which you can subscribe with a RSS feed reader like
Mozilla Firefox. Please give it a try and send me any feedback.
For an introduction to RSS feeds, please see
http://www.webreference.com/authoring/languages/xml/rss/intro/
To subscribe to a logbook, enter following URL into your RSS reader:
http://<your-elog-host.domain>/<logbook>/elog.rdf
From the newest Mozilla Firefox browser, you can also click on the RSS box at
the lower right corner of the browser (see attachment). |