Thread: [BadWM-devel] startup stuf in configs
Status: Beta
Brought to you by:
ran_at
Menu
▾
▴
badwm-devel
|
From: Alexander K. <god...@bk...> - 2004-10-04 13:04:25
|
Hi all, I was thinking about the startapp config option and i figured out how to implement this :) In netwm spec iv'e readed about _NET_WM_DESKTOP property for every client window and i have implemented it, it's working like: Then creating a client, we set this property to the clients win for later use, for example my pager uses this atom to get the desktop which we need to plot the clients representation on. So we just need to set this atom on the newly created window then we starting apps from the config file. I will try to make this real today. -- Best Regards, Alexander Kremer. |
|
From: Alexander K. <god...@bk...> - 2004-10-04 14:12:41
|
Ok, Now i understand why it's not THAT simple :) Where is a startapp option now, it parses the vdesk and the cmd now, but it uses spawn, and spawn don't support setting the desktop. The problem here is that the window self is created after parsing the configs, it's made by a event, and the event don't know about the vdesk we wanted so much. What can we do? we can implement a startapp mechanism, it should remember all the parameters we had specified in the configs and then after all it shell start the apps, however, make_new_client have now 3 arguments where the last one is vdesk. i have no more ideas :( Berney, please help :) On Mon, Oct 04, 2004 at 05:02:04PM -0300, Alexander Kremer wrote: > Hi all, > > I was thinking about the startapp config option and i figured out how to implement this :) > In netwm spec iv'e readed about _NET_WM_DESKTOP property for every client window and i have implemented it, it's working like: > Then creating a client, we set this property to the clients win for later use, for example my pager uses this atom to get the desktop which we need to plot the clients representation on. > So we just need to set this atom on the newly created window then we starting apps from the config file. > > I will try to make this real today. > > -- > Best Regards, > Alexander Kremer. > > > ------------------------------------------------------- > This SF.net email is sponsored by: IT Product Guide on ITManagersJournal > Use IT products in your business? Tell us what you think of them. Give us > Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more > http://productguide.itmanagersjournal.com/guidepromo.tmpl > _______________________________________________ > BadWM-devel mailing list > Bad...@li... > https://lists.sourceforge.net/lists/listinfo/badwm-devel -- Best Regards, Alexander Kremer. |
|
From: <2b...@se...> - 2004-10-05 11:52:48
|
Hi, I think that this isn't thing that BadWM should do. - all that I have written are just some ideas and they don't have to be true - It may be a good idea to leave BadWM without ability to create windows at startup. Because there is something called session manager - it may be able to it instead of window manager. http://csrc.nist.gov/publications/nistpubs/800-7/node74.html I guess that it is what we need. Since BadWM is able to use _NET atoms (tanks Alex) it may be possible to use any other standart session manager together with BadWM. The problem is how to identify window - executed program. :-) I'll try to use the source and look. Berny > Ok, > > Now i understand why it's not THAT simple :) > Where is a startapp option now, it parses the vdesk and the cmd now, but it uses spawn, and spawn don't support setting the desktop. > The problem here is that the window self is created after parsing the configs, it's made by a event, and the event don't know about the vdesk we wanted so much. > What can we do? we can implement a startapp mechanism, it should remember all the parameters we had specified in the configs and then after all it shell start the apps, however, make_new_client have now 3 arguments where the last one is vdesk. > > i have no more ideas :( > Berney, please help :) > > On Mon, Oct 04, 2004 at 05:02:04PM -0300, Alexander Kremer wrote: > > Hi all, > > > > I was thinking about the startapp config option and i figured out how to implement this :) > > In netwm spec iv'e readed about _NET_WM_DESKTOP property for every client window and i have implemented it, it's working like: > > Then creating a client, we set this property to the clients win for later use, for example my pager uses this atom to get the desktop which we need to plot the clients representation on. > > So we just need to set this atom on the newly created window then we starting apps from the config file. > > > > I will try to make this real today. > > > > -- > > Best Regards, > > Alexander Kremer. > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: IT Product Guide on ITManagersJournal > > Use IT products in your business? Tell us what you think of them. Give us > > Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more > > http://productguide.itmanagersjournal.com/guidepromo.tmpl > > _______________________________________________ > > BadWM-devel mailing list > > Bad...@li... > > https://lists.sourceforge.net/lists/listinfo/badwm-devel > > -- > Best Regards, > Alexander Kremer. > > > ------------------------------------------------------- > This SF.net email is sponsored by: IT Product Guide on ITManagersJournal > Use IT products in your business? Tell us what you think of them. Give us > Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more > http://productguide.itmanagersjournal.com/guidepromo.tmpl > _______________________________________________ > BadWM-devel mailing list > Bad...@li... > https://lists.sourceforge.net/lists/listinfo/badwm-devel |
|
From: Alexander K. <god...@bk...> - 2004-10-05 13:55:46
|
Hi. Maybe you are right, maybe we just need to get a session manager working. Session manager is smf like KDM, XDM, GDM? if so, it suck, and i dont use it, but i will if it's usefull :) Berney, give me your icq so we can talk about it. On Tue, Oct 05, 2004 at 01:52:39PM +0200, Bernard Lidicky wrote: > Hi, > I think that this isn't thing that BadWM should do. > - all that I have written are just some ideas and > they don't have to be true - > > It may be a good idea to leave BadWM without ability to create windows > at startup. Because there is something called session manager - it > may be able to it instead of window manager. > > http://csrc.nist.gov/publications/nistpubs/800-7/node74.html > > I guess that it is what we need. Since BadWM is able to use > _NET atoms (tanks Alex) it may be possible to use any other > standart session manager together with BadWM. > > The problem is how to identify window - executed program. :-) > I'll try to use the source and look. > > Berny > > > Ok, > > > > Now i understand why it's not THAT simple :) > > Where is a startapp option now, it parses the vdesk and the cmd now, but it uses spawn, and spawn don't support setting the desktop. > > The problem here is that the window self is created after parsing the configs, it's made by a event, and the event don't know about the vdesk we wanted so much. > > What can we do? we can implement a startapp mechanism, it should remember all the parameters we had specified in the configs and then after all it shell start the apps, however, make_new_client have now 3 arguments where the last one is vdesk. > > > > i have no more ideas :( > > Berney, please help :) > > > > > > > On Mon, Oct 04, 2004 at 05:02:04PM -0300, Alexander Kremer wrote: > > > Hi all, > > > > > > I was thinking about the startapp config option and i figured out how to implement this :) > > > In netwm spec iv'e readed about _NET_WM_DESKTOP property for every client window and i have implemented it, it's working like: > > > Then creating a client, we set this property to the clients win for later use, for example my pager uses this atom to get the desktop which we need to plot the clients representation on. > > > So we just need to set this atom on the newly created window then we starting apps from the config file. > > > > > > I will try to make this real today. > > > > > > -- > > > Best Regards, > > > Alexander Kremer. > > > > > > > > > ------------------------------------------------------- > > > This SF.net email is sponsored by: IT Product Guide on ITManagersJournal > > > Use IT products in your business? Tell us what you think of them. Give us > > > Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more > > > http://productguide.itmanagersjournal.com/guidepromo.tmpl > > > _______________________________________________ > > > BadWM-devel mailing list > > > Bad...@li... > > > https://lists.sourceforge.net/lists/listinfo/badwm-devel > > > > -- > > Best Regards, > > Alexander Kremer. > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: IT Product Guide on ITManagersJournal > > Use IT products in your business? Tell us what you think of them. Give us > > Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more > > http://productguide.itmanagersjournal.com/guidepromo.tmpl > > _______________________________________________ > > BadWM-devel mailing list > > Bad...@li... > > https://lists.sourceforge.net/lists/listinfo/badwm-devel > > > ------------------------------------------------------- > This SF.net email is sponsored by: IT Product Guide on ITManagersJournal > Use IT products in your business? Tell us what you think of them. Give us > Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more > http://productguide.itmanagersjournal.com/guidepromo.tmpl > _______________________________________________ > BadWM-devel mailing list > Bad...@li... > https://lists.sourceforge.net/lists/listinfo/badwm-devel -- Best Regards, Alexander Kremer. |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X