Robert, I agree that this is a conundrum. :) We are facing the same decision that had to be made for OpenStep on Windows.
I really believe that we should choose an approach similar to the one that NeXT took at that point. I would be very skeptical of an MDI based approach, but I might be open to providing it as an option, if someone can show me that it's a viable approach for GNUstep apps. What concerns me about MDI are the modifications that would be necessary in the backend to support it... as well as possible impacts on the API to accommodate the concepts having subwindows (which MDI uses) would introduce. Later, Gregory Casamento -- Principal Consultant - OLC, Inc # GNUstep Chief Maintainer ________________________________ From: Robert J. Slover <[email protected]> To: Richard Frith-Macdonald <[email protected]> Cc: "[email protected]" <[email protected]> Sent: Monday, January 19, 2009 6:12:02 PM Subject: Re: Impelmenting NSWindows95InterfaceStyle I agree. However, on Windows, I'd expect the menu to be attached to an MDI window containing the other open windows (if any) when it has no other natural home. --Robert >>> >> >> >> >> >> >> >> > The main problem is that it's not much like the way mswindows behaves ... we > want to implement an NSWindow95InterfaceStyle for our main menu which makes > our apps behave like mswindows apps. An application programmer may well want > (and be allowed) to control things (eg preventing the main window from > appearing in certain windows and terminating the app when they want to) but > the default behavior of the application should be like mswindows, with the > main menu displayed inside every eligible window and the app being terminated > if there is no eligible widow. _______________________________________________ Discuss-gnustep mailing list [email protected] http://lists.gnu.org/mailman/listinfo/discuss-gnustep
_______________________________________________ Discuss-gnustep mailing list [email protected] http://lists.gnu.org/mailman/listinfo/discuss-gnustep
