Moose-dev April 2013

moose-dev@list.inf.unibe.ch

34 participants
198 discussions

Re: Issue 736 in moose-technology: Moose crashes when importing Citezen (OrderedCollection(Object)>>doesNotUnderstand: #unsafeAdd:)
by moose-technology＠googlecode.com 23 Jun '13

23 Jun '13

Updates: Summary: Moose crashes when importing Citezen (OrderedCollection(Object)>>doesNotUnderstand: #unsafeAdd:) Comment #3 on issue 736 by tudor.gi...(a)gmail.com: Moose crashes when importing Citezen (OrderedCollection(Object)>>doesNotUnderstand: #unsafeAdd:) http://code.google.com/p/moose-technology/issues/detail?id=736 (No comment was entered for this change.)

4 15

Issue 647 in moose-technology: Integrate torch package visualization
by moose-technology＠googlecode.com 23 Jun '13

23 Jun '13

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 647 by cy.delau...(a)gmail.com: Integrate torch package visualization http://code.google.com/p/moose-technology/issues/detail?id=647 Maybe it would be a good idea (?) to use / integrate the torch packages visualization in moose ? http://hal.archives-ouvertes.fr/docs/00/53/15/08/PDF/Uqui10a-Torch-WCRE10.p…

2 4

Re: Issue 469 in moose-technology: integrate Kontractor
by moose-technology＠googlecode.com 23 Jun '13

23 Jun '13

Updates: Labels: Milestone-4.3 Comment #4 on issue 469 by tudor.girba: integrate Kontractor http://code.google.com/p/moose-technology/issues/detail?id=469 What is the status of this?

1 3

Re: Issue 437 in moose-technology: Text is not affected by zooming in Mondrian
by moose-technology＠googlecode.com 23 Jun '13

23 Jun '13

Comment #1 on issue 437 by alexandre.bergel: Text is not affected by zooming in Mondrian http://code.google.com/p/moose-technology/issues/detail?id=437 Situation has been slightly improved, but this is clearly not satisfactory

1 4

Issue 907 in moose-technology: VerveineJ does not export source anchors for FAMIXAnnotationType and FAMIXAnnotationTypeAttribute
by moose-technology＠googlecode.com 19 Jun '13

19 Jun '13

Status: New Owner: ---- CC: anquetil...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Famix New issue 907 by tu...(a)tudorgirba.com: VerveineJ does not export source anchors for FAMIXAnnotationType and FAMIXAnnotationTypeAttribute http://code.google.com/p/moose-technology/issues/detail?id=907 When we have an explicit annotation in the code, we should also get the source anchor associated with it. For example, in the below case, SomeAnnotation.java should be associated with SomeAnnotation: SomeAnnotation.java @Documented @Target({ ElementType.FIELD }) @Retention(RetentionPolicy.CLASS) public @interface SomeAnnotation {...} The same applies for the contained FAMIXAnnotationTypeAttributes.

1 3

Issue 910 in moose-technology: [VerveineJ] Some methods have 'private' modifier in source code but not in model
by moose-technology＠googlecode.com 10 Jun '13

10 Jun '13

Status: New Owner: anquetil...(a)gmail.com CC: damien.c...(a)gmail.com Labels: Type-Defect Priority-High Component-VerveineJ New issue 910 by damien.c...(a)gmail.com: [VerveineJ] Some methods have 'private' modifier in source code but not in model http://code.google.com/p/moose-technology/issues/detail?id=910 1- Take ant-1.8.2.mse 2- Search methods with each isProtected not and: [each isPublic not and: [each isPrivate not and: [each isStub not]]] 3- Some methods are private here

1 2

Issue 870 in moose-technology: ROFocusView focuses on the wrong spot
by moose-technology＠googlecode.com 04 Jun '13

04 Jun '13

Status: New Owner: ---- CC: alexandr...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Roassal Component-Glamour New issue 870 by tu...(a)tudorgirba.com: ROFocusView focuses on the wrong spot http://code.google.com/p/moose-technology/issues/detail?id=870 Open a Roassal Easel and paste this: | node | node := view node: #a. ROFocusView new on: node view: view raw. The node is selected somewhere at the bottom. The reason is likely to be that the canvas has a static size, instead of adapting by default to the size of the surrounding pane

1 1

MOGraphVizLayout: should I port it into Roassal?
by Juraj Kubelka 31 May '13

31 May '13

Hi, there is a class MOGraphVizLayout used in some visualisations (e.g. GTVisualizations new viewPragmaConstellation or MooseBrowser>>multiplicationBrowser). Should I port it into Roassal? Cheers, Jura

4 21

New features for forceBasedLayout
by mathieubmddehouck＠mailoo.org 17 May '13

17 May '13

Hello I've added new features for the force based layout. You can change the gravity center, tell where you want to see your fixed nodes and so on. I still have a bug with padding, and resizeStrategy, for example when you click on Example in the view. Gofer it smalltalkhubUser: 'MathieuDehouck' project: 'RoassalAlgorithm'; package: 'RoassalForceBaseLayout'; load. Try this : --------------------------- "Preambule. It includes the initialization. " | rawView view layout | rawView := ROView new. view := ROMondrianViewBuilder view: rawView. "enter your script below" "-------------" "-------------" view interaction on: ROMouseEnter do: [ :n | | nodes | nodes := view raw elementsFromModels: n element model allSubclasses. ROHighlightElements on: nodes ]. view interaction on: ROMouseLeave do: [ :n | | nodes | nodes := view raw elementsFromModels: n element model allSubclasses. ROUnhighlightElements on: nodes ]. view shape rectangle size: 10. view nodes: (Collection withAllSubclasses). view edgesFrom: #superclass. layout := ROForceBasedLayout_N new. layout fix: (view nodes last) at: 450@450; gravityAt: 437@38 . view layout: layout. view applyLayout. "-------------" "-------------" "Below is the initiation of the menu and opening the visualization" ROEaselMorphic new populateMenuOn: view. view open --------------------------------------- Mathieu

5 10

ConfigurationOfMoose + Spec
by roberto.minelli＠usi.ch 08 May '13

08 May '13

Hi, I am trying to load Moose in a fresh Pharo 2.0 image by doing > Gofer new > smalltalkhubUser: 'Moose' project: 'Moose'; > package: 'ConfigurationOfMoose'; > load. > > (Smalltalk at: #ConfigurationOfMoose) > perform: #loadDevelopment and it does not load correctly (i.e., there is an error after some minutes) I also tried #loadMinimal but it does not work either and I got: > MetacelloProjectSpecLoadError: No version found for 'default' of ConfigurationOfMooseAlgos > MetacelloMCProjectSpec>>loadVersion: > MetacelloMCProjectSpec>>load > MetacelloProjectReferenceSpec>>loadUsing:gofer: > MetacelloFetchingMCSpecLoader(MetacelloCommonMCSpecLoader)>>linearLoadPackageSpecs:repositories: in Block: [:pkg | pkg loadUsing: self gofer: gofer] > OrderedCollection>>do: Can anyone please take a look at the issue and fix the ConfigurationOfMoose? Cheers, R

5 8

← Newer
1
...
4
5
6
7
8
9
10
...
20
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev April 2013