Moose-dev August 2012

moose-dev@list.inf.unibe.ch

21 participants
113 discussions

Start a nNew thread

Jenkins build became unstable: moose-latest-dev #1105

by admin＠moosetechnology.org

See <http://hudson.moosetechnology.org/job/moose-latest-dev/1105/>

12 years, 10 months

Moose in the classroom

by Alexandre Bergel

Hi! Yesterday evening we had a 3 hours moose session with industrial. We had fun :-) http://dl.dropbox.com/u/31543901/MooseInClassroom.jpg Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

12 years, 10 months

identifying Exception classes

by Nicolas Anquetil

It seems there is no way to identify classes (java) that are Exceptions. Even the one that are used. There are ThrownException / DeclaredException / CaughtException , all pointing to the exceptionClass, but there is no opposite property in the exception class that one could use to test whether a given class is used as an exception. So the only way is to test whether Exception is an ancestor of a given class ? nicolas

12 years, 10 months

Jenkins build became unstable: moose-latest-dev #1100

by admin＠moosetechnology.org

See <http://hudson.moosetechnology.org/job/moose-latest-dev/1100/>

12 years, 10 months

Roassal hover popup on edges

by Ben Coman

With the following script, in Mondrian when you hover over edges a popup appears showing the name of the edge. Is the same possible with Roassal? view shape rectangle size: 20. nodes := view nodes: (1 to: 20). view edges: (2 to: 20) from: 1 to: #yourself. view circleLayout. cheers, Ben

12 years, 10 months

Design advice request (somewhat but not completely Roassal focussed)

by Ben Coman

12 years, 10 months

ROMondrianViewBuilder versus native Roassal

by Ben Coman

Is there anything (at all) to gain in my continuing to use ROMondrianViewBuilder versus "native" Roassal? Is ROMondrianViewBuilder "just" for backward compatability to ease the transition and draw people into the new system? Or... is there stuff that ROMondrianViewBuilder does better than "native" Roassal - in terms of conciseness, ease of use, flexibility, access to layouts, features, etc... I am trying to determine whether putting effort into the perhaps easier step of going from Mondrian to ROMondrianViewBuilder may be wasted leaving me missing out on any new power of Roassal, or require more effort later to rework for native Roassal. You may have gone over this before, but how do the purpose and architecture of the two differ? cheers -ben

12 years, 10 months

Roassal internals >> ROShape>>removeShape:

by Ben Coman

Just recording a bit of my learning the internals of Roassal, since it helps me flesh out my understanding. [ROShape>>removeShape:] does not have a test to reference for my understanding of this, but it appears to not work as expected. For example in workspace... b := ROBox new. c := ROCircle new. b addLast: c. b removeShape: ROCircle. b inspect results in a linked list of: aROBoxShape --> aROCircleShape --> aROChildrenShape. Actually the semantics of [removeShape:] seem problematic. What should be the result of... b := ROBox new. b removeShape: ROBox. b inspect. I would guess that 'b' should hold aROChildrenShape, except you can't change the value of 'b' from inside the [removeShape:] method. (In my limited knowledge of 'slots', I wonder if this is something they might help with.) I am relying on the guess that you could have aROChildrenShape as the only shape on an element, for subviews without a border, but could you clarify this. Naively I thought to just try... removeShape: aShapeClass ^ (self isKindOf: aShapeClass) ifTrue: [ next become: next next ] ifFalse: [ next removeShape: aShapeClass ] but the danger of #become hit me and locked my image. btw, something else just while I am feeling evil, what should happen with the following... b := ROBox new. b removeShape: ROChildrenShape. b inspect. cheers -ben

12 years, 10 months

Running CodeCity in Pharo?

by Torben Knerr

Hi everybody, is there a Pharo port of Code City? I am wondering because the use of VisualWorks Smalltalk and the license restrictions that come with it make it impossible to use Code City in a commercial setting (if I understand it right). Cheers, Torben

12 years, 10 months

popUpView in Roassal

by Usman Bhatti

Hello all, I'm having trouble to apply proper layout in popUpView in Roassal. The problem can be seen with the output of the following scripts: both manipulating same entities, the first one drawing entities without popUp (and producing correct layout), the second one is using popUpView (problem with the produced layout): myView := ROMondrianViewBuilder new. myView node: 'test' forIt: [ myView shape rectangle. myView node: #innerNode forIt: [ myView shape rectangle. myView node: #first forIt: [ myView nodes: #(1 2 3) ]. myView shape rectangle. myView node: #second forIt: [ myView nodes: #(1 2 3) ]. myView shape rectangle. myView node: #third forIt: [ myView nodes: #(1 2 3) ]. myView verticalLineLayout center ]. myView gridLayout ]. myView open ========================================================== view := ROMondrianViewBuilder new. view shape label. view interaction popupView: [ :entity :myView | myView node: 'test' forIt: [ myView shape rectangle. myView node: #innerNode forIt: [ myView shape rectangle. myView node: #first forIt: [ myView nodes: #(1 2 3) ]. myView shape rectangle. myView node: #second forIt: [ myView nodes: #(1 2 3) ]. myView shape rectangle. myView node: #third forIt: [ myView nodes: #(1 2 3) ]. myView verticalLineLayout center ]. myView gridLayout ]. ]. view nodes: #(0 9 8). view open Could you please see if there is a bug or I am doing it wrong? tx, Usman

12 years, 10 months

← Newer
1
...
6
7
8
9
10
11
12
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev August 2012