Moose-dev

moose-dev@list.inf.unibe.ch

6630 discussions

by Alexandre Bergel

Hi! It is frequent to see have guard in the style “self error: ‘Have you forget to add something?’”, to indicate the end user that an API is not properly used. However, at the execution, it opens a debugger. I have the impression this is not what we want. We probably something more friendly than a full-fledged debugger. No? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

10 years, 1 month

Fwd: MalCyclesCoverage

by Alexandre Bergel

Hello, The truth is that I am not familiar with this code. I can hardly provide any justification about the result. I advice you to subscribe to the Moose mailing list (http://moosetechnology.org) Alexandre > Begin forwarded message: > > From: Bledar Aga <bledar.aga(a)students.unibe.ch> > Subject: MalCyclesCoverage > Date: November 27, 2014 at 1:09:45 PM GMT-4 > To: abergel(a)dcc.uchile.cl, alexandre.bergel(a)me.com > > Dear Prof. Bergel, > > I’m a master student at Bern University and I am working for my master thesis about dependency cycles. > > I am using your implementation of Tarjan algorithm MalCyclesCoverage (Moose) for detecting the cycles. I tried to understand your implementation but it is a bit hard to follow the execution and I can’t find the documentation. > > I want kindly to ask: Is there any reason that given a certain input it does not provide all the circuits of a strongly connected components? > > Removing the dependencies (edges) from a cyclic graph at the end I obtain the acyclic graph and this is what I want, but I need to understand how the single circuits are obtained. > > Example: > > Considering the following input: > > |tarjan| > tarjan := MalCyclesCoverage new. > tarjan nodes: #(1 2 3 4 5). > tarjan edges: #((1 3) (3 1) (1 5) (5 1) (4 1) (2 1) (2 5) (5 2) (2 3) (3 2) (3 4) (5 4)) from:#first to:#second. > tarjan run. > self halt. > > It returns the following output: ((1 3 4)(1 5) (1 5)(2 3) (1 3) (1 5 4) (2 5)). In practice there are more circuits, example (1 3 2) (1 5 2 3)...? > > To have a clear idea of the input I attached the graph. > > Thank you very much in advance for your time. > > Best regards, > Bledar Aga. > > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

10 years, 1 month

PetitParser debugger

by Anne Etien

Hi, We are using PetitParser. We get an error that we don’t understand. So we try to use PetitParser debugger. We execute the parsing using the debugger mode. We switch to PetitParser debugger. When we click on the ‘proceed’ button, the error is raised but we are no more in the PetitParser debugger but in the classic one. So we have no way to know the incriminated rule. And when we execute step by step the parsing, it is the same problem, when the error arises, the debugger switch back to the normal one. However, the idea is to use the debugger when we get an error in order to understand from where it comes from. So it would be great that it remains in the PetitParser debugger despite the error. Any idea how to remain in the PetitParser debugger? Anyone gets the same issue? Thanks in advance for your help. Jean-Christophe et Anne

10 years, 1 month

Issue 1099 in moose-technology: update visible list items on selection

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Glamour New issue 1099 by usman.bh...(a)gmail.com: update visible list items on selection https://code.google.com/p/moose-technology/issues/detail?id=1099 Tree/list presentation should display non-visible items when one of these items is selected. To reproduce, execute the following script. Normally, the of items should be expanded and 14 should be shown in the list on the left because it is the current selection item. However, the list does not change and 14 is not shown. browser := GLMTabulator new. browser column: #one; column: #two. browser transmit to: #one; andShow: [:a | a list showOnly: 10; display: [:number | (1 to: number)] ]. browser transmit to: #two; from: #one; andShow: [:a | a roassal2 initializeView: [ RTMondrianViewBuilder new ]; painting: [:view :number | view interaction when: TRMouseDoubleClick do: [:ann | ((browser paneNamed: #one) port:#selection) value: ann element model ]. view shape label. view nodes: (1 to: number + 5). view edgesFrom: [:each | each // 2 ]. view treeLayout ]]. browser openOn: 100. ((browser paneNamed: #one) port: #selection) value: 14. -- 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

Menus with Glamour / GT inspector

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.

10 years, 1 month

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*

10 years, 1 month

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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

10 years, 1 month

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 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

10 years, 1 month

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/

10 years, 1 month

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

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