Re: gnuplot-beta digest, Vol 1 #770 - 7 msgs

[Ethan A M. <merritt@u.washington.edu>]

On Sunday 16 April 2006 10:19 am, Per Persson wrote:
> 
> I have the following (mostly finished) stuff sitting in my local copy:
> * Monochrome (B/W) option
> 
> * Fill patterns
> I think that unless the plot is monochrome, filling with solid colors  
> are a better option than fill patterns, since patterns can cause  
> disturbing effects to the visual apperance ("leaning" bars etc.). So  
> my plan is to use fill patterns only in the case when the user  
> requests a B/W plot.

Several other terminals implement colored fill patterns as differing
intensity.  E.g. (from emf.trm):
        case FS_PATTERN: /* pattern fill implemented as partial density */
                fillpar *= 12;
		/* Fall through to ...*/
        case FS_SOLID: /* solid fill */
                if (fillpar >= 0 && fillpar < 100) {
                    double density = (double)fillpar / 100.;

> When you say that it doesn't support all the features of the x11  
> terminal, I take it that you refer to mouse interaction?

Mousing:  coord tracking, zoom, 3D interactive manipulation of view
Other:	hot keys ("bind" command)
	{no}persist
	UTF-8 and other multibyte font support

I'm not sure whether the full range of user-specified color options
are supported.  It looks like  AQUA_set_color is missing TC_LT from
its case statement, for example.  That is probably a trivial fix, but
there may be other places that bits are missing.

Another minor issue is that we're trying to make the syntax for
"set termoption", work for as many terminals as possible, particularly
screen terminals. That requires the (term->set_font)() routines to
accept strings of the form "fontname,fontsize".
I can't quite work out what AQUA_set_font is doing, but it seems to
expect an '@' rather than a comma as separator?
	 
> I haven't been paying close attention lately, but there was a  
> discussion on closing of paths which would be nice to be able to  
> implement. What was the outcome? Was there any change/addition to the  
> term API to support it? In that case I'll add that to aquaterm too.

Yes. There is a new terminal API entry  (term->path)(int i)
	i = 0  means start new path
	i = 1  means close path
Either or both of these may be a no-op, depending on what the
terminal needs.  So far only the postscript and svg terminals
actually use this mechanism, but it should probably be implemented
for pdf and maybe others as well.

-- 
Ethan A Merritt
Biomolecular Structure Center
University of Washington, Seattle 98195-7742