Path: utzoo!utgpu!attcan!uunet!lll-winken!lll-lcc!ames!mailrus!tut.cis.ohio-state.edu!bloom-beacon!adt.UUCP!madd
From: madd@adt.UUCP (jim frost)
Newsgroups: comp.windows.x
Subject: Re: A developer's view of the X fill policy
Message-ID: <8901061651.AA14516@adt.uucp>
Date: 6 Jan 89 16:51:42 GMT
Sender: daemon@bloom-beacon.MIT.EDU
Organization: The Internet
Lines: 28

Ok, I understand what you mean now.  I hadn't realized that the fill
definition extended to lines as well, although I admit that this makes
sense.

Why should we have the proposed border_fill affect line drawing at
all?  If we don't, there isn't a problem with what's in the border and
what's not.  Just as the fill rule has no effect on lines, it would
seem that my proposed addition need have no effect (unless I'm
overlooking something, which is entirely possible -- am I?).

>and indeed, my question after all this is worked out is "Who else cares
>a whole lot about this, and why?".

Who cares?  At least two DEVELOPERS, both of which are doing object
oriented graphical systems.  They may not be the wave of the future
but object oriented systems are very useful things, and it might be to
X's advantage to make it easy (or at least easier) to write them.  I
might be missing the boat here but I thought the idea was to
standardize the industry on a graphical environment.  Making it
difficult to do common things isn't going to help.  We originally
picked X as an environment because it would give us such a wide range
of machines as a base after the port.  Unfortunately it turns out to
be easier to port to other systems than it is to get around some of
the limitations of X.  I'm trying very hard to correct this, not only
for my own good but for that of the industry.

jim
madd@bu-it.bu.edu