- Moose-dev - INF Mailman

Re: [Pharo-dev] editing the default window size of glamour inspector

by Nicolai Hess

2014-11-12 15:14 GMT+01:00 Clément Bera <bera.clement(a)gmail.com>: > Hello, > > I would like for specific objects to change the default window size of the > glamour inspector (Basically a bigger window will be opened by default for > these objects). This is because I extended my inspectors to provide roassal > visualization that are quite large. > > How can I do it ? > > For example I would like something like that: > > MyObject>>#gtInitialWindowExtent > < gtInitialWindowExtent > > ^ 800@1000 > > Clement > > I think this is not doable. You can change the method with the inspector pragma to be called with the context (inspector instance) gtInspectorItemsIn: composite inContext: aGTInspector <gtInspectorPresentationOrder: 30> instead of gtInspectorItemsIn: composite <gtInspectorPresentationOrder: 30> this way you have access to the glamour inspector. Unfortunately it does not have any window extent property. Maybe we can move the initialExtent property from GLMBrowser up to GLMPresentation? That way it would be accessible and usable for this aGTInspector argument. Nicolai

10 years, 7 months

3
2
0 0

Pharo and Categories Importer update

by Gustavo Santos

Hello, I have noticed that the Category Importer was removed from Moose. I've been using the Pharo Importer instead, but there are some information missing in the model it generates (e.g., the parent package of a method). This information is important for the project I'm working on (Orion). So, I made commit of the missing code in order to make Orion tests pass again. Does it make sense to commit on Moose to make PharoImporter work as CategoriesImporter was working before? Regards, -- Gustavo Santos

10 years, 7 months

2
3
0 0

Issue 1098 in moose-technology: Roassal Presentatnio should offer SVG export

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Glamour Milestone-5.0 New issue 1098 by tu...(a)tudorgirba.com: Roassal Presentatnio should offer SVG export https://code.google.com/p/moose-technology/issues/detail?id=1098 Just that. -- 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

10 years, 7 months

1
1
0 0

Extension in GT

by Alexandre Bergel

Hi Milton, It would be great to have an export SVG and export HTML accessible from GT Inspector. The starting point is the method GLMRoassal2Presentation >> defaultActions Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

10 years, 7 months

2
1
0 0

Menu in Roassal are not pretty

by Alexandre Bergel

This is a recurrent complain. We have to improve the menus… Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

10 years, 7 months

1
0
0 0

About RBCompiler

by Serge Stinckwich

I'm trying to port QuasiQuote package from Lukas Renggli to Pharo 3.0/4.0. This package use the RBCompiler class from the AST-Compiler package available here: http://source.lukas-renggli.ch/helvetia If I understand RBCompiler, this is a Compiler that use RB parser nodes. I guess this is something that is no more relevant with the new Opal compiler ? -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

10 years, 7 months

2
3
0 0

Kiviat support in Roassal

by Alexandre Bergel

Hi! Pierre just finished a first version of Kiviat in Roassal. Here are some example: -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= b := RTKiviatBuilder new. b objects: RTAbstractCircleLayout withAllSubclasses. n := RTMultiLinearColorForIdentity new objects: (b objects). b shape circle color: [ :value | n rtValue: value named]; size: 10. b addMetric: #numberOfLinesOfCode. b addMetric: #numberOfMethods. b addMetric: #numberOfVariables. b activatePolygons. b build. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-= It would be great to have feedback on this! Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

10 years, 7 months

5
6
0 0

Caveat Example added

by Alexandre Bergel

Hi! I migrated some of Pierre's example into the GT-based browser: Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

10 years, 7 months

1
0
0 0

Re: Why extra configurations for GT

by Stephan Eggermont

Doru wrote: >On Fri, Nov 21, 2014 at 11:39 AM, Stephan Eggermont <[hidden email]> wrote: >>Why are there extra configurations for GT? > >Because we will go away from groups and because we needed to have the tools loadable individually. Why do you want to go away from groups? Tools can be loaded individually with groups. >I'm afraid that leads to duplication of effort, > >Why? Because there is already lots of duplication in those separate configurations. >>and introduces lots of problems. > >What kind of problems? missing updates. Basically no DRY >>Moose was nearly loading in Pharo 4, >>the only thing that went wrong was the loading of fonts. > >Where is the difference now? missing groups Stephan

10 years, 7 months

1
0
0 0

ConfigurationOfGlamour broken, needs CoreExtras group

by Stephan Eggermont

The removal of the CoreExtras group is a change that needs to propagate to all configurations using Glamour (or be undone). It is a change to the public API. It currently breaks loading Moose in Pharo 4 Stephan

10 years, 7 months

2
1
0 0

Why extra configurations for GT

by Stephan Eggermont

Why are there extra configurations for GT? I'm afraid that leads to duplication of effort, and introduces lots of problems. Moose was nearly loading in Pharo 4, the only thing that went wrong was the loading of fonts. Stephan

10 years, 7 months

2
1
0 0

using FAMIX in Pharo 4

by Peter Uhnák

Hi, is it possible to use FAMIX model in Pharo 4 (=not Moose image)? I didn't find a separate configuration and loading the whole Moose package fails (probably because Moose image is on Pharo 3?). Thanks, Peter

10 years, 7 months

2
2
0 0

allParsersDo:seen: error while using PetitParser

by Anne Etien

Hi, We are using PetitParser and we get this error message. But it is not very explicit and even while using PetitParser browser we get this issue. The problem is that even while testing the parsing of a subpart of the erroneous test with another test, we get the error. Does someone knows what this error means and what to do to correct it? Thanks in advance. Anne

10 years, 7 months

2
2
0 0

Roassal2 and edges

by jannik laval

Hi Alex, I have some problems with displaying edges. I have difficulties to reproduce things outside my application. But I am trying to add arrows. So when I do: (RTLine new color: Color red) + (RTSimpleArrowHead new color: Color red), the text that follow the + brake my visualization: the arrow is wrongly placed. If I remove the + (RTSimpleArrowHead new color: Color red), it works fine. When I tried to reproduce it, I created an example that does not work, I do not understand why: === b := RTGraphBuilder new. shape := RTShapeBuilder new. shape shape: (RTEllipse new color: Color gray; size: 40). el := (RTElement on: 1). el + shape. b view add: el. el2 := (RTElement on: 2). el2 + shape. b view add: el2. l := RTEdge from: el to: el2. b view add: l. RTCellLayout on: b view elements. b build. b open === -- ~~Jannik Laval~~ École des Mines de Douai Enseignant-chercheur http://www.jannik-laval.eu http://www.phratch.com http://www.approchealpes.info http://car.mines-douai.fr/

10 years, 7 months

2
2
0 0

humane assessment example

by Alexandre Bergel

Hi! We have improved the coverage of RTView. Hapao helps a lot! https://www.facebook.com/ObjectProfile/photos/a.341189379300999.82969.34054… <https://www.facebook.com/ObjectProfile/photos/a.341189379300999.82969.34054…> Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

10 years, 7 months

2
1
0 0

Issue 1095 in moose-technology: PlayGround directory cache bug

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-GlamorousToolkit New issue 1095 by anquetil...(a)gmail.com: PlayGround directory cache bug https://code.google.com/p/moose-technology/issues/detail?id=1095 opening on a computer an image coming from another computer When typing anything in the PlayGround, there is an exception (see attached). work areounf: go in System > Settings > GlamourousToolkit > LocalPlaygroundCacheDirectory and set it to a directory on local disk Attachments: Screenshot from 2014-11-03 16:41:02.png 141 KB -- 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

10 years, 7 months

2
3
0 0

another GTPlayground problem

by Esteban Lorenzano

“tab” is broken :( Esteban

10 years, 7 months

2
2
0 0

Fwd: Re: RTPNGExporter - review needed

by Nicolai Hess

Am 14.11.2014 00:57 schrieb "Chris Cunningham" <cunningham.cb(a)gmail.com>: > > Nah, morphic works. What you do is have it write to a canvas big enough to hold the drawing, then get the form under it, and then save that out. So, something like this in the morph: > > asForm > | canvas | > canvas := FormCanvas extent: self extent. > self drawOn: canvas. > ^canvas contentsOfArea: bounds > > and write it out with: > > PNGReadWriter putForm: morph asForm onFileNamed: 'someFileName.png' > > I've used this with rediculously large diagrams before. > > -chris Yes, pure morphic. But rendering the above Diagramm in a morphic window and with Athens (and therefore Cairo) only works, because it only renders the visible part. If you have a display with >32k width or hight, you would suffer from the same Problem.

10 years, 7 months

3
2
0 0

latest GTPlayground ignoring DarkTheme colorisation

by Esteban Lorenzano

Hi, So… someone is hardcoding the shout theme… something in Rubric, perhaps? But well… playground became non-usable for me :( cheers, Esteban ps: the timestamp as title is also ugly. I propose to just remove that title. Is useless anyway (toolbar icons can be replaced by a menu/toolbar for window, no need of a pane with an unique tab there). pps: the menu options are arbitrary in his relevancy and I still miss some of the options (already reported) ppps: lots of uncategorised methods in GLMMorphicPharoPlaygroundRenderer and around pppps: got it, RubSHTextStylerST80 does not respect style, and uses always default style (that’s obviously not cool :p).

10 years, 7 months

3
2
0 0

Issue 816 in moose-technology: MooseMetaBrowser's Map re-display after selection of a node

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-MooseCore New issue 816 by anquetil...(a)gmail.com: MooseMetaBrowser's Map re-display after selection of a node http://code.google.com/p/moose-technology/issues/detail?id=816 In the Moose MetaBrowser, when selecting a node in the Map, this map is redisplayed at a new location which can even hide the selected node. How to reproduce the problem: - open MetaBrowser - the map (drawing) must be larger than the Map panel - scroll to the right of the map - select a node (at the right) - the map is redisplayed scrolled back to its initial position (full left) Same thing happens vertically (scroll down, select a node down, map is redisplayed from top)

10 years, 7 months

1
10
0 0

Issue 1003 in moose-technology: The treemap builder should offer a default weight of 1

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium Component-Roassal Milestone-5.0 New issue 1003 by tu...(a)tudorgirba.com: The treemap builder should offer a default weight of 1 http://code.google.com/p/moose-technology/issues/detail?id=1003 Right now, the weight block has to be specified. Instead, we should have a default weight of 1. Furthermore, right now, if the weight returns 0 (like above), we get a ZeroDivide. Zero should be handled without an error. -- 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

10 years, 7 months

1
2
0 0

Re: Issue 674 in moose-technology: Bullet graphs in Graph-ET

by moose-technology＠googlecode.com

Updates: Summary: Bullet graphs in Graph-ET Labels: -Component-EyeSee Comment #2 on issue 674 by tu...(a)tudorgirba.com: Bullet graphs in Graph-ET http://code.google.com/p/moose-technology/issues/detail?id=674 I changed the topic to be related to Graph-ET :) -- 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

10 years, 7 months

1
1
0 0

Issue 514 in moose-technology: Introduce the PharoImageSourceAnchor

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-SmalltalkImporter Component-Famix New issue 514 by tudor.gi...(a)gmail.com: Introduce the PharoImageSourceAnchor http://code.google.com/p/moose-technology/issues/detail?id=514 Currently, FAMIXClass>>sourceText has a hack that checks for mooseModel isSmalltalk explicitly. We should introduce a PharoImageSourceAnchor that properly takes care of this.

10 years, 7 months

1
1
0 0

Re: Issue 393 in moose-technology: Interactive sort of table widget by columns

by moose-technology＠googlecode.com

Updates: Cc: simon.de...(a)gmail.com tudor.gi...(a)gmail.com Comment #1 on issue 393 by tu...(a)tudorgirba.com: Interactive sort of table widget by columns http://code.google.com/p/moose-technology/issues/detail?id=393 Issue 156 has been merged into this issue. -- 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

10 years, 7 months

1
1
0 0

Issue 973 in moose-technology: Roassal font organizer singleton inconsistencies

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 973 by benjamin...(a)gmail.com: Roassal font organizer singleton inconsistencies http://code.google.com/p/moose-technology/issues/detail?id=973 Following on from Issue 971, use of singletons related to the Roassal font organizer seems not used consistently. Using Finder, I've searched all 'Source' of Roassal packages, for the following both 'ROFontOrganizer' and 'fontOrganizerClass' and found... ----Part1-------------- ROAbstractLabel >> fontFor: anElement with: aCamera fo := ROPlatform current fontOrganizerClass. ROAbstractLabel >> offsetWhenDrawing ^ ROPlatform current fontOrganizerClass ROAbstractLabel >> widthOfLine: string withFont: aFont ^ ROFontOrganizer current widthOfString: string font: font. I propose the last is changed to... ROAbstractLabel >> widthOfLine: string withFont: aFont ^ ROPlatform current fontOrganizerClass widthOfString: string font: font. and also delete... ROFontOrganizer >> current ^ self subclasses first which seems plain wrong. ----Part2-------------- Also I'm a perplexed by the way both of these methods ROMorphicPlatform>>fontOrganizerClass ^ ROFontOrganizerMorphic ROPharoAthensPlatform>>fontOrganizerClass ^ ROFontOrganizerAthens override this one ROPlatform>>fontOrganizerClass ^ fontOrganizerClass such that the instance-variable 'fontOrganizerClass' is ignored, as well as the following seeming irrelevant... ROPlatform>>fontOrganizerClass: ^ fontOrganizerClass := aClass. Is ROPlatform ever instantiated, or abstract? A search for all references to 'ROPlatform' in the 'Source' of all Roassal finds... * ROPlatform current (x40) * ROPlatform platforms (x2) * ROPlatform removeNamed: (x1) * ROPlatform add: (x2) * ROPlatform setCurrent: (x1) * ROPlatform new (x1) The last is only in a test ROPlatformTest>>testAddingAPlatform. I propose to modify... ROPlatform>>fontOrganizerClass self subclassResponsibility delete.... fontOrganizerClass instance-variable delete... ROPlatform>>fontOrganizerClass: from... ROPlatformTest>>testAddingAPlatform remove line... platform fontOrganizerClass: ROFontOrganizer subclasses anyOne. hope this helps, cheers -ben -- 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

10 years, 7 months

1
5
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev