Hi,
I developed a small extension which allows to query a moose model to obtain a set of implicit associations derived from low level relationships.
What you can do concretely is for example to select a group of namespace entities, and ask for all implicit associations existing between the selected entities based on a specific relationship existing at a lower abstraction level (i.e.: the method level).
The end result is much similar to the one provided by Moose Chef, with the advantage of being much more generic and flexible.
Each generated association keeps a reference to the concrete relationships on which it is based on.
If you are interested, you can try it out at: http://www.squeaksource.com/Lift.html
The wiki page contains some usage examples.
cheers,
Andrea
_____________________________
Andrea Caracciolo -- caracciolo(a)iam.unibe.ch
Software Composition Group
University of Bern
Hi,
I would like to create a visualization with resizable nodes (with resizable
I mean that I can click and drag a border to change the size of the node).
Is this possible in Roassal or Mondrian?
Cheers,
Fabrizio
Hi,
Roassal add "Roassal Easel" as an item in the root of the World menu. However, this is a rather primitive Easel.
In Glamour, there already exists an Easel similar to the Mondrian one. I now added all these editors in the Moose menu.
In the Moose image, I would prefer to not have the default Roassal easel in the World menu, because it increases confusion. Perhaps one idea would be to move it into Tools (like PetitParser does).
Alex, what do you say?
Cheers,
Doru
--
www.tudorgirba.com
"Yesterday is a fact.
Tomorrow is a possibility.
Today is a challenge."
I remember seeing some discussion on this in the past.
What is the status of the Latent Semantic Indexing (Hapax I believe) in
Moose?
Was it ported to Pharo?
nicolas
MouseEnter event does not fire while entering a node.
This script shows the demonstrates the problem.
view := ROMondrianViewBuilder new.
view shape rectangle size: 20.
view interaction on: ROMouseEnter do: [ :event |
view shape line color: Color blue.
view edgesFrom: [ :i | i \\ 2 ].
].
view nodes: (1 to: 20).
view shape line.
view treeLayout.
view open
tx,
Usman Bhatti
Hi!
The release of Roassal is now official. As you might have seen, Roassal is now distributed with Moose. The plan is to slowly replace Mondrian by Roassal. This may take some time, but we will reach the point that Mondrian can rest in peace.
Roassal remains largely compatible with Mondrian. The visualizations you have scripted with Mondrian should normally work with Roassal without too much pain.
Gofer new
squeaksource: 'Roassal';
package: 'ConfigurationOfRoassal';
load.
(Smalltalk at: #ConfigurationOfRoassal) project lastVersion load.
Having Roassal out implies that I will essentially focus on Roassal instead of Mondrian. Naturally, I will continue to incorporate important bug fixes in Mondrian. But as far I am concerned, no major enhancement of Mondrian is planned.
We learnt a lot with Mondrian. Roassal really goes one step further with better interactions, a clean low level if you wish to build your own domain specific language. To be short, Roassal is simpler and better.
I suggest people to enter bug fixes and requests for enhancement in the Moose google project as we are doing for Mondrian.
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi,
I have the following browser:
| browser |
browser := GLMTabulator new.
browser
row: [ :r | r column: #one; column: #two];
row: #three.
browser transmit to: #one; andShow: [:a |
a title: 'One'.
a list display: [ #('Something 1' 'Something 2' 'Something 3' 'Something
4')];
selectionAct: [:list |
(list pane port: #customSelection) value: 1 ]
entitled: 'Open new panel'
].
browser transmit from: #one; to: #two; andShow: [:a |
a title: 'Two'.
a list
display: [ #('A' 'B' 'C' 'D') ]
].
browser transmit from: #two; to: #three; andShow: [:a |
a title: 'Information'.
a text display:[ :x | 'Information related to ',x asString ] .
].
browser transmit to: #three; from: #one port:#customSelection;andShow: [:a
|
a title: 'Three'.
a list
display: [#('A' 'B' 'C' 'D')]
].
browser openOn: 1.
When a value of the list of the pane "two" is selected a new pane is open
in #three. Also, when the action of the pop-up menu of the pane #one is
selected, a new pane is open in #three. My problem is that the new pane
opened after clicking in the pop-up menu is only shown the first time that
it is called. That is, if I click in the menu, then I click in an element
of the pane #two and finally I click again in the menu action the pane
#three is not shown this time. I'm doing something wrong? I can't
understand why this happens.
Thanks!
Cheers,
Santiago
--
Santiago Vidal
Hi!
I know this has been on the wished list of many of you. The following script produces:
-=-=-=-=-=-=-=-=-=-=-=-=
| view el1 el2 edge line |
view := ROView new.
el1 := ROElement new.
el1 @RODraggable.
el1 extent: 50@50.
el1 + ROBox blue.
el2 := ROElement new.
el2 @RODraggable.
el2 extent: 50@50.
el2 + ROBox green.
el1 translateTo: 0 @ 100.
edge := ROEdge from: el1 to: el2.
line := ROLine new.
line add: ROArrow new offset: 0.1.
line add: ROArrow new offset: 0.5.
edge + line.
view add: el1; add: el2; add: edge.
view open
-=-=-=-=-=-=-=-=-=-=-=-=
I will remove ROArrowedLine very soon then
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
I'm getting this error in my visualizations. Should I open a bug entry?
DNU: ROMondrianViewBuilder >> container...
To reproduce: execute the following code in a freshly downloaded moose
image, trigger the visualization by right-clicking on a number and
selecting the menu item....
| browser |
browser := GLMTabulator withStatusbar.
browser column: #one; column: #two.
browser transmit to: #one; andShow: [ :a |
a list
title: 'Select and trigger from menu';
display: [:x | 1 to: x ];
selectionAct: [:list |
| value |
value := list selection * 10. "simulate some custom setup"
(list pane port: #customSelection) value: value ]
entitled: 'Multiply by 10 and then send outside'
].
browser transmit to: #two; from: #one port: #customSelection; andShow: [ :a |
a roassal
title: 'Numbers in Roassal';
painting: [:view :number |
view shape label.
view nodes: (1 to: number).
view edgesFrom: [:each | each // 5 ].
view treeLayout.
ROEaselMorphic new populateMenuOn: view.
]].
browser openOn: 42
Hello,
I had built a few visualizations in Galmour based on low-level roassal api.
I download a new version of Moose and the now glamour returns an object
of ROMondrianViewBuilder instead of ROView, which breaks my visualizations.
So, does glamour aim to provide a way to work with the low-level api or
should I just create my own extensions to adapt my visualization to the new
mode?
tx,
Usman
Thx, I'll have a look.
Ken
On week 24, 2012-06-13, at 4:21 AM, moose-dev-request(a)iam.unibe.ch wrote:
> Date: Tue, 12 Jun 2012 23:16:29 +0200
> From: Tudor Girba <tudor(a)tudorgirba.com>
> Subject: [Moose-dev] Re: Moose in VW 7.8 on Mac?
> To: Moose-related development <moose-dev(a)iam.unibe.ch>
> Message-ID: <A4B82012-5E72-4CB8-9210-FD91B3E96050(a)tudorgirba.com>
> Content-Type: text/plain; charset=us-ascii
>
> Hi Ken,
>
> The most recent instructions can be found here:
> http://www.moosetechnology.org/download/vw
>
> As you can see, the last time we looked into it, VW was at version 7.7.
>
> Cheers,
> Doru
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 807 by santiago...(a)gmail.com: Populating menu in Roassal
visualization in Glamour doesn't work
http://code.google.com/p/moose-technology/issues/detail?id=807
Roassal doesn't populate a menu in Glamour. For example, using the example
of GLMBasicExamples>>roassalPainting I want to add a menu in the view
using 'ROEaselMorphic new populateMenuOn: view'. While a small scrolling is
done (to not have the buttons over the nodes) the buttons aren't shown.
| browser |
browser := GLMTabulator withStatusbar.
browser column: #one; column: #two.
browser transmit to: #one; andShow: [ :a |
a list
title: 'Select and trigger from menu';
display: [:x | 1 to: x ];
selectionAct: [:list |
| value |
value := list selection * 10. "simulate some custom setup"
(list pane port: #customSelection) value: value ]
entitled: 'Multiply by 10 and then send outside'
].
browser transmit to: #two; from: #one port: #customSelection; andShow:
[ :a |
a roassal
title: 'Numbers in Roassal';
painting: [:view :number |
view shape label.
view nodes: (1 to: number).
view edgesFrom: [:each | each // 5 ].
view treeLayout.
ROEaselMorphic new populateMenuOn: view.
]].
browser openOn: 42
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 785 by fabrizio...(a)gmail.com: inFamix don't export
FAMIXLocalVariable>>parentBehaviouralEntity
http://code.google.com/p/moose-technology/issues/detail?id=785
FAMIXLocalVariable entities exported with inFamix are not associated with
the behavioural entity they are belong to.
Dear Smalltalkers,
As you know ESUG (European Smalltalk User Group) is a nonprofit
organization, ran by a bunch of volunteers which aims at promoting
Smalltalk (http://www.esug.org/Promotion). ESUG does have multiple
actions such as sponsoring Smalltalk-related publications (articles
and books), encouraging developers and more specifically young
students to learn Smalltalk (Student Volunteers program) and build
innovative software using Smalltalk (SummerTalk, ESUG Awards, "Support
your project" program, Umbrella for GSoC, ...).
ESUG revenue comes only from sponsoring, donations, and registrations
to the ESUG yearly event (for 20 years!).
Therefore, we invite you to support the ESUG actions by encouraging
your companies and organizations to sponsor ESUG.
As previous years, we have three sponsoring packages
(http://www.esug.org/About/BecomeSponsor):
* Silver ESUG Sponsor: By paying € 500 per year, the logo of your
company/association is displayed during the ESUG conference, and you
are also recognized as a sponsor on our ESUG website
http://www.esug.org. You are entitled to mention that you are an ESUG
sponsor, and to use the ESUG logo in that context.
* Gold ESUG Sponsor: By paying € 1000 per year, you get all of the
above, and ESUG correspondence and distributions (CD, Documentation)
will feature your logo. You also get a 10% fee reduction on the ESUG
events for up to 5 people of your organisation.
* Platinum ESUG Sponsor: By Paying € 2000 per year, you get all of the
above, but you get a 20% fee reduction on the ESUG events for up to 10
people of your organisation.
For any further information, you can contact us directly at board(a)esug.org.
Best regards,
Luc Fabresse
On behalf of the ESUG board
--
Damien Cassou
http://damiencassou.seasidehosting.st
"Lambdas are relegated to relative obscurity until Java makes them
popular by not having them." James Iry
Basically right now I would like to get a visual overview of how things work together, the main subsystems, that sort of thing. I would like something to help me build a conceptual framework of a fairly large client server suite, in order to place the different software pieces in my mind when I come across them.
Perhaps something like this:
<http://www.moosetechnology.org/docs/famix/3.0>
would be good to start with, then later maybe this:
<http://www.moosetechnology.org/docs/famix/dynamix>
or:
<http://www.moosetechnology.org/docs/polymetricviews>
I'm not sure what is possible at this point so I'm unsure of what would be most beneficial.
Thx for taking the time to respond,
Ken
On 2012-06-12, at 2:47 PM, moose-dev-request(a)iam.unibe.ch wrote:
> Date: Tue, 12 Jun 2012 22:05:48 +0200
> From: St?phane Ducasse <stephane.ducasse(a)inria.fr>
> Subject: [Moose-dev] Re: Moose in VW 7.8 on Mac?
> To: Moose-related development <moose-dev(a)iam.unibe.ch>
> Message-ID: <19BD3E4C-12DE-46D8-8023-4F3C8F89B06F(a)inria.fr>
> Content-Type: text/plain; charset=us-ascii
>
> Hi ken
>
> it is in the state we left it when we were kind of forced to move away from VW.
> So this is working but this is three years now that we worked on the new one.
>
> Tell us what you need and we will tell you if we know if this is working.
>
> Stef
>
> On Jun 12, 2012, at 7:29 PM, Ken G. Brown wrote:
>
>> I'm new to the Moose Suite and would like to give it a try in VW 7.8 on Mac, for aiding in exploring an existing quite extensive suite of software.
>>
>> What is the current status of the Moose family on VW 7.8?
>>
>> Could someone please point me in the right direction for an appropriate jump-start in order to get going as quickly as possible?
>>
>> Any tips and recommendations will be greatly appreciated.
>>
>> Thx,
>> Ken G. Brown
>> _______________________________________________
>> Moose-dev mailing list
>> Moose-dev(a)iam.unibe.ch
>> https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi,
using the example of GLMBasicExamples>>roassalPainting I want to add a menu
in the view using ROEaselMorphic new populateMenuOn: view. While a small
scrolling is done (to not have the buttons over the nodes) the buttons
aren't shown. Is this a bug of the Glamour or I'm doing something wrong?
Thanks
Cheers
Santiago
| browser |
browser := GLMTabulator withStatusbar.
browser column: #one; column: #two.
browser transmit to: #one; andShow: [ :a |
a list
title: 'Select and trigger from menu';
display: [:x | 1 to: x ];
selectionAct: [:list |
| value |
value := list selection * 10. "simulate some custom setup"
(list pane port: #customSelection) value: value ]
entitled: 'Multiply by 10 and then send outside'
].
browser transmit to: #two; from: #one port: #customSelection; andShow: [ :a
|
a roassal
title: 'Numbers in Roassal';
painting: [:view :number |
view shape label.
view nodes: (1 to: number).
view edgesFrom: [:each | each // 5 ].
view treeLayout.
ROEaselMorphic new populateMenuOn: view.
]].
browser openOn: 42
--
Santiago Vidal
I'm new to the Moose Suite and would like to give it a try in VW 7.8 on Mac, for aiding in exploring an existing quite extensive suite of software.
What is the current status of the Moose family on VW 7.8?
Could someone please point me in the right direction for an appropriate jump-start in order to get going as quickly as possible?
Any tips and recommendations will be greatly appreciated.
Thx,
Ken G. Brown
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 805 by galois.z...(a)gmail.com: Can't import example model from
SCD:MSE webpage
http://code.google.com/p/moose-technology/issues/detail?id=805
I'm trying to test Moose and for that I wanted to import the meta-model
that describes the structure of the package LIB from the SDC:MSE webpage
(http://scg.unibe.ch/wiki/projects/fame/mse). THe problem is that the tool
produces an error saying "Element 'FM3.Package' not found".
1 - Copy the model text from the webpage and save it in a *.mse file;
2 - In Moose choose the Import model from MSE file
3 - Select the *.mse file you created in 1.
4 - Moose will present an error window with the title "Error:
Element 'FM3.Package' not found'
I juts downloaded Moose from the website. It is version 4.6.
I'm running Moose on a Mac sunning OS X 10.7.4.
The Java version I'm running is:
java version "1.6.0_31"
Java(TM) SE Runtime Environment (build 1.6.0_31-b04-415-11M3635)
Java HotSpot(TM) 64-Bit Server VM (build 20.6-b01-415, mixed mode)
Please fill in the labels with the following information:
* Type-Defect
* Component-FAMIX
Hi Ben (Coman :)),
Currently, Mondrian-Pharo-Morphic is branched.
I tried to understand the rubberBand-related code, but I did not quite understand its purpose.
Could you please merge the two branches? Also, in the process, please remove the active writing to Transcript.
Cheers,
Doru
--
www.tudorgirba.com
"Not knowing how to do something is not an argument for how it cannot be done."
Hi,
I'm trying to open a Roassal visualization in glamour. I have the following
script:
| browser action|
browser := GLMTabulator new.
browser
row: [ :r | r column: #columnA; column: #columnB ];
row: #seconRow.
browser transmit to: #columnA; andShow: [ :a |
a list display: [#('Value 1' 'Value 2' 'Value 3') ];
dynamicActionsOnSelection: [:list | self actionsFor: list ]
].
browser transmit from: #columnA; to: #columnB; andShow: [ :a |
a list titleIcon: GLMUIThemeExtraIcons glamorousBrowse
;title:'Data'; display:#('data A' 'data B' 'data C').
].
browser openOn: MooseModel root allModels anyOne.
actionsFor: aPresentation
|actions|
actions:=OrderedCollection new.
actions add: ((GLMGenericAction new)
action: [:each |AMerlinWizard openWizard(each selection)];
title: 'Open visualization';
yourself).
^actions.
Specifically, when I click in the option "Open visualization" of the popup
menu (see dynamicActionsOnSelection) a Merlin Wizard is opened (there are
some options that the user has to select) to create a Roassal (or Mondrian)
visualization. Currently, I'm creating the visualization in a new view.
However, I would like to open it in the #seconRow pane. Someone please
could tell me how I can accomplish this? Thanks
Cheers
Santiago
--
Santiago Vidal
Status: New
Owner: andreho...(a)gmail.com
Labels: Type-Enhancement Priority-Medium Component-EyeSee
New issue 803 by andreho...(a)gmail.com: Improve pie and kiviat charts
http://code.google.com/p/moose-technology/issues/detail?id=803
Pie and kiviat charts should work with legends.
Kiviat chart to plot metric labels on axis.
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-Finder Milestone-4.7
New issue 802 by tudor.gi...(a)gmail.com: The MetaBrowser spawns an error
when wanting to browse the implementation of a property
http://code.google.com/p/moose-technology/issues/detail?id=802
browser := MooseMetaExplorer new browser.
browser openOn: MooseModel meta.
(browser pane port: #entityToSelect) value: FAMIXClass mooseDescription.
(browser pane port: #propertyToSelect) value: FAMIXClass mooseDescription
allComplexAttributes anyOne.
Then switch to the second pane and press Command+b.
Status: New
Owner: tudor.gi...(a)gmail.com
Labels: Type-Defect Priority-Medium Component-Glamour Milestone-4.7
New issue 804 by tudor.gi...(a)gmail.com: GLMRoassalEasel should support the
Mondrian API of Roassal
http://code.google.com/p/moose-technology/issues/detail?id=804
Right now, it provides ROView as an input. Instead, it should provide
ROMondrianViewBuilder