Quoting Hallvar Helleseth ([EMAIL PROTECTED]): > Hey! > > Been thinking a little about how I could get a usable WM for DirectFB. I > have some questions I would like cleared if you have the time to answer. > > 1. > Is it a bad idea to give the WM a pointer to DirectFBWindow. > The WM could do pretty much anything it would like to with > the window. However is it a security issue if the WM is run by a normal user and > root puts in windows (with multi app core) ? > In the case of yes, there would have to be added a whole set of wm functions > for manipulating windows (moving/resizing/opacity/stacking/focus/etc) > and retrieving info about the window (when it moves/resizes itself, and > also if it would have a window title)
I think a method for enumeration of all present windows would help. Also a GetWindow (by id) method would give the WM access to the window, these should be restricted to the administrative cooperative level. > 2. > If DirectFB should have a WM, a window should have ways of telling which > sort of window it is (thereby determining the window border the WM might > give it). Is it an idea to store/set/get this info with > DFBWindowDescription. In addition to window type, window title and > window max/min size comes to mind which could also be stored in > DFBWindowDescription. I think we should distinguish between a window description and window properties. The description should only be used for creation and other settings like min/max size and the DFBWindowOptions would then belong to the window properties that can be get/set later on. But I'm not really sure yet so I wouldn't insist ;) > 3. > DFBWindowDescription is currently only used when initially creating a > window. Could there not be functions to IDirectFBWindow that get and set > a DFBWindowDescription to the window? The changeable things in a window description have their own methods like Resize or Move. The window capabilities is the only thing that can't be changed right now. So we would have to think about that. > 4. > Is window->SetOpacity(window, 0x00) as good as a potential window->Hide/Show() > (where the window could temporarily be removed from the stack) ? What about Dispose/Realize? Hiding a window doesn't make clear if it's surface will be destroyed (temporarily) which I would like to do with Dispose. > That's it for now. Thanks for taking the time during such beatiful days > of summer :) Thank you, too. And seize these days ;) -- Best regards, Denis Oliver Kropp .------------------------------------------. | DirectFB - Hardware accelerated graphics | | http://www.directfb.org/ | "------------------------------------------" Convergence GmbH -- Info: To unsubscribe send a mail to [EMAIL PROTECTED] with "unsubscribe directfb-dev" as subject.
