dps-devel

Re: [Dps-devel] Building with XFree86 4.0.2?

[Juliusz C. <Jul...@en...>]

>> gcc DefaultGcc2i386Opt    -I. -I..

I got it.  You need to build the config files in the X source tree; it
won't work with a virgin tree.

Yep, the DPS build procedure is badly hosed.

                                        Juliusz

Re: [Dps-devel] Building with XFree86 4.0.2?

[Juliusz C. <Jul...@en...>]

KB> Texteriods builds but I don't see anything when I run it...

Probably a fonts problem.  Texteroids is rather stupid about error
handling (i.e. it doesn't do any).

What does the following do in dpsexec?

  /Times-Roman findfont flush
  20 scalefont flush setfont flush
  20 20 moveto (Hello) show flush

If it breaks, something's wrong with your fonts directory of Fontmap.

                                        Juliusz

Re: [Dps-devel] Building with XFree86 4.0.2?

[Kevin B. <Co...@co...>]

Juliusz Chroboczek wrote:
> 
> KB> Texteriods builds but I don't see anything when I run it...
> 
> Probably a fonts problem.  Texteroids is rather stupid about error
> handling (i.e. it doesn't do any).
> 

Okay, maybe I'll improve it a little...


> What does the following do in dpsexec?
> 
>   /Times-Roman findfont flush
>   20 scalefont flush setfont flush
>   20 20 moveto (Hello) show flush
> 
> If it breaks, something's wrong with your fonts directory of Fontmap.
> 
>                                         Juliusz

That works fine.  What do all the flush's do?  Are they required to see
any errors during dpsexec?  I noticed dpsexec only seems to print a
prompt in some situations, not after every 'Enter'.  But when I enter
something that causes a stackunderflow or nocurrentpoint error it prints
the error and a prompt immediately.

I also rebuilt the clock example against OpenMotif (the one I was trying
to build with LessTif).  It doesn't show any errors now, but it still
doesn't display anything.  Possibly related to the texteroids problem?

-- 
Kevin

Re: [Dps-devel] Building with XFree86 4.0.2?

[Juliusz C. <Jul...@en...>]

KB> That works fine.

Then I've got no idea what's going wrong.  The ``Hello'' message does
appear, right?

You may try uncommenting lines 274 and 275 in texteroids.c.

KB> What do all the flush's do?  Are they required to see any errors
KB> during dpsexec?

Not errors, only standard output.

KB> I noticed dpsexec only seems to print a prompt in some situations,
KB> not after every 'Enter'.

In DPS, context output is buffered.  The executive (the thing you
interact with in dpsexec) works by flushing output before printing
every prompt.  The reason that works is that the executive does not
interact with standard input, but with terminal input which gives it a
chance to print a prompt once in a while.

I have not (yet?) implemented terminal input, but instead have made it
an alias for terminal input.  So you need to type either ``flush'' or
``prompt'' once in a while to get the output flushed.

KB> But when I enter something that causes a stackunderflow or
KB> nocurrentpoint error it prints the error and a prompt immediately.

The error handler runs a new instance of the executive which starts by
calling ``prompt'' which in turn calls ``flush''.

                                        Juliusz

Re: [Dps-devel] Building with XFree86 4.0.2?

[Kevin B. <Co...@co...>]

Juliusz Chroboczek wrote:
> 
> KB> That works fine.
> 
> Then I've got no idea what's going wrong.  The ``Hello'' message does
> appear, right?
> 

Yes, fonts seem to draw correctly.

> You may try uncommenting lines 274 and 275 in texteroids.c.
> 

No difference.

I built texteroids with debug, and it's hanging up in the pswrap for
GetInvCTM() in libc in a select() call.  


> KB> What do all the flush's do?  Are they required to see any errors
> KB> during dpsexec?
> 
> Not errors, only standard output.
> 
> KB> I noticed dpsexec only seems to print a prompt in some situations,
> KB> not after every 'Enter'.
> 
> In DPS, context output is buffered.  The executive (the thing you
> interact with in dpsexec) works by flushing output before printing
> every prompt.  The reason that works is that the executive does not
> interact with standard input, but with terminal input which gives it a
> chance to print a prompt once in a while.

Hmm, I'm a little lost here.  So... DPS passes the Postscripts tokens to
the interpreter immediately, right?  And executes them?  But any
response output from the interpreter may not appear until a flush?

Or are you saying that Postscripts tokens aren't passed to the
interpreter by DPS until a flush?  (Which doesn't match the behavior I'm
seeing...  But then again, I'm used to talking Postscript directly to a
printer, which doesn't do anything with tokens until you end a line or
use some other action which tells the interpreter to exec.)


> 
> I have not (yet?) implemented terminal input, but instead have made it
> an alias for terminal input.  So you need to type either ``flush'' or
> ``prompt'' once in a while to get the output flushed.
> 
> KB> But when I enter something that causes a stackunderflow or
> KB> nocurrentpoint error it prints the error and a prompt immediately.
> 
> The error handler runs a new instance of the executive which starts by
> calling ``prompt'' which in turn calls ``flush''.
> 
>                                         Juliusz

Re: [Dps-devel] Building with XFree86 4.0.2?

[Kevin B. <Co...@co...>]

Juliusz Chroboczek wrote:
> 
> >> gcc DefaultGcc2i386Opt    -I. -I..
> 
> I got it.  You need to build the config files in the X source tree; it
> won't work with a virgin tree.
> 
> Yep, the DPS build procedure is badly hosed.
> 
>                                         Juliusz

Oh, okay.  Must be a tools problem, I noticed my path statement doesn't
default to using the different projectroot binaries first.

I was also able to force DPS/examples/clock to build, but what you said
looks like the problem.  I had to change one of the Mrm functions to get
it to run, but then it doesn't draw any of the user interface.  It looks
like it reads the uid file and ignores most (all?) of the graphical
objects defined.  So I end up with an empty window.  Thats fits your
description of uil being an early implementation.  I'm going to take a
look at OpenMotif.  Would it be useful to have a small test app you
could add to the dps package?  Something not licensed by Adobe or GPL?

I managed to build dpsexec and get it running.  And see my first snippet
of postscript display something on the screen!

Texteriods builds but I don't see anything when I run it...

-- 
Kevin