• forkpty() emulation for Solaris
  
• PAM support
  

> Using the COMMENT feature to add guidance to an ATTRIBUTE works great, but
> is it possible to add a TOOLTIP <ATTRIBUTE> = so as to save screen space? 

Where should the tooltip appear? In the entry form or when an entry is
displayed, or even in the tabular listing? I can put a title arround the
attribut names such as

<div title="Please enter some subject here">Subject:</div>

which gets interpreted by most browsers as a tooltip. However it's not
apparent to the user that leaving the cursor on top of "Subject" opens a
tooltip, especially since the cursor is displayed as the text cursor (vertical
bar), not as an arrow over the attribute. Do you have a link to a public web
page which uses tooltips?

> For a complex entry form it is desireable to try and have everything in a
> single window and this, I think, would help.

Aiming for running elog on you PDA? Let me know if you succeed...

> > Using the COMMENT feature to add guidance to an ATTRIBUTE works great, but
> > is it possible to add a TOOLTIP <ATTRIBUTE> = so as to save screen space? 
> 
> Where should the tooltip appear? In the entry form or when an entry is
> displayed, or even in the tabular listing? I can put a title arround the
> attribut names such as
> 
> <div title="Please enter some subject here">Subject:</div>
> 
> which gets interpreted by most browsers as a tooltip. However it's not
> apparent to the user that leaving the cursor on top of "Subject" opens a
> tooltip, especially since the cursor is displayed as the text cursor (vertical
> bar), not as an arrow over the attribute. Do you have a link to a public web
> page which uses tooltips?
> 
> > For a complex entry form it is desireable to try and have everything in a
> > single window and this, I think, would help.
> 
> Aiming for running elog on you PDA? Let me know if you succeed...

In the Entry form I am thinking, as this is when most people need some help. 
Perhaps the user could be clued in with a "Mouse-over each attribute for Help"
COMMENT at the top.

As for the PDA, no, it's just that some people around here get confused if they
have to scroll down.  Not a big thing . . . ;-> Hmmm, PDA . . . 

Ok, I added the option

Tooltip <attribute> = ...

I apply the HTML "title" tag to the whole table row, so the tooltip appears on the
whole line, not only the attribute name. I guess this is much more intuitive. Give
it a try. New version under CVS and available as a snapshot.

> Ok, I added the option
> 
> Tooltip <attribute> = ...
> 
> I apply the HTML "title" tag to the whole table row, so the tooltip appears on the
> whole line, not only the attribute name. I guess this is much more intuitive. Give
> it a try. New version under CVS and available as a snapshot.

I like the implementation, especially with the tooltip popping up anywhere in the
area.  Thanks.

> I'd like this same facility with elog.  Now I know that it can be
> done by (for example) in the config file preselecting one of the
> selections on reply- or indeed one that does not exist to "clear" it, 
> but in this case that is not the route I'd want to take every time.

What about defining an additional option "unspecified". So you have

Roptions attr = option1, option2, option3, none

Whenever you click on "none", the selection is removed from the other options. The HTML standard unfortunately does 
not foresee radio buttons not being selected, so I would have to tweak it somehow to get exactly what you want.

> > I'd like this same facility with elog.  Now I know that it can be
> > done by (for example) in the config file preselecting one of the
> > selections on reply- or indeed one that does not exist to "clear" it, 
> > but in this case that is not the route I'd want to take every time.
> 
> What about defining an additional option "unspecified". So you have
> 
> Roptions attr = option1, option2, option3, none
> 
> Whenever you click on "none", the selection is removed from the other options. The HTML standard unfortunately does 
> not foresee radio buttons not being selected, so I would have to tweak it somehow to get exactly what you want.

Hadn't realised the standard was written that way.  
What you propose seems fine to me.

David.