T.R | Title | User | Personal Name | Date | Lines |
---|
3384.1 | bulova::bookreader | CLTMAX::dick | Schoeller - Failed Xperiment | Mon Sep 24 1990 13:21 | 6 |
| Peter,
You might get better response in the conference specifically on the bookreader.
BULOVA::BOOKREADER.
Dick
|
3384.2 | | PSW::WINALSKI | Careful with that VAX, Eugene | Mon Sep 24 1990 15:16 | 24 |
| RE: .0
> One thing about all the applications under (behind ?)
> DECwindows is new windows are always created in about the
> most annoying place possible. For example, the long awaited
> DECwrite window splats right on top of the DECterm window as
> you're half way through reading a Mail...
Where should it go, then?
I'm not sure that there's a universally acceptable answer to that question on
a multitasking system. Most PCs (including the Mac) are basically
one-application-at-a-time systems. You start up an application, that
application has control of the system, and then when you're done with it,
control of the system transfers to another application. In such an
environment, there is no question as to which windows ought to be on top.
The situation is different with DECwindows. Suppose, for example, you had
started DECwrite and then, instead of reading through mail, you just folded
your arms and waited for DECwrite to come up. You wouldn't want DECwrite to
come up behind the other windows on the screen. You'd want it to come up on
top. I'm not sure how the window manager could be programmed to divine your
intent in these situations.
--PSW
|
3384.3 | I'm a little confused - do you really have a file in bookreader format? | CVG::PETTENGILL | mulp | Tue Sep 25 1990 01:08 | 20 |
| If yes, then you're currently expected to have the knowledge of a `librarian'
and know how to `catalog' and `file' it. If you refer to the bookreader
conference, you will find much discussion on that, and many other topics.
At this point it is a matter of priorities; would you rather have a better
assortment of books, or an easier method of cataloging things. At the moment,
the primary focus is on getting as much as possible of DEC's publications and
of our third party software producers and major customers materials online.
However, not every file is in a format that can be handled by bookreader.
Bookreader requires a very specialized format; only recently has there been
an alternative to VAX DOCUMENT for producing bookreader format material, and
even at that DECwrite is providing very basic functionality compared to what
would be ideal.
And, with all the above to consider, there is a major requirement to hyperize
bookreader by interfacing it to MEMEX.
And, the last time I looked, the number of people working on bookreader was
well less than a handfull. And much of the DECwindows is like that - 10
manyears of work for every 1-2 persons on the project.
|
3384.4 | | PSW::WINALSKI | Careful with that VAX, Eugene | Tue Sep 25 1990 17:08 | 7 |
| RE: .0, .2
By the way, my intent in .2 is to point out some of the design difficulties
that DECwindows faces in managing screen real estate. I think that .0 has a
valid cricicism. It's just that it would be difficult to do anything out it.
--PSW
|