Moose-dev

moose-dev@list.inf.unibe.ch

6630 discussions

by Fabrice Atrevi

Hi! I'm using roassal in glamour for painting. I want to know how i can give a length for edge. Like in the screenshot, the default length is too small. And if possible, i want boxes and arcs do not intersect. Thanks, -- *ATREVI D. Fabrice* *Master en Informatique A l'Institut de la Francophonie pour l'Informatique (IFI/Hanoï)*

10 years, 9 months

Roassal2: Tree layout set vertical separation

by Johan Fabry

Hi all, quick question: how do I set the vertical separation between nodes in a RTTreeLayout? I have tried verticalGap: and topGap: but it does not make a difference. length: is undefined. Thanks in advance, ---> Save our in-boxes! http://emailcharter.org <--- Johan Fabry - http://pleiad.cl/~jfabry PLEIAD lab - Computer Science Department (DCC) - University of Chile

10 years, 9 months

Thanks Serge for the MooseDay

by Alexandre Bergel

Hi! The second day of the moose day is over. It was great to meet you guys. I had a wonderful time! Thanks Serge for organizing the event, setting up the website, arranging the restaurant, and having found sponsors :-) Good spirit!! Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

10 years, 9 months

removing group nodes in Roassal2

by Usman Bhatti

Hi, When removing grouped nodes from RTView, we get the red box. Try this script: view := RTView new. menuBuilder := RTMenuBuilder new view: view. menuBuilder menu: 'Click Me' background: Color gray callback: [ view clean. ]. group := RTGroup new. (1 to: 10) do: [:each| group add: ((RTBox new borderColor: (Color green); elementOn:each) @ RTDraggable; +(RTLabel new color: (Color red); text: each asString; yourself))]. view add: group. RTVerticalLineLayout on: view elements. view open. Is it a bug or does it occur because of the wrong usage of RTGroup? Usman

10 years, 9 months

Re: Rubric slow as hell :)

by Yuriy Tymchuk

Ok, then it’s my fault probably. I have Epicea but it should be concerned only about method/class changes. Also DFlow is installed but not running, maybe it’s erecting stuff anyway. Uko On 01 Jun 2014, at 18:38, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > I had a look in your image and indeed the workspace is quite slow. > However, if I copied the same input to a new fresh moose image and it works fast. > > It seems that somehow styling takes a lot of time in your image. Are you using some kind of > instrumentation? > > > Cheers, > Andrei > > > On Sun, Jun 1, 2014 at 1:46 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Hi Andrei, > > this is the image https://space.zeo.net/g/4xxns. It contains inspector with a lot of code. For me it’s responding slow. > > Uko > > > > On 01 Jun 2014, at 17:07, Andrei Chis <chisvasileandrei(a)gmail.com> wrote: > >> Hi Yuriy, >> >> That's strange. Rubric should be very fast. If you look at the examples from RubLipsumBasicExample even text with almost 1800 lines works flawlessly. >> If it's so slow there should be a problem in the way in which we integrated rubric into glamour. Do you have an example where I can reproduce this problem. I just copied a huge amount of text into an inspector/workspace but still cannot reproduce the slowness. >> >> Cheers, >> Andrei >> >> >> On Sun, Jun 1, 2014 at 1:10 PM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: >> Hi, I thought my image is lagging, but it happens only in rubric. Yes, probably having 1794 characters in a method is not good, but when you are scripting Code City stuff, sometimes your experiments get large :). Again, sorry for that harsh characteristics, but typing characters and waiting 2 secs for them to appear is a bit upsetting :). >> >> Uko >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev >> >> _______________________________________________ >> Moose-dev mailing list >> Moose-dev(a)iam.unibe.ch >> https://www.iam.unibe.ch/mailman/listinfo/moose-dev > >

10 years, 9 months

Roassal2 and zooming (camera)

by Yuriy Tymchuk

Hi, zooming in Roassal was always a sensitive topic for me, and now it seems to get better API in Roassal2. There are still some things that I don’t understand. Eg. when I send #translateTo:, #translateBy: and related things like #focusOnCenter to TRCamera, nothing happens (at least in GTInspector view). Is there a specific way to use it? Or it’s still work in progress? Cheers! Uko

10 years, 9 months

An interesting paper for keeping track of code transformations

by Stéphane Ducasse

Hi guys The rascal people told me about this nice about tracibility of transformation http://homepages.cwi.nl/~storm/publications/string-origins.pdf Stef

10 years, 9 months

revamping the moose logo

by Tudor Girba

Hi, I am playing with a new look for Moose. I started from the logo and the goal is to provide a more dynamic feeling to it. Here is a draft. It is based on the same philosophy as the current logo (see http://www.tudorgirba.com/blog/moose-and-the-analysis-story) Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

10 years, 9 months

Roassal2 element bounds

by Yuriy Tymchuk

Hi, I’m trying to port rectangle packing layout to roassal 2. And one problem that I’ve encountered was that element now do not understand #bounds. I’ve replaced all #bounds usages with #encompassingRectangle, but in the end layout is broken anyway. Before I start to dig down, maybe there are known changes that can impact layouts? Uko

10 years, 9 months

Jenkins build became unstable: moose-5.0 #1560

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-5.0/1560/>

10 years, 9 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev