Re: WM Spec Purpose, etc.



> > > I meant like for GNOME applications, you have a desktop file which tells
> > > you a bit about the application. Something similar to tell you what the
> > > config tool name is, what the name of the WM binary is, what the name of
> > > the window manager is, perhaps the WM author & email address, maybe some
> > > other things about how it behaves on non-configurable issues.
> >
> > Sorry, I misunderstood you. I think the idea of a .desktop (or whatever)
> > file for window manager config tools makes much more sense than a big
> > complex IPC interface.
> >
> 
> What I was referring more to is how GNOME or KDE will know certain pieces
> of info about the WMs and the WM config tool, not so much as the config
> tool talking to the WM. In my opinion, the config tools should be written
> by the people writing the WM. They can use CORBA, IPC, whatever they want,
> as long as it gets the job done and deals with at least (X) particular
> options.

I agree. A central configuration tool would be nice, but I think it would
be tricky to implement and would probably not be missed by most people. A
central "jumping off point" to existing config tools is enough.


Michael Rogers




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]