Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

Start a nNew thread

Jenkins build became unstable: moose-latest-dev #1149
by admin＠moosetechnology.org 02 Oct '12

02 Oct '12

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

1 1

Roassal ROPopup styleable
by Dennis Schenk 02 Oct '12

02 Oct '12

Hi all, I wanted to be able to style popups in Roassal e.g. using another background color or setting a border, etc. So I added a method to ROPopup to be able to acces the ROBox it uses. The filed out class can be found here: http://cl.ly/code/3D0y0P233v1o @Alexandre: If you like the changes, could you add them to Roassal? Example usage would be: *popup := ROPopup text: 'test'.* *popup textColor: Color black.* *popup box color: Color white; borderWidth: 1; borderColor: Color lightGray. * * * Cheers, Dennis

2 2

Issue 847 in moose-technology: Glamour does not populate the right value when selecting in EyeSeePresenation
by moose-technology＠googlecode.com 01 Oct '12

01 Oct '12

Status: New Owner: ---- CC: tudor.gi...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Glamour Milestone-4.7 New issue 847 by tu...(a)tudorgirba.com: Glamour does not populate the right value when selecting in EyeSeePresenation http://code.google.com/p/moose-technology/issues/detail?id=847 See GLMBasicExamples new eyeseeBarDiagram openOn: #(5 2 10 6 12 8).

1 2

Issues plotting histograms with EyeSee
by Hernán Morales Durand 01 Oct '12

01 Oct '12

Hi guys, I want to dome basic plotting with EyeSee in Pharo 1.4, and try to imitate the following histogram produced with matplotlib: http://biopython.org/DIST/docs/tutorial/images/hist_plot.png which was taken from 94 samples rendered with 20 bins. I've tried this script including the same models: | diagram | diagram := ESDiagramRenderer new. diagram histogram models: #(740 753 748 744 733 718 730 704 740 709 700 726 753 699 658 752 726 765 755 742 762 745 750 731 741 740 727 711 743 727 757 770 767 759 750 788 774 789 688 719 743 737 728 740 696 732 731 735 720 740 629 572 587 700 636 716 592 716 733 626 737 740 574 594 610 730 641 702 733 738 736 732 745 744 738 739 740 745 695 745 743 730 706 744 742 694 712 715 688 784 721 703 744 592); property: [:each | each ]; numberOfIntervals: 20; rotatedLabels: true; yAxisLabel: 'Count'; xAxisLabel: 'Sequence length (bp)'; regularAxis; addXDecorator: ESValueLabelDecorator new. ^ diagram open but I'm experimenting some limitations that you may know better: 1) Cannot make both x and y labels to be displayed. 2) In the X axis, matplotlib seems to take only significant interval. 3) Also tried with different decorators (ESValueLabelDecorator, ESRangeLabelDecorator, ESRegularTickDecorator, etc) but it didn't changed. Any hints to overcome this? Best regards, Hernán

2 4

selective forwarding of ROMenuActivable
by Ben Coman 01 Oct '12

01 Oct '12

Alexandre, A couple of days ago you showed how to forward only ROMouseDragging on a composed element while leaving ROLightlyHighlightable on the inner elements. I'd like to do the same with menus using ROMenuActivable. That is, I want to define one menu for an outer element to activate for all its inner elements. I gave it a naive guess by modifying ROExample>>composingOn:. below. This works if all are forwarded per CASE 1, but not per CASE 2. Is there a different class I should be forwarding? cheers -ben "-------------" "-------------" counter := 0. outter := ROElement new + ROBorder white. outter @ RODraggable @ ROLightlyHighlightable. inner := ROElement sprite @ ROLightlyHighlightable. innerLabel := (ROElement labelOn: 'My sprite') @ ROLightlyHighlightable. outter add: inner; add: innerLabel. "We layout the things" ROVerticalLineLayout on: outter elements. rawView add: outter. "CASE 1 forwarding all" inner forward. innerLabel forward. "CASE 2 menu forwarding" "inner forward: ROMouseDragging. inner forward: ROMenuActivable . innerLabel forward: ROMouseDragging. innerLabel forward: ROMenuActivable . " "MENUS" outter @ (ROMenuActivable new item: 'OuterMenu' action: [ :model | counter := counter + 1. Transcript crShow: 'Outer ', counter asString . ] ). inner @ (ROMenuActivable new item: 'InnerMenu' action: [ :model | counter := counter + 1. Transcript crShow: 'Inner ', counter asString . ] ). innerLabel @ (ROMenuActivable new item: 'InnerLabelMenu' action: [ :model | counter := counter + 1. Transcript crShow: 'InnerLabel ', counter asString . ] ). "-------------" "-------------"

2 2

Jenkins build is unstable: moose-latest-dev #1147
by admin＠moosetechnology.org 01 Oct '12

01 Oct '12

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

1 1

Issue 848 in moose-technology: Roassal tree layouts raise DNU when send #layered
by moose-technology＠googlecode.com 01 Oct '12

01 Oct '12

Status: New Owner: tu...(a)tudorgirba.com CC: alexandr...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Roassal Milestone-4.7 New issue 848 by tudor.gi...(a)gmail.com: Roassal tree layouts raise DNU when send #layered http://code.google.com/p/moose-technology/issues/detail?id=848 For example: view shape rectangle width: #yourself. view nodes: (1 to: 100). view edgesFrom: [:x | x // 2 ]. view horizontalTreeLayout layered

1 2

problem with fuelmoose apparently corrupting exporting
by Tudor Girba 01 Oct '12

01 Oct '12

Hi, I have a problem with FuelMoose: - I have an MSE produced by VerveineJ. - Import it into Moose 4.7 - I export it with FuelMoose - But, after I import it back I get a DNU from the model. The reason seems to be that FuelMoose provides a property value (e.g., a method signature) to the wrong property slot (e.g., the package reference). - I do not know if it's relevant, but I do this on Windows 7 Originally, I suspected that somehow Fame messes up properties, but I tried to export and load the same model using the MSE mechanism and that works properly. So, I would need help. If someone has time to look into this, I can provide the model privately. Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

4 7

Roassal-Magritte link semantics
by Ben Coman 01 Oct '12

01 Oct '12

For a long time I have had the code below linking Magritte-Roassal. Originally I had expected ":view" to hold aROView, and it was a surprise when I found out held aROMondrianViewBuilder instead. While it makes sense to have had a drop in replacement for the Magritte-Mondrian, and it is simple to get the ROView from the ROMondrianBuilder, it feels inelegant to have to do this each time. --- browser transmit from: #pane1 to: #pane2 andShow: [ :a | a roassal title: 'Instance Model Full View'; painting: [ :view :selection | | rawView | rawView := view raw. ...etc... ] ]. --- Looking in from outside and considering long term broadening use of Roassal outside of Mondrian, it would "feel" better if ... andShow: [ :a | a roassal.... passed aROView as a parameter to #painting, and the Mondrian drop-in replacement to be something like ... andShow: [ :a | a roassalMondrian andShow: [ :a | a roMondrian andShow: [ :a | a mondrianBuilder which passed aROMondrianBuilder. cheers -ben

3 2

Jenkins build is unstable: moose-latest-dev #1141
by admin＠moosetechnology.org 30 Sep '12

30 Sep '12

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

1 3

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev