[haiku-appserver] Re: Refactoring

  • From: "Axel Dörfler" <axeld@xxxxxxxxxxxxxxxx>
  • To: haiku-appserver@xxxxxxxxxxxxx
  • Date: Tue, 05 Jul 2005 21:42:23 +0200 CEST

"Stephan Assmus" <superstippi@xxxxxx> wrote:
> > > > 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... :-)

Yes, I think that would be the best approach.

> 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.

Right, VirtualScreen/Surface wouldn't do a lot, but that's not bad - 
almost a new thing in the app_server ;-)


Other related posts: