Moose-dev

moose-dev@list.inf.unibe.ch

6630 discussions

Issue 1046 in moose-technology: TextPresentation should update rendering when text port is populated

by moose-technology＠googlecode.com

Status: New Owner: tu...(a)tudorgirba.com Labels: Type-Defect Priority-Medium Component-Glamour Milestone-5.0 New issue 1046 by tu...(a)tudorgirba.com: TextPresentation should update rendering when text port is populated http://code.google.com/p/moose-technology/issues/detail?id=1046 This should update the rendering to '42': composite := GLMCompositePresentation new with: [:a | a text ]. composite openOn: 'fourtytwo'. composite first text: '42'. -- 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, 1 month

Issue 981 in moose-technology: Glamour should provide a means to not transmit all Roassal clicks

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium Component-Glamour Milestone-5.0 New issue 981 by tu...(a)tudorgirba.com: Glamour should provide a means to not transmit all Roassal clicks http://code.google.com/p/moose-technology/issues/detail?id=981 Originally reported on stackoverflow: http://stackoverflow.com/questions/18829093/make-edges-not-clickable-in-roa… In the below example, you need to uncomment the two lines to work around this issue. We need a better solution. browser := GLMTabulator new. browser column: #myRoassal ; column: #mySelection. browser transmit to: #myRoassal ; andShow: [ : aGLMPresentation | aGLMPresentation roassal painting: [ : view : numbers | |edges| view shape rectangle ; withText ; size: 30. view nodes: numbers. view interaction noPopup. view edges: numbers from: [ :x | x / 2] to: [ :x | x ]. " view edges do: [ :edge | edge model:#doNotSelectMe ]." view treeLayout. ]. ]. browser transmit to: #mySelection ; from: #myRoassal ; " when: [ :selection | selection ~= #doNotSelectMe ] ;" andShow: [ : aGLMPresentation | aGLMPresentation text display: [ : selectedItem | selectedItem asString ] ]. browser openOn: (1 to: 10). -- 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, 1 month

Re: Issue 890 in moose-technology: All meta-entities should have a class comment

by moose-technology＠googlecode.com

Updates: Summary: All meta-entities should have a class comment Comment #1 on issue 890 by tu...(a)tudorgirba.com: All meta-entities should have a class comment http://code.google.com/p/moose-technology/issues/detail?id=890 (No comment was entered for this change.)

10 years, 1 month

What has changed in Mondrian/Roassal2.

by volkert＠nivoba.de

Dear All, i am using heavily Mondrian (ROMondrianViewBuilder) from Roassal1 in my Tool/Project. Today i tried to migrate my work to Roassal2 and found out, that the Interface of RTMondrianViewBuilder has changed a lot. Is there a list what has changed/what was removed/what are the alternatives/...? Some examples view := ROMondrianViewBuilder *titled*: 'asdasd'. view shape rectangle *withText*: #shortName; *textVerticalPadding*: -10; *fontSize*: 6. view *addMenu*: 'Zoom in' callBack: [ :stack | … ]. Anther question: How can i change the line thickness of a Mondrian Node? I find the default size is to thick. BW, Volkert

10 years, 1 month

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

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

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

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

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

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

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev