
|
[haiku-appserver]
||
[Date Prev]
[10-2004 Date Index]
[Date Next]
||
[Thread Prev]
[10-2004 Thread Index]
[Thread Next]
[haiku-appserver] Dual-display
- From: "Mikael Jansson (mailing lists)" <lists@xxxxxxxxxxxxxxxxx>
- To: haiku-appserver@xxxxxxxxxxxxx
- Date: Mon, 25 Oct 2004 15:32:54 GMT
Hello again,
Is multi-display something you've considered?
What I'm thinking of in a multi-display setup like this:
A Display is a set of monitors arranged physically in a MxN layout
without holes, where M, N >= 1. Displays maps to workspaces 1:1. One
can have >= 1 Displays connected to the computer. A workspace cannot be
displayed at the same time on > 1 Display.
Usage scenario:
Three monitors available, M1, M2, M3. M1 and M2 forms a wide monitor,
called D1 (Display 1). M3 is D2. I use D2 mainly on workspaces 1
through 4, which is where I keep mail, web and IRC. D1 is for
development, where I need to see output, debugger, documentation and
the actual code at the same time. I usually use it with workspaces 5
through 8. If I happen to activate workspaces 5 through 8 on D2 (low-
res), I'll have a large virtual desktop I can use the mouse to pan in.
On the other hand, if I use D1 on workspaces 1 through 4, only one of
the monitors will be active (at least that's the naive solution.)
Is this what you guys had in mind, as well?
Moreover, is there a design document of the app_server I can read so I
don't have to send annoying messages to the list whenever I want to
know something, or am I forced to get an understanding of the
app_server sauce?
Thanks in advance,
--
Mikael Jansson
http://mikael.jansson.be
|

|