Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 979 by benjamin...(a)gmail.com: Default window sizes for large screens http://code.google.com/p/moose-technology/issues/detail?id=979 The following should probably be pushed upstream for Pharo 3.0, but I thought it best to report here in case it is feasible to include in Moose 4.8. Let me know what you think and if needed I can submit a changeset or slice (what is the preferred method for submissions for Moose) I've got a 24 inch screen that I have been using with Moose-4.8-dev for a couple of weeks. I am finding it annoying that the Glamorous Inspector and Glamorous Debugger open to maximum full screen size. 1. For the Standard Debugger, I don't agree with making the default size bigger for bigger screens. I think the extra screen space is useful for inspectors and observing the application. Indeed, the debugger width should match the width of the System Browser, since that is the basis for the formatting of code. Matching these helps give a consistent UI feel for users. For Moose4.8/Pharo2.0 we have... NautilusWindow>>initialExtent ^ 850@600 Actually, perhaps that shouldn't be hard coded and instead be... NautilusWindow>>initialExtent ^ RealEstateAgent standardWindowExtent then for Debugger we could have something similar to this... Debugger>>initialExtent dependents size < 9 ifTrue: [^ super initialExtent]. "Pre debug window" RealEstateAgent standardWindowExtent y < 400 "a tiny screen" ifTrue: [^ super initialExtent]. ^ [ RealEstateAgent standardWindowExtent. ] on: Error do: [800@600] 2. For Glamourous Inspector I understand defaulting to maximum width is useful, but its overkill to default to the full height of the screen. So you could have... GLMMorphicRender>>open: aRenderable window := GLMMorphicWindowRenderer render: aRenderable from: self. ^ window openInWorld "removed 'maximize' from here" GTInspector>>initialExtent ^ RealEstateAgent fullscreenWindowExtent x @ RealEstateAgent standardWindowExtent y which requires also... RealEstateAgent class >> fullscreenWindowExtent ^ self maximumUsableArea insetBy: self fullscreenMargin. and... RealEstateAgent class >> fullscreenMargin ^ FullscreenMargin ifNil: [FullscreenMargin := 25] The last was copied from SystemWindow class >> fullScreenMargin which as an option can then be... SystemWindow class >> fullScreenMagin ^ RealEstateAgent fullscreenMargin 3. Glamorous Debbugger needs a bit more vertical height, so perhaps... GTDebugger >> initialExtent ^ RealEstateAgent fullscreenWindowExtent x @ RealEstateAgent fullscreenWindowExtent y * 2 // 3 -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings