ELOG Forum

> I am trying to unify several existing logbook collections that run on
> seperate servers under a single server using groups.  For a top group, under
> "[global topgroupname]", I would like to redefine the resource directory or
> the logbook directory so that everything except for the .cfg is at it
> original location.  However, it seems like "Resource dir" and "Logbook dir"
> can not be redefined in the global section for specific groups.  Is it
> possible to redefine these directories for each top group, or is it feature
> that could be added?

Not easily. There is only a single logbook and resource directory inside elogd.
The reason is that these are constants which can be fixed during compile time.
The Debian package uses this extensively. So having multiple directories would
break that scheme.

> I could probably do what I want with soft-links, but redefining the resource
> dir just seems to be right way to do this.  (For one thing, I would like
> different favicons for each group.)

I'm afraid you have to use soft links. The favicons you can define however via
the theme, which is a per-logbook option, so it would work in the [global
topgroupname] section as well.

67133

Thu Sep 29 10:12:40 2011

Stefan Ritt

Re: Digest page or email?

Graham Medlin wrote:

We have about 10 logbooks running on the same Elog that all get fair use. Many people have turned off new entry emails because they were filling up inboxes, but are still interested in what's new. I saw the option to add "?last=1" to the start page, although I'm afraid using it might cause confusion over how to get to the older posts.

I was trying to figure out a way of creating a "digest" of sorts, a list of entry subjects posted in the past day or week, something similar to what's generated by "?last=1?mode=threaded", but for every logbook (similar layout to the selection page with nested logbooks). This could either be a page, or a regular email.

Is there way to generate such a cross-logbook page? What about a scheduled email formatted based on a given filter?

PS: The elog has been invaluable to us, a big thanks to all involved!

What we do is use the RSS feed of elog. This gives you nice summaries without going through your email inbox. Most browsers have RSS readers, there are also tons of stand-alone programs for that. Attached is a screenshot from the Google Reader subscribed to this logbook and to the "contributions' logbook. You see nice one-line summaries, you can expand them, and you can go directly to the logbook if you click on the arrow. The second image is from the Firefox using what they call "live bookmarks", but it's basically a RSS reader.

To make this work, I installed the RSS extension of Google Chrome (Firefox has this under "Bookmarks"/"Subscribe to this page"), then go to the elog page, then click on the RSS icon, then clicked on "Subscribe to this" via Google Reader. Just a few clicks.

Hope this is what you want.

- Stefan

Attachment 1: Screen_Shot_2011-09-29_at_9.58.02_.png

Attachment 2: Screen_Shot_2011-09-29_at_10.06.52_.png

67134

Thu Sep 29 16:55:25 2011

Re: Digest page or email?

Stefan Ritt wrote:

Graham Medlin wrote:

Is there way to generate such a cross-logbook page? What about a scheduled email formatted based on a given filter?

PS: The elog has been invaluable to us, a big thanks to all involved!

Hope this is what you want.

- Stefan

Perfect! I didn't not know there was RSS support. I will probably use something like rss2email, but this is exactly what I needed. Thanks!

67960

Fri Jun 5 19:01:05 2015

Andreas Luedeke

andreas.luedeke@psi.ch

Info

All

3.1.0+

Re: Different way CSS files are handled

Hi Stefan,

there is a little problem with the Makefile (on SL5 and SL6): the following line:

@$(INSTALL) -m 0644 themes/default/* $(ELOGDIR)/themes/default/

/usr/bin/install: omitting directory `themes/default/icons'
make: *** [install] Error 1

When I go back to the old Makefile construct:

        @$(INSTALL) -m 0644 themes/default/icons/* $(ELOGDIR)/themes/default/icons/
        @for file in `find themes/default -type f` ;\
          do \
            if [ ! -f $(ELOGDIR)/themes/default/`basename $$file` ]; then \
              $(INSTALL) -m 0644 $$file $(ELOGDIR)/themes/default/`basename $$file` ; \
           fi; \
          done

then it seems to work again.

Cheers

Andreas

Stefan Ritt wrote:

Hi,

I just implemented a different way CSS files are handled in ELOG. Previously, we had the default.css, which could be adjusted for specific needs. Some people did that (like myself). So I changed a few colors etc. When I now implement a new feature in elog, it might need a new CSS class which I put in default.css. But this means that people who have modified this file get it either overwritten, or do not get the new styles.

In order to fix this, the default.css is now called elog.css and is always inluded in any ELOG page. If one specifies a CSS file with "CSS = <file.css>", then this CSS file is loaded in addition to elog.css. So one can put only the modifications into that file and inherits all the rest from elog.css. If new features come in elog.css, the installation with the personalized CSS file will then get the new features from the new elog.css automatically, and just overwrite a few settings in the personalized file. Here is an example:

elog.css:

td {
color:black;
font-size:12px;

}

Personalized file special.css, activated with "CSS = special.css" in the elogd.cfg file:

td {
font-size:18px;
}

This personalized file now overwrites the font size from elog.css to 18 pixel, while maintaining all the rest from elogd.css.

The modification is committed to GIT and will be contained in the next release of elog.

/Stefan

Goto page Previous 1, 2, 3 ... 568, 569, 570 ... 806, 807, 808 Next

ELOG V3.1.5-3fb85fa6