[haiku-appserver] Re: [haiku-appserver] Re: Refactoring

  • From: "Stephan Assmus" <superstippi@xxxxxx>
  • To: haiku-appserver@xxxxxxxxxxxxx
  • Date: Mon, 4 Jul 2005 11:50:45 +0200 (MEST)

Hi gang,

> > > The hardware detection code
> > > would have to be moved from AccelerantHWInterface to somewhere 
> > > higher up the
> > > hirarchy.
> >     Are you sure? Why?
> Yeah, why? :-))

I was thinking of multiple graphics cards. If AccelerantHWInterface is to
stay with using one Accelerant, and not multiple, then someone higher up the
hirarchy has to tell the AccelerantHWInterface which Accelerant to use. Ie,
there would be an entity, that finds all suitable Accelerants and
instantiates an AccelerantHWInterface for each one (also a PhysicalScreen
object for each). The other way is too confusing: AccelerantHWInterface
would manage different accelerants... no way, it gives me a headache
already... :-)

I think VirtualScreen might not be necessary, only MultiplexingDisplayDriver
is. Well, VirtualScreen could be nothing more than the entity managing the
screen layout and be the container for PhysicalScreen objects. The
MultiplexingDisplayDriver could be hooked up to VirtualScreen and use that
for the information where each PhysicalScreen is and which
DisplayDriverPainter to use for which area.

Best regards,

Weitersagen: GMX DSL-Flatrates mit Tempo-Garantie!
Ab 4,99 Euro/Monat: http://www.gmx.net/de/go/dsl

Other related posts: