Ok, I turned display of HTML attachments completely off in 2.5.8-3. So if one wants to see
it, on has to click on it. Otherwise there is no way to ensure a correct web page, so
people would complain again that the page does not pass the HTML validator if someone
attached an invalid HTML file.

I think this is reasonable. All the HTML-files which I want insert (created with the software
INCA) are not shown correctly. My testfiles made with OpenOffice are shown correctly. Maybe
you have the time to program an option for the attachement "Show inside/Show in new window or
tab", so that the user can choose, how his HTML file is shown. Similiar to the option "Submit
as HTML text".

> I think this is reasonable. All the HTML-files which I want insert (created with the software
> INCA) are not shown correctly. My testfiles made with OpenOffice are shown correctly. Maybe
> you have the time to program an option for the attachement "Show inside/Show in new window or
> tab", so that the user can choose, how his HTML file is shown. Similiar to the option "Submit
> as HTML text".

I changed it such that all attachment are shown in a separate browser window if clicked. Hope
this satisfies most people. I believe an extra switch in the config file is too much for this
little thing, unless someone absolutely wants back the old behaviour.

Can conditional attributes be assigned as conditions?

Arbitraty Example:

Attributes = Operating system, Version, Name
Options Opperating system = Linux {1}, Windows {2}
{1} Options Version = 2.2 {a}, 2.4 {b}, 2.6 {c}
{2} Options Version = ME {d}, 2k {e}, NT {f}, XP {g}
{1&a} Options Name = This computer
{1&b} Options Name = That Computer
{2&f} Options Name = Workstation

and so on..?

> Can conditional attributes be assigned as conditions?

Well, I guess the question was: "Can you implement this?" I'm sure that you
tried before.. (;-)

Yes, it is working now, I had to add some new code and fix a bug with AND'ed
conditions (via '&'). The new version is under CVS. Since you use Windows, you
have to wait for the next release.

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.