From: Alexander F. <Ale...@gm...> - 2000-12-10 17:35:56
|
On Thursday, 7. December 2000 18:23, Joseph WENNINGER wrote: > -----Ursprüngliche Nachricht----- > Von: kre...@li... > [mailto:kre...@li...]Im Auftrag von > Alexander Feigl > Gesendet: Donnerstag, 07. Dezember 2000 12:57 > An: kre...@li... > Betreff: Re: [Kreatecd-devel] RFC: Wizards in kreateCD > > > Am Mittwoch, 6. Dezember 2000 21:25 schrieben Sie: > > [....] > --SNIP.-- > > >Hmm. We would have to check whether an instace of KreateCD is already > > running > >and communicate through DCOP to add the track to the running instance. We > >would have to make KreateCD DCOP-aware first. I am right? > > Yes, I would suggest a small wrapper, which starts kreatecd and sets the > menu entries in the service menu, for adding a new sesssion, adding to > session or starting kreateCD + creating a new track / session. (Wrapper > <--> kreatecd with DCOP). Hmm. You mean we need two binaries to do this? What are the disadvantages when we do everything in one binary? Or do we have to run the wrapper all the time so support these service menus? > The only problem at the moment could be with dcop > communication between different users. > I think kreateCD needs to run as root, while the wrapper runs as another > user. (I'm talking to some kde-core-developers about this problem at the > moment) I still prefer the current handling of root operation. The most time KreateCD runs as the user which has started KreateCD. Only when we need access to the CD burner we regain root access. We don't need DCOP when we are in "root mode" so I don't know whether there is any problem. -- Linux is like a Wigwam : no Gates, no Windows but an Apache inside My Homepage : http://www.moondream.de KreateCD Homepage : http://wwww.moondream.de/kreatecd/ |