Moose-dev

moose-dev@list.inf.unibe.ch

6621 discussions

passing Glamour list selection to Roassal view

by Ben Coman

With Glamour, to enable targeting the focus of a Roassal View based on the list selection in another pane, I hacked up the following Workspace script. Is there a more elegant way to achieve this? In particular, one that avoids the need to for the 'viewHack' variable? ------------- | browser viewHack | browser := GLMTabulator new. browser column: #list; column: #drawing. browser transmit to: #list; andShow: [ :a | a list ]. browser transmit to: #drawing; andShow: [ :a | a roassal painting: [ :moview :collection | collection do: [ :x | moview view add: (ROElement spriteOn: x) + ROLabel + ROBox white ]. ROVerticalLineLayout on: moview view elements. viewHack := moview view. ] ]. browser transmit from: #list port:#selection; to: #drawing; transformed: [ :x | | foundElements | viewHack elements do: [ :el | ROUnhighlightElement on: el ]. targetElement := viewHack elements at: x. ROFocusView on: targetElement. ROHighlightElement on: targetElement color: Color red. viewHack signalUpdate ]. browser openOn: #(1 2 3 4 5 6). --------------------

12 years, 5 months

Animation in Roassal

by Alexandre Bergel

hi! Just to share an example on how to do animations in Roassal. All the pieces are there, but abstractions are still missing. Sequencing animations is not intuitive so far. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= "Source code: ROExample>>animationOn:" "Preambule. It includes the initialization. " | view rawView elements b helpLabel | rawView := ROView new. view := ROMondrianViewBuilder view: rawView. "-------------" "-------------" "Define 10 blue rectangles, align them, and move them away from the corner" elements := ROElement forCollection: (1 to: 10). elements do: [ :el | el + ROBox blue; extent: 40 @ 80 ]. rawView addAll: elements. ROHorizontalLineLayout new horizontalGap: 0; on: elements. elements do: [ :el | el translateBy: 40 @ 40 ]. "We define the animation in a block to be repeatable" b := [ elements do: [ :el | el model odd ifTrue: [ ROLinearMove new nbCycles: 30; for: el by: 0 @ 40; after: [ ROLinearMove new nbCycles: 30; for: el by: 0 @ -40 ] ] ] ]. "We first do the animation" b value. "Help message" RONopAnimation new nbCycles: 70; after: [ rawView add: (helpLabel := (ROElement on: 'Click here!') + ROLabel). helpLabel translateTo: 20 @ 150.]; on: rawView. RONopAnimation new nbCycles: 120; after: [ helpLabel remove ]; on: rawView. rawView on: ROMouseClick do: [ :event | b value ]. "-------------" "-------------" "Below is the initiation of the menu and opening the visualization" ROEaselMorphic new populateMenuOn: view. view noLayout. view open -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

12 years, 5 months

Issue 734 in moose-technology: VerveineJ does not export parameters for stub methods

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: anquetil...(a)gmail.com Labels: Type-Defect Priority-Medium Component-VerveineJ New issue 734 by tu...(a)tudorgirba.com: VerveineJ does not export parameters for stub methods http://code.google.com/p/moose-technology/issues/detail?id=734 If we analyze this code, the print method will appear without parameters. public class NoParametersInStubMethods { public void invoking() { System.out.print("aString"); } }

12 years, 5 months

Issue 879 in moose-technology: PetitParser browser does not provide the possibility to add a new parser

by moose-technology＠googlecode.com

Status: New Owner: ---- CC: kurs....(a)gmail.com Labels: Type-Enhancement Priority-Medium Component-PetitParser New issue 879 by tu...(a)tudorgirba.com: PetitParser browser does not provide the possibility to add a new parser http://code.google.com/p/moose-technology/issues/detail?id=879 We should be able to invoke the PPAddParserRefactoring refactoring from the browser.

12 years, 5 months

Issue 761 in moose-technology: Missing method invocation with VerveineJ

by moose-technology＠googlecode.com

Status: Accepted Owner: ---- Labels: Type-Defect Priority-Medium Component-VerveineJ New issue 761 by anquetil...(a)gmail.com: Missing method invocation with VerveineJ http://code.google.com/p/moose-technology/issues/detail?id=761 see discussion on mailing list: "invokingMethods broken in moose or inFamix" source code: http://svn.apache.org/repos/asf/incubator/stanbol/trunk/enhancer/engines/ke… The method getLinkedEntityTypes in org.apache.stanbol.enhancer.engines.keywordextraction.linking.EntityLinker has an empty collection of invokingMethods even though the method is invoked for example by "process()".

12 years, 5 months

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

by admin＠moosetechnology.org

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

12 years, 5 months

To a unified software model repository for Moose.

by jannik.laval

Hi guys, Each time we need to do case studies in Moose, we have to select the software application, in a certain version and probably without all the source code needed. This results on evaluations that are probably not reproducible. I think that we need to unify our efforts and share the mse files of our models. With that, it will be not necessary to generate a FAMIX model each time we need one. For now, I begun to generate the model from the Qualitas Corpus 'e' (http://qualitascorpus.com/). There are 486 multiple versions of multiple Java systems. The mse files are really big (more than 650Mo for Eclipse_SDK3.7). I tried to load the biggest one in Moose, and it loads ! I just needed to attribute 2Gb of memory in the info.plist file of Moose 4.6. I propose to put the files on a server. For all the tar.bz2 files, I need 3.65Gb. Now, we lack ok at least two pieces of information : (i) the version of verveineJ used for the extraction. For now, VerveineJ has no version (I took the latest one). (ii) the version(s) of Moose that can load the file. I tried one mse file with Moose4.6. We also need a server that can accept all the files. Any suggestion ? Jannik

12 years, 5 months

Issue 878 in moose-technology: Glamour does not show the shortcuts on toolbar actions

by moose-technology＠googlecode.com

Status: New Owner: tu...(a)tudorgirba.com Labels: Type-Defect Priority-Medium Component-Glamour Milestone-4.7 New issue 878 by tu...(a)tudorgirba.com: Glamour does not show the shortcuts on toolbar actions http://code.google.com/p/moose-technology/issues/detail?id=878 In the following browser, the toolbar icon and menu item does not show the shortcut. | wrapper | wrapper := GLMWrapper new. wrapper act: [:f | f inspect] icon: GLMUIThemeExtraIcons glamorousInspect on: $i entitled: 'Inspect with icon'. wrapper act: [:f | f inspect] on: $i entitled: 'Inspect without icon'. wrapper show: [:a | a text ]. wrapper openOn: 'sample'

12 years, 5 months

Issue 874 in moose-technology: Secondary selection color is white

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Other Priority-Low New issue 874 by kurs....(a)gmail.com: Secondary selection color is white http://code.google.com/p/moose-technology/issues/detail?id=874 In Moose, secondary selection is enabled, but the color is the same as a background color. Therefore user cannot see the secondary selection.

12 years, 5 months

Issue 876 in moose-technology: FAMIX: Opposite reference between BehaviouralEntity and ImplicitVariable

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 876 by anne.et...(a)gmail.com: FAMIX: Opposite reference between BehaviouralEntity and ImplicitVariable http://code.google.com/p/moose-technology/issues/detail?id=876 - There is a reference between ImplicitVariable and BehaviouralEntity (parentBehaviouralEntity) whose opposite reference is named localVariables. However, in BehaviouralEntity, the reference named localVariables points to LocalVariables. And there is no inheritance between ImplicitVariable and LocalVariable. Please fill in the labels with the following information: * Type-Engineering * Component-FAMIX

12 years, 5 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