As I wrote you by mail, I implemented your idea in the following way. As you
say, it's only working on Gecko based systems. I did not implement additional
configuration parameters, but made it through the CSS file:

- adding a new CSS style "attachmentframe" around all attachments
- adding class "attachmentframe" to the 'default.css' like:

.attachmentframe {
  border:1px solid grey;
  border-top:1px solid lightgrey;
  border-left:1px solid lightgrey;
  background-color:white;
  padding:5px;
}

.attachmentframe img {
    max-width:100%;
}

The latter restricts the image size to 100%, which is the width of the 
browser window. I like it that, but of course you can write 200px or 
anything else. Please find the modified elogd.c and default.css under CVS.

Is it possible to create a Link To command (ala Copy To, Move To) that
would allow you to reference an entry in another log book without copying it?
This would be handy as the info would be kept current in both log books.
My thought is that it would create a psuedo entry in the other log
book that pointed back at the originating log book entry (similar to a 
UNIX soft link)
/Tim

> Is it possible to create a Link To command (ala Copy To, Move To) that
> would allow you to reference an entry in another log book without copying it?
> This would be handy as the info would be kept current in both log books.
> My thought is that it would create a psuedo entry in the other log
> book that pointed back at the originating log book entry (similar to a 
> UNIX soft link)

What you ask for is not possible due to internal reasons. The underlying database
does not support links. But what you can do is to reference a logbook entry with

elog :<loglook>/<id>

So I can reference your question with elog:Forum/1099. Some people make even
complete "summary" pages where they reference a whole set of other logbook entries like

Your question is at elog:Forum/1099
A script for thumbnail generation is at elog:Contributions/12
Demo entries: elog:Linux+Demo/14, elog:Linux+demo/1

Is it possible to have last runtime filtering and viewing method to be
stored in a cookie in order to make them permanent across navigation ?

I mean:
- if I decide to view "all" entries in the elog and then open one of them, 
  I'd like not to select "show all entries" again and again
- same thing if I choose to view last week
- same for every runtime filter and/or viewing option 

hope this is simple to implement :-)  thanks in advance 

is it possible to make the "+" sign, indicating a thread in the threaded
view, to be clickable in order to be able to expand a single thread each time ?

of course elog should remember the choice, so it will be possible to expand
N threads over the M total ones..

thanx :-) 

> of course elog should remember the choice, so it will be possible to expand
> N threads over the M total ones..

How should elog remember that? If you put this into the URL like

http://<elog-host>/<logbook>/?exp=12&exp=14&exp=18

to expand the entries 12, 14 and 18, it might work fine. But imagine that some uses
have very long list with thousands of entries. This would make the URL very long,
everything very slow and could even crash some browsers.

What I usually do is to not expand the list. If I click on an individual entry, I
see then the expanded thread for that entry above that entry. But you probably
realized this possibility already.

> Is it possible to have last runtime filtering and viewing method to be
> stored in a cookie in order to make them permanent across navigation ?

Sounds like a good idea. Will put it on the wishlist.

> > of course elog should remember the choice, so it will be possible to expand
> > N threads over the M total ones..
> 
> How should elog remember that? If you put this into the URL like
> 
> http://<elog-host>/<logbook>/?exp=12&exp=14&exp=18
> 
> to expand the entries 12, 14 and 18, it might work fine. But imagine that some uses
> have very long list with thousands of entries. This would make the URL very long,
> everything very slow and could even crash some browsers.
> 
> What I usually do is to not expand the list. If I click on an individual entry, I
> see then the expanded thread for that entry above that entry. But you probably
> realized this possibility already.

:-) yes I do 

A way may be using cookies, otherwise one can implement a kind o session mechanism
(using cookies or QS to pass sessid and storing user data on the server for a limited
time...)
the session method may be useful, but more difficult to implemnet, of course