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
Hi Fabrizio,
We made quite some FAMIX changes recently. All test were green,
but It can be a test coverage problem.
In the latest moose I only have
FAMIXParameterizableClass>>parameterizedTypes
<MSEProperty: #parameterizedTypes type: #FAMIXParameterizedType opposite: #parameterizableClass>
<multivalued> <derived>
^ parameterizedTypes
Do you have a sample MSE file for me exhibiting the problem?
Stephan
Hi,
Glamour now offers an integration of Graph-ET.
In the latest Moose image you can do:
GLMCompositePresentation new with: [ :c |
c graphET
chart: [:chart :interval |
(chart lineDiagram)
models: interval;
y: [ :x | x*x ] ] ];
openOn: (1 to: 10)
It requires some more polishing, but it works.
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
I made a screencast of Graph-ET :-)
It is my GSoC project and will be presented on ESUG this year.
http://www.youtube.com/watch?v=PkKNALQHa88
Any comments or suggestions to this mail.Enjoy!
- Daniel
Hi
just a short question
does FAMIX-AST forces to have the AST node subclass of a Moose entity
what is the independence of the tree? can we reuse him outside of famix and moose?
Stef
Hi,
I just generated an mse with inFamix and I got a MNU while importing the
file into the latest Moose.
Is there a newer release of inFamix I should download? Is it a know problem?
Thanks,
Fabrizio
Hi,
If you have to compare two MooseModels, we got tools for you.
We created the ConfigurationOf FamixDiff and OrionMerge.
- FamixDiff enables to do a diff between two MooseModels (or one OrionModel and a MooseModel). The result is a set of changes between the two models.
- OrionMerge takes this set of changes and creates a versioned OrionModel by applying the Orion action associated to each change. The result is thus an OrionModel corresponding to the target model of the diff, but taking less space of memory since its benefits from the way of Orion to manage model (between two versions, only the modified entities are stored. A clever system enables to access each entity whatever, it has been modified or not).
More information about Orion can be found there http://www.moosetechnology.org/tools/orion
I hope it is understandable.
So if you need to use them, please don't hesitate.
Anne
Nicolas wrote:
>did you run the tests before?
>I believe I saw some of them fail in the past ... ?
Uhm, we broke the build from 981 to 984,
but I'm not aware of earlier problems.
Stephan