Moose-dev November 2014

moose-dev@list.inf.unibe.ch

42 participants
98 discussions

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

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

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

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

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

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

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

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

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, 1 month

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, 1 month

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev November 2014