Moose-dev November 2014

moose-dev@list.inf.unibe.ch

42 participants
98 discussions

by Christophe Demarey

Hello, I just did my first specific visualization with the GT inspector and it is very cool / powerful. As I don't know Glamour, I read the Glamour chapter in the book 'Deep into Pharo' and I tried to use #act:entitled: to display a menu for a table visualization like: composite table title: 'foo'; display: [ self associations ]; column: 'Key' evaluated: #key; column: 'Value' evaluated: #value; act: [ self halt ] entitled: 'new menu entry' I cannot display the menu. Do I miss something? Another question: Is it possible to add a menu bar with buttons to such a visualization? Thanks, Christophe.

9 years, 4 months

Glamour transmission problem with #onChangeOfPort:act:

by Guillaume Larcheveque

Hi everyone, I am realising some reusable components for synectique and i faced a strange behavior. I created a little example to show it: |tab| tab := GLMTabulator new. tab row: #test. tab transmit to: #test; andShow: [ :p | p list onChangeOfPort: #aPort act: [ :pre :input | input inspect ] ]. tab transmit from: #test; to: #test port: #aPort; transformation: [ :anything | 5 ]. tab openOn: (100 to: 150) here i expect that when i click on an element of the list, i will inspect 5 but if you try, you will see that you inspect the interval 100 to: 150 -- *Guillaume Larcheveque*

9 years, 4 months

Gradient lines

by Alexandre Bergel

Hi! Pierre did an excellent work on having gradient lines. -=-=-=-=-=-=-=-=-=-= | v elem1 elem2 edge | v := RTView new. elem1 := (RTEllipse new color: (Color blue alpha:0.3); size:20) elementOn: 1. elem2 := (RTEllipse new color: (Color red alpha:0.9); size:20) elementOn: 2. elem2 translateBy: 300@0. v add: elem1. v add: elem2. edge := RTEdge from:elem1 to:elem2. v add: (edge + (RTGradientColoredLine new colors: (Array with: (elem1 color) with: (elem2 color)); precision: 100; gradientColorShape)). v open -=-=-=-=-=-=-=-=-=-= -=-=-=-=-=-=-=-=-=-= | v elem1 elem2 edge | v := RTView new. elem1 := (RTEllipse new color: (Color red alpha:0.3); size:20) elementOn: 1. elem2 := (RTEllipse new color: (Color red alpha:0.9); size:20) elementOn: 2. elem2 translateBy: 300@0. v add: elem1. v add: elem2. edge := RTEdge from:elem1 to:elem2. v add: (edge + (RTGradientColoredLine new colors: (Array with: (elem1 color) with: (elem2 color)); precision: 100; gradientColorShape)). v open -=-=-=-=-=-=-=-=-=-= Feedback are welcomed! Pierre & Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

9 years, 4 months

Composite Shapes in Roassal

by Alexandre Bergel

Hi! The last few days I have worked a lot on the composite shapes and nesting. I would like you to report anomalies or bugs related to these issues. Amazing to see the complexity of these things. Coping with all the subtleties is quite hard. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

9 years, 4 months

Charter problem in the last version of MOOSE

by Serge Stinckwich

In the last version of MOOSE (#3266), there is a problem with Charter graphs. When you try the Charter examples in the Roassal GT examples menu, the image completely freeze ... -- Serge Stinckwich UCBN & UMI UMMISCO 209 (IRD/UPMC) Every DSL ends up being Smalltalk http://www.doesnotunderstand.org/

9 years, 4 months

Issue 1084 in moose-technology: Impossible to load an image with opened TRMorph

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: alexandr...(a)gmail.com Labels: Type-Defect Priority-High Component-Roassal New issue 1084 by guillaum...(a)gmail.com: Impossible to load an image with opened TRMorph http://code.google.com/p/moose-technology/issues/detail?id=1084 When you save an image with a TRMorph opened; it is not possible to load this image anymore. You have to do on the command line: TRMorph allInstances do: #delete to be able to open your image. -- 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

9 years, 4 months

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

9 years, 4 months

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

9 years, 4 months

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.)

9 years, 4 months

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

9 years, 4 months

← 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