| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 353.1 | What does VAXSTATION use? | PDVAX::P_DAVIS | aka SARAH::P_DAVIS | Thu May 07 1987 10:50 | 3 |
| Just out of curiousity, what would you want a VAXSTATION destination
to produce? UIS calls? Given the DECwindows strategy, I doubt
serious consideration would be given to supporting UIS specifically.
|
| 353.2 | (1) oops; (2) what do you have in mind? | VAXUUM::DEVRIES | Those are features, not bugs | Thu May 07 1987 15:24 | 18 |
| RE: -INCLUDING as an -E- message
You are, of course, right. That was an implementation oversight
in BL07 that will be fixed in later versions. Thanks for the
report.
RE: VAXSTATION as a destination
To second the previous reply: what would you expect this
destination to provide? The TERMINAL destination provides
output that can be reproduced on any ANSI device, whether
a VTxxx terminal, a VTxxx emulator on your VAXSTATION (or
whatever), or a printer that understands simple ANSI commands
(text, control characters, bold and underline sequences).
Did you have something else in mind?
Mark
|
| 353.3 | | PDVAX::P_DAVIS | Peter Davis (aka SARAH::P_DAVIS) | Thu May 07 1987 15:47 | 7 |
| I'm guessing that the VAXSTATION destination was intended to allow
<EMPHASIS>(previewing) of fancy documents on workstations. This
is something that may be possible with PostScript output on DECwindows,
since a general purpose PostScript preview capability is being
considered. Other than that, however, the VAXSTATION output would
require some display software that could show a page at a time
with matching video fonts, etc. Not a trivial piece of work.
|
| 353.4 | VAXstation's use SIXEL graphics | CHAMBR::GUINEAU | | Thu May 07 1987 17:01 | 9 |
|
No, nothing too fancy. Just a SIXEL output. With white space for page-breaks.
Probably a subset of the LN03 stuff?
John
|
| 353.5 | workstation preview planned -- but not trivial | VAXUUM::DEVRIES | Those are features, not bugs | Fri May 08 1987 09:20 | 20 |
| > No, nothing too fancy. Just a SIXEL output.
To view sixel files is trivial (just type). To CREATE them, however,
is very difficult. You've got to do everything you do for any other
device, plus figure out what pixels all that stuff on your page
will activate for the requested characters, sizes, fonts, spacing,
graphics, ... everything on the page, then encode that in sixel
format.
If you leave it to some other software (UIS, X, etc.) to worry about
the pixels, you still have a full-blown device converter, at least
as complex as the LN03 converter -- not merely a subset of it.
This kind of thing is on the list for development in the near future.
There are some kinds of previewers kicking around now, but nothing
that is really well integrated with the world of VAX DOCUMENT.
This kind of thing is a requirement for the future, and will come
to pass. And the sooner, the better.
Mark
|