Moose-dev March 2011

moose-dev@list.inf.unibe.ch

24 participants
119 discussions

Issue 541 in moose-technology: Create an initial Moose help :)

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium Component-MooseCore New issue 541 by tudor.gi...(a)gmail.com: Create an initial Moose help :) http://code.google.com/p/moose-technology/issues/detail?id=541 We should have a Moose help entry in ProfStef. The idea is to pick some existing pieces of text from the webpage and the book.

13 years, 11 months

Issue 547 in moose-technology: integrate fuel in ConfigurationOfMoose

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium Milestone-4.4 New issue 547 by jannik.l...(a)gmail.com: integrate fuel in ConfigurationOfMoose http://code.google.com/p/moose-technology/issues/detail?id=547 Gofer new squeaksource: 'Fuel'; package: 'ConfigurationOfFuelMooseExtension'; load. (Smalltalk at: #ConfigurationOfFuelMooseExtension) perform: #load

13 years, 11 months

Issue 494 in moose-technology: Dynamic presentation should be a browser

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium Component-Glamour Milestone-4.3 New issue 494 by tudor.gi...(a)gmail.com: Dynamic presentation should be a browser http://code.google.com/p/moose-technology/issues/detail?id=494 The problem is that when in a presentation we ask for entity, we get the value of the entity of the pane around the dynamic presentation, instead of the transformed value.

13 years, 11 months

Issue 510 in moose-technology: Introduce Port>>transientValue:

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium Component-Glamour New issue 510 by tudor.gi...(a)gmail.com: Introduce Port>>transientValue: http://code.google.com/p/moose-technology/issues/detail?id=510 We should be able to set the value of a port only temporarily. This would be useful for triggering other transmissions. For example, to implement a search like behavior we could use the code from below. The problem is that if you press the search icon once, then change the selection manually, and then press the button again, the selection will not change because the #focusOne port did not change the value. |browser | browser := GLMTabulator new. browser act: [:b | (b pane port: #focusOne) value: 3 ] icon: MooseIcons mooseSearch entitled: 'Search'. browser column: #one; column: #two. browser transmit to: #one; andShow: [ :a | a tree display: [:x | 1 to: x]]. browser transmit to: #two; from: #one; andShow: [ :a | a tree display: [:x | 1 to: x*2]]. browser transmit to: #one port: #selection; fromOutsidePort: #focusOne. browser openOn: 3

13 years, 11 months

Issue 540 in moose-technology: Glamour: removing dependency in configuration - core group

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 540 by vuqui...(a)vub.ac.be: Glamour: removing dependency in configuration - core group http://code.google.com/p/moose-technology/issues/detail?id=540 In the configuration of Glamour, the core group was loading only Glamour packages, and the extras group: mondrian and magritte presentations. This allowed to load those presentations if needed. Currently, the core group is also depending on Mondrian. The method MOViewRenderer>>openWithStatusbar is causing this dependency in the package Glamour-Scripting. Can this dependency be removed from the group core? * Type-Enhancement * Component-Glamour

13 years, 11 months

Re: Issue 448 in moose-technology: MOEaselTextEditor contains many methods that are never called

by moose-technology＠googlecode.com

Comment #1 on issue 448 by tudor.gi...(a)gmail.com: MOEaselTextEditor contains many methods that are never called http://code.google.com/p/moose-technology/issues/detail?id=448 Is this still a problem? And what is /branches/?

13 years, 11 months

Re: Issue 460 in moose-technology: scaleBy: should be in shapes, and not in MONode

by moose-technology＠googlecode.com

Updates: Labels: Component-Mondrian Comment #1 on issue 460 by jannik.l...(a)gmail.com: scaleBy: should be in shapes, and not in MONode http://code.google.com/p/moose-technology/issues/detail?id=460 (No comment was entered for this change.)

13 years, 11 months

Re: Issue 446 in moose-technology: uml class shape aligned the rectangles

by moose-technology＠googlecode.com

Updates: Status: Accepted Labels: -Priority-Medium Priority-High Comment #4 on issue 446 by tudor.gi...(a)gmail.com: uml class shape aligned the rectangles http://code.google.com/p/moose-technology/issues/detail?id=446 A form of the problem is still around. This is an important issue that prevents us from actually using the FormsBuilder. Here is an example with a ChildrenShape inside. The green shape on top should have a constant minimum size. Instead its height increases together with the height of the children shape below: | builder | builder := MOFormsBuilder new. builder column; fill. builder row; fill; row; fill. builder x: 1 y: 1 add: (MORectangleShape new width: 30; fillColor: Color green). builder x: 1 y: 2 add: (MORectangleShape new). builder x: 1 y: 2 add: (MOChildrenShape new). view shape: builder shape. view nodes: (1 to: 5) forEach: [:each | view nodes: (1 to: each). view verticalLineLayout ]

13 years, 11 months

Problem worth working on

by Alexandre Bergel

Hi! Since some of you are working on remodularizing code, maybe the following may inspire you. In Mondrian, the tests are badly structured. I actually wrote a large part of them as a way for me to understand the initial version of Mondrian, back in 2007-2008. Most of the tests are contained in the class MOViewRendererTest. They actually contain a lot of duplicated scenario (not really code): I open a canvas, put some nodes and edges, run the layout... I would like to cut this class into smaller unit tests. Fixture will have to be found for each new unit tests. How to structure them? Along the class hierarchy? Along the features of Mondrian? Along the features commonly used in Mondrian scripts (which is how they are roughly structured)? I can remodularize my tests and come up with a satisfactory design in a couple of hours. But maybe someone worked on a tool that would help me on this. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

13 years, 11 months

Mondrian bug or my fault?

by Fabrizio Perin

Hi, i got a strange behaviour from Mondrian trying to build a shape for data base tables. Basically defining a shape which contains a rectangle with a title and a children shape it happen that the rectangle containing the title have the same size of the children shape. Is it a bug or is a problem of my code? Below the code that i use, copy and paste in MOShapeSelector the tableShape method and than in a normal mondrian easel window you should be able to reproduce the same behaviour with the snippet below. By using this shape definition: tableShape | builder | builder := MOFormsBuilder new. builder column; fill; pref; grow. builder row; fill; pref; grow; row; fill; pref; grow. builder x: 1 y: 1 add: (MORectangleShape new text: [:table | table name]; fontSize: 10). builder x: 1 y: 2 add: MORectangleShape new. builder x: 1 y: 2 add: MOChildrenShape new. ^view shape: builder shape and using this visualization script: view shape tableShape. view node: (FAMIXNamedEntity new name: 'test') forIt: [ view shape rectangle. view nodes: (1 to: 20). view verticalLineLayout. ]. I got the result in the attachment. Thanks, Fabrizio

13 years, 11 months

← Newer
1
2
3
4
5
6
7
8
...
12
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev March 2011