Path: utzoo!utgpu!attcan!uunet!lll-winken!ames!husc6!bloom-beacon!EXPO.LCS.MIT.EDU!rws
From: rws@EXPO.LCS.MIT.EDU (Bob Scheifler)
Newsgroups: comp.windows.x
Subject: Re: A developer's view of the X fill policy
Message-ID: <8901062219.AA08334@EXPIRE.LCS.MIT.EDU>
Date: 6 Jan 89 22:19:44 GMT
References: <8901061651.AA14516@adt.uucp>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 23


    Why should we have the proposed border_fill affect line drawing at all?

We shouldn't necessarily.  I'm just trying to get you to think through all
the issues, so that the proposal really proposes what you want (and also so
that you can begin to understand that design isn't always as simple as it
seems).  So, if border_fill doesn't apply to lines, I assume that means
you're happy with the existing ("partial border") semantics for wide lines?

    Who cares?  At least two DEVELOPERS, both of which are doing object
    oriented graphical systems.

Geez, stay calm.  I wasn't trying to write you off.  I already know about
you two developers, the question is whether there are more.  I'm not trying
to put down your idea, but for almost *any* idea I can probably find two
people who think it's a good one; the question is whether there is reasonable
consensus that it is a good idea.

   Making it difficult to do common things isn't going to help.

True, but the hard part is figuring out what is "common".  (For example,
PostScript doesn't seem to provide a "fill-sans-strokepath" primitive.)
That's why I'm asking the question of who else cares your proposed semantics.