Moose-dev

moose-dev@list.inf.unibe.ch

6630 discussions

by Alexandre Bergel

Hi! I’ve just stumbled on this rather old piece of code. It animates some text. Kind of fun :-) In case you have never seen it, you may try: RTExample new rotatingLabelsAnimated Here is the code: -=—=-=-=—=-=-=—=-=-=—=-= | v shape timer | v := RTView new. timer := VITimer new cycleLength: 2. shape := RTRotatedLabel new. shape angleInDegree: [ :cls | | valueEnd | valueEnd := cls numberOfMethods negated / 1.5. VIAnimatedValue new evaluator: [ :t | 0 interpolateTo: valueEnd at: t ]; timer: timer; yourself. ]. shape text: [ :cls | ' ', cls name ]. shape color: (Color black alpha: 0.2). v addAll: (shape elementsOn: Collection withAllSubclasses). v canvas color: Color white. v addAnimation: TRResetAllShapes new. timer start. v open -=—=-=-=—=-=-=—=-=-=—=-= -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

9 years, 10 months

Issue 1110 in moose-technology: Easy Improvement of Roassal

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium Component-Roassal New issue 1110 by alexandr...(a)gmail.com: Easy Improvement of Roassal https://code.google.com/p/moose-technology/issues/detail?id=1110 Improve RTNestingBehavior>>centerOn: backElement elements: elements Code is about ugly. -- 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, 10 months

Issue 896 in moose-technology: Roassal should offer a proper scrolling mechanism

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: alexandr...(a)gmail.com Labels: Type-Enhancement Priority-Medium Component-Roassal New issue 896 by tu...(a)tudorgirba.com: Roassal should offer a proper scrolling mechanism http://code.google.com/p/moose-technology/issues/detail?id=896 For any visualisation that is larger than the screen, you immediately get lost in Roassal. Furthermore, the current dragging style does not scale for visualizations that are much larger on one dimension than the screen. We need a mechanism that helps us: - get an idea of where we are (and how much is left outside the current view) - have an easy way to actually scroll through a larger space

9 years, 10 months

GT Inspector: Immediately Browse Class

by Sean P. DeNigris

There's a little workflow I'm used to, where I have say an inst var in the debugger and I want to browse its class, so I inspect it and then immediately browse (cmd-b). This worked in the old inspector, but in GT, since there is nothing selected by default, I get a browser on Undefined. Maybe default to self instead of nil? ----- Cheers, Sean -- View this message in context: http://forum.world.st/GT-Inspector-Immediately-Browse-Class-tp4809519.html Sent from the Moose mailing list archive at Nabble.com.

9 years, 10 months

ADA Parser?

by Alexandre Bergel

Hi! Do we have an ADA parser? Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

9 years, 10 months

Re: [Pharo-dev] Example implementation of associations with Slots in Pharo 4.0

by Tudor Girba

Exactly :). In Fame, there is a FMMultivalueLink hierarchy that implement many to one and many to many relations. This implementation exists since before slots and now we should reimplement them with slots. It will make the code so much nicer :). Anyone interested in picking this up? Cheers, Doru On Mon, Feb 23, 2015 at 10:34 PM, Ben Coman <btc(a)openinworld.com> wrote: > I haven't played with the relation example yet, but will real soon. Just > some initial thoughts... > > I like RelationSlot. To me association seems one-way while a relation is > two-way. > > btw, Is there some reason to not match the syntax of the often cited paper > "Flexible Object Layout" ? > I see one advantage is that its easier to read all the slot names > vertically aligned. > > Object subclass: #SlotExampleMovie > slots: { > #name. > #year. > #director => ToOneRelationSlot opposite: #directedMovies class: > #SlotExamplePerson. > #actors => ToManyRelationSlot opposite: #actedInMovies class: #SlotExamplePerson. > } > classVariables: { } > category: 'SlotAssociations-Tests-Example' > > > Also maybe an alternative slot class name so that it reads more like a > sentence... "#director related to one #directedMovies in class > #SlotExamplePerson" > > Object subclass: #SlotExampleMovie > slots: { > #name. > #year. > #director => RelatedToOne inverse: #directedMovies inClass: > #SlotExamplePerson. > #actors => RelatedToMany inverse: #actedInMovies inClass: #SlotExamplePerson. > } > classVariables: { } > category: 'SlotAssociations-Tests-Example' > > Or even... > > Object subclass: #SlotExampleMovie > slots: { > #name. > #year. > #director => OneRelatedTo many: #directedMovies inClass: > #SlotExamplePerson. > #actors => ManyRelatedTo many: #actedInMovies inClass: #SlotExamplePerson. > } > classVariables: { } > category: 'SlotAssociations-Tests-Example' > > cheers -ben > > > On Tue, Feb 24, 2015 at 2:33 AM, Jan van de Sandt <jvdsandt(a)gmail.com> > wrote: > >> >> On Mon, Feb 23, 2015 at 9:59 AM, Marcus Denker <marcus.denker(a)inria.fr> >> wrote: >> >>> >>> > On 21 Feb 2015, at 21:11, Jan van de Sandt <jvdsandt(a)gmail.com> wrote: >>> > >>> > Today I experimented a little with the new Slots feature of Pharo 4.0. >>> As an example I implemented support for associations/relationships. >>> > >>> >>> Very nice! Can I add this to Pharo4 as an example? >>> >>> Sure, cool! >> >> >>> My idea is that at first we add these things as examples, and then later >>> take the examples and distill a library of >>> generally useful slots. >>> >>> >>> >> That sounds like a good approach to get familiar with these kind of new >> features. >> >> Some things I can do to improve the Example >> - Add an option to make one side of the association readonly. In most >> situations I think it's a good idea to update an association only from one >> side to keep things simple. >> - Whats a better name AssociationSlot or RelationSlot? I'm not sure >> - As Stéphane said, isn't there a nicer way to declare the associations? >> - Better error handling >> >> Jan. >> >> >> >> >> >> >> >> >> >> >> >> > -- www.tudorgirba.com "Every thing has its own flow"

9 years, 10 months

roassal pixel rendering

by Peter Uhnák

Hi, I've been experiencing weird behavior with pixel rendering... basically one pixel lines will get blurred for some reason even though there is no half-pixel overlapping. Here is a test code (screenshots attached below). Without the labels the left box will be blurred while the right is better (even though it still has slight shadow); when I add labels however their behavior will switch. What I would expect is to have nice sharp lines all the time. Is this Athens issue? Roassal? Pharo? Its ugly both on Linux and Windows. ==================================== | view box1 box2 | view := RTView new. box1 := RTBox new width: 50; height: 51; fillColor: Color transparent; borderColor: Color black; elementOn: '50@51'. view add: box1. box2 := RTBox new width: 51; height: 50; fillColor: Color transparent; borderColor: Color black; elementOn: '51@50'. view add: box2. "box1 @ RTLabelled. box2 @ RTLabelled." box1 translateTo: -50 @ 0. box2 translateTo: 50 @ 0. view open ==================================== Peter

9 years, 10 months

Issue 1109 in moose-technology: roassal pixel rendering

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 1109 by alexandr...(a)gmail.com: roassal pixel rendering https://code.google.com/p/moose-technology/issues/detail?id=1109 Hi, I've been experiencing weird behavior with pixel rendering... basically one pixel lines will get blurred for some reason even though there is no half-pixel overlapping. Here is a test code (screenshots attached below). Without the labels the left box will be blurred while the right is better (even though it still has slight shadow); when I add labels however their behavior will switch. What I would expect is to have nice sharp lines all the time. Is this Athens issue? Roassal? Pharo? Its ugly both on Linux and Windows. ==================================== | view box1 box2 | view := RTView new. box1 := RTBox new width: 50; height: 51; fillColor: Color transparent; borderColor: Color black; elementOn: '50@51'. view add: box1. box2 := RTBox new width: 51; height: 50; fillColor: Color transparent; borderColor: Color black; elementOn: '51@50'. view add: box2. "box1 @ RTLabelled. box2 @ RTLabelled." box1 translateTo: -50 @ 0. box2 translateTo: 50 @ 0. view open ==================================== Peter Attachments: with labels.png 3.0 KB -- 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, 10 months

Extensible labels

by Alexandre Bergel

Hi! Not sure everybody is aware of it. In case you need to make your label fit in a given space portion, you can use RTExtensibleLabel. -=-=-=-=-=-=-=-=-=-=-=-= v := RTView new. s := RTExtensibleLabel new. 40 timesRepeat: [ e := s elementOn: 'Hello World'. e extent: (50 atRandom + 10) @ (50 atRandom + 10). v add: e. ]. RTFlowLayout on: v elements. v -=-=-=-=-=-=-=-=-=-=-=-= -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

9 years, 10 months

Little question about visualization in Moose

by Sebastian Tleye

Hi, I have a system with several classes and several packages. I want to do an Overview pyramid visualization. I select them all and when I do the pyramid it says NOP = 1 (number of packages equals 1), then I have a high NOC. Why is this happening? Is it correct? Thanks -- Sebastián Tleye

9 years, 10 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