On 5/18/06, Yen-Ju Chen <[EMAIL PROTECTED]> wrote:
A single class is fine. It is just a C-to-ObjC translation of x window functions. But why not to be more object-oriented ?
oh well it's just that most of the things are operations on a "workspace" (eg we ask the workspace to do something for us), so I was thinking it would be easier for developers to have just one "public" class to do that. Doesn't prevent us to have more behind-the-scene classes to implement that neatly in proper OO fashion.
And GNUstep is abstract from backend already. That's why we need a WindowManagerKit to access x window now. :) If we add another layer of abstract, it is just redundant in my own opinions.
Not really -- GNUstep is indeed abstracted from X, but here we're not using GNUstep methods : we want to ask for specific actions at the workspace level.. And those actions are not in gnustep, hence WindowManagerKit. As they are not in GNUstep, well, they obviously are not abstracted. So that's why we need to abstract them, so eg if you use WindowManagerKit, it will work the same from the application developer's point of view if it runs on X11 or on another display system such as DirectFB. I don't think it's redundant, but I'm perhaps missing something. -- Nicolas Roard "I love deadlines. I like the whooshing sound they make as they fly by." -- Douglas Adams _______________________________________________ Etoile-dev mailing list [email protected] https://mail.gna.org/listinfo/etoile-dev
