- Moose-dev - INF Mailman

Jenkins build became unstable: moose-latest-dev-4.8 #423

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/423/>

12 years, 2 months

2
3
0 0

tooltips in roassal

by Tudor Girba

Hi, The tooltips in Roassal are handled inside the Roassal canvas. Thus, you are right at the border of the Roassal pane, you cannot see the tooltip. It would be great to have a different solution for displaying tooltips. Cheers, Doru -- www.tudorgirba.com "No matter how many recipes we know, we still value a chef."

12 years, 2 months

1
0
0 0

PetitJava work

by Chris Cunningham

Hi. I'm starting to need to parse Java code, and am going to be using the PetitJava as found on SmalltalkHub. In particular, I need access to the AST from this parsing. So, I am going to be filling in the AST generation that is found there to cover more of the parsed syntax, following along the lines already laid out there. A question I have, though, is why none of our AST models seems to print out the 'code' by default? This model, and I believe the RB Smalltalk AST, neither have a printOn: defined, so that when you inspect/explore the results, it is rather unpleasant to find out what the model is of. In some past models, I have included a default #printOn: to the model parts,so that when exploring the parsed results, it is easier to see which parts of the code you are looking at. (Most recently while delving into a 10,000+ line COBOL program). Personally, I find it much more enjoyable. Is there a reason to not do this? I am already adding this to the PetitJava code as it makes it easier to see what I'm doing, but I can package it independently if anyone objects. -Chris

12 years, 2 months

3
2
0 0

About roassal design points for scalability if it will use athens for real

by Stéphane Ducasse

Hi guys with igor we sat and had a look at Roassal for a couple of minutes and here are a list of points for real speed improvements. Igor did not want to send them because he does not want to look like an asshole criticizing but I think that if we want roassal to be really a success we should. Now are the mooser and roassalers really interested in making Roassal scalable? (I hope so but I would respect otherwise and think for the future :) because we (moosers) could ask for feedback to igor and Alex you could come to pair program here with him around ESUG. Stef * Point 1: wasting cycles to do conversion -------------------------------------------------------- ROPharoCanvas>>line: aPoint to: aPoint2 width: aSmallInteger color: aColor nativeCanvas line: (self virtualToRealPoint: aPoint) to: (self virtualToRealPoint: aPoint2) width: aSmallInteger color: aColor. wasting cycles to convert from your local coordinate space into global one on every single operation is not a good idea. Guess why :) Athens provides the user-space coordinate system for geometry by default.. so that you don't have to maintain it by yourself. So if you want a real system these points should be addressed ;) * Point 2: missing transformation matrix ----------------------------------------------------- You don't even have a transformation as a concept.. and instead of simple and straightforward affine matrix which people learn in schools today: a Camera virtualToRealPointNoTrunc: aPoint "Return a virtual point from a one expressed in the real coordinates" | visibleBounds offset | visibleBounds := self bounds. offset := self position. ^ ((aPoint x asFloat - offset x * realExtent x / visibleBounds width) asFloat) @ ((aPoint y asFloat - offset y * realExtent y / visibleBounds height) asFloat) ROAthensCanvas>>line: aPoint to: aPoint2 width: aSmallInteger color: aColor | path | path := nativeCanvas createPath: [:builder | builder absolute; moveTo: (self virtualToRealPoint: aPoint); lineTo: (self virtualToRealPoint: aPoint2). ]. (nativeCanvas setStrokePaint: aColor) width: aSmallInteger . nativeCanvas drawShape: path see this #virtualToRealPoint: calls? Athens provides this for free. Do not do it the hard way: (do not transform poor vector multiple times to get there.) Athens do it for you using math: (v * M1) * M2 = v * (M1*M2) * Point 3 about design ------------------------------ ROAbstractArrow ROArrow ROReversedArrow ROHorizontalArrow ROReversedHorizontalArrow ROVerticalArrow ROReversedVerticalArrow Why do we have all these classes? why they are not...

12 years, 2 months

6
25
0 0

great energy

by Tudor Girba

Hello everyone, The energy flowing through this mailing list these days is amazing. Let's keep it up :) Cheers, Doru -- www.tudorgirba.com "When people care, great things can happen."

12 years, 2 months

3
2
0 0

Jenkins build became unstable: moose-latest-dev-4.8 #417

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/417/>

12 years, 2 months

1
1
0 0

question about layout visualization

by Stéphane Ducasse

Hi guys I would like to see how I can avoid to get confused. I would like to see distribution maps improved and get some variations. Now I wonder is distribution maps a layout? Stef

12 years, 2 months

4
3
0 0

Refactor, LaggeredTree

by mathieubmddehouck＠mailoo.org

Hi I've made kind a big refactoring in Roassal-Algorithm, as I've learnt that ROContainer's attributes was there for any kind of use, now the CompactTree family uses it, there are new methods for ROElement in the package, but no more need of ROCompactTreeNode (former RONode). In the same time, I've written tests to be sure that the code still works (in fact it's the aim of tests I think). So now, there ain't crossing any more, in LaggeredTree. Tell me what kind of new layout you wish to see in Roassal, maybe you can have a look at D3 library. Or maybe I will start looking at how to increase roassal scalability. Just tell Regards Mathieu

12 years, 2 months

4
7
0 0

Roassal edgesToAll:

by Usman Bhatti

Alex, When using ROMondrianViewBuilder >> edgesToAll: the direction of the edges is reversed. For example, in the script below, I am telling Roassal to draw edges to 2 but its drawing edges from 2. Can you please confirm and correct, if need be. view := ROMondrianViewBuilder new. view shape rectangle size:20. view nodes: #(1 2 3). view shape arrowedLine color: Color red. view edgesToAll: #(2). view forceBasedLayout. view open. Usman

12 years, 2 months

5
17
0 0

Question: Can I remove these codes?

by Juraj Kubelka

Hi! Can I remove these methods?: 1. MooseEntity>>openInEasel (it is not called and there is MOEasel) 2. FAMIXClassGroup>>viewDuplicationComplexity (annotation is commented) 3. #browsePackageBlueprints (it is not called, annotations are commented) 6. HismoClassHistoryGroup>>viewEvolutionMatrix and #viewEvolutionMatrix (it is not called) Thanks, Jura

12 years, 2 months

4
3
0 0

generalizing NeoCSV

by Tudor Girba

Hi Sven, I am looking at NeoCSV, and I would like to add it to Moose by default. During the review, I noticed that it relies on perform: addRawField: accessor "Add a field based on an accessor to be written as a #raw field" self addFieldAccessor: [ :object | self writeRawField: (object perform: accessor) ] I would prefer to have it modified to simply use value:. In this way we can pass blocks as transformation specifications. Why is this important? Because we often have values that we want to export but that do not have a direct correspondent in a unary method. Would it be Ok to make this modification? Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

12 years, 2 months

1
0
0 0

Adding predefined types

by Yuriy Tymchuk

Hi. So FM3 has 4 predefined types: Object, String, Number and Boolean. What is the best way to add more. For example I want to model a database and I wan't to be able to have Integer, Float, Date, etc. -- View this message in context: http://moose-dev.97923.n3.nabble.com/Adding-predefined-types-tp4027277.html Sent from the moose-dev mailing list archive at Nabble.com.

12 years, 2 months

3
3
0 0

ConfigurationOfMoose + Spec

by roberto.minelli＠usi.ch

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

12 years, 2 months

5
8
0 0

Question: Can I remove GlamourousHealth

by Juraj Kubelka

Hi! Can I remove this class? Alexandre noticed that it is likely not used. And it seams to be broken. In my image calling "GlamourousHealth new viewTestCoverage" produces "does not understand" message. Thanks, Jura

12 years, 2 months

1
0
0 0

Migration of tools from Mondrian into Roasal - project status

by Juraj Kubelka

Hi! There is a compilation of the work I have to do in order to remove Mondrian from Moose. If you find something irrelevant or missing or you have a note I should consider, I will appreciate it! Cheers, Jura MOViewRender is used for visualisations: 1. UML class diagram 2. View Multiplication constelation 3. Side by Side Duplication 4. System complexity 5. Namespace Hierarchy 6. System Overview 7. Within overall hierarchy 8. Package-wise System Complexity 9. Evolution matrix 10. Hierarchy evolution MOViewRenderer is used in classes (package Mondrian is not included in this list): 1. DSMBuilder 2. DSMExample 3. DudeMultiplicationGroup 4. FAMIXClass 5. FAMIXClassGroup 6. FAMIXNamespaceGroup 7. FAMIXPackageGroup 8. GlamorousHealth 9. GLMBrowser 10. GLMMondrianEasel 11. GLMMondrianPresentation 12. GLMMondrianPresentationTest 13. GLMMorphicMondrianRenderer 14. GTVisualizations 15. HismoClassHistoryGroup 16. MOCycleTableSample 17. MOFameView 18. MOLayerTable 19. PackageBlueprint 20. PPParser 21. TwoDimensionsDistributionMap MOFormsBuilder is used (package Mondrian is not included in this list): 1. MOFameView>fameShape 2. MOCycleTableSample>>exampleCycleTable 3. HismoClassHistoryGroup>>viewEvolutionMatrixOn: Other things: 1. Create ROGraphVizLayout (used in Annotation Constellation) 2. DSM uses borderStyle. Mandatory? Should we implement it in Roassal? Obsolete code? Remove it?: 1. MooseEntity>>openInEasel (it is not called and there is MOEasel) 2. FAMIXClassGroup>>viewDuplicationComplexity (annotation is commented) 3. #browsePackageBlueprints 4. FAMIXNamespace>>accessTo: has flag "maybe not more useful" 5. FAMIXImplicitVariable does not understand parentType (produces does not understand debugger).

12 years, 2 months

2
1
0 0

Jenkins build became unstable: moose-latest-dev-4.8 #409

by admin＠moosetechnology.org

See <https://ci.inria.fr/moose/job/moose-latest-dev-4.8/409/>

12 years, 2 months

1
1
0 0

Simple warnings in Roassal

by Andre Hora

Hello Alex, Some simple warnings found in Roassal: Warning: call #sourceCode instead of #getSource for compiledMethods ROEaselMorphic>>getExampleSourceFor: ROEaselMorphic>>scriptPreambuleForMethod: ROMondrianExample>>methodComplexityFor:on: ROMondrianExample>>methodComplexityOn: I can fix if it is ok for you.. regards, -- Andre Hora

12 years, 2 months

2
2
0 0

Issue 894 in moose-technology: Roassal revised ROSelection and example

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Defect Priority-Medium New issue 894 by benjamin...(a)gmail.com: Roassal revised ROSelection and example http://code.google.com/p/moose-technology/issues/detail?id=894 Initially I contributed ROSelection as part of the rubberbanding feature. The attached changeset generalizes it a bit and provides the folllowing example of its use. ------------- activeSelection := ROSelection new onInclusion: [ :element | ROHighlightElement on: element color: Color red ]; onExclusion: [ :element | ROUnhighlightElement on: element ]. statusBar := (ROElement on: activeSelection) + (ROLabel text: [ :el | el model asString ]) + ROBox white. view stack add: statusBar. statusBar translateTo: 0 @ 480. view shape label. view interaction on: ROMouseLeftClick do: [ :ann | activeSelection clear. activeSelection add: ann element. ]. view nodes: #(1 2 3 4 5). view gridLayout. --------------- There are two things I need help with: 1. Deselecting all elements when clicking on the background.** 2. Multiple selection, which if I knew the right way to work with the announcement events, would conceptually be as simple as the following modification... [ :ann | ann isShiftClicked ifFalse: [ activeSelection clear ]. activeSelection add: ann element. ]. **may also relate to Issue 884 comment #9 . Attachments: ROSelectionAndExample.1.cs 1.4 KB

12 years, 2 months

2
12
0 0

Issue 911 in moose-technology: Nested nodes in Roassal take too long

by moose-technology＠googlecode.com

Status: New Owner: alexandr...(a)gmail.com CC: usman.bh...(a)gmail.com Labels: Type-Defect Priority-Medium Component-Roassal New issue 911 by usman.bh...(a)gmail.com: Nested nodes in Roassal take too long http://code.google.com/p/moose-technology/issues/detail?id=911 Try this script for creating nested nodes in Roassal. The execution seems to never return. The behavior is similar with both Mondrian DSL or Roassal API. view := ROMondrianViewBuilder new. view shape rectangle withoutBorder. view node:#aaa forIt:[ view shape rectangle. view nodes: (1 to: 10000). view gridLayout. ]. view shape rectangle withoutBorder. view node:#bbb forIt:[ view shape rectangle. view nodes: (1 to: 1000). view gridLayout. ]. view verticalLineLayout. view open

12 years, 2 months

1
3
0 0

Re: Refactor, LaggeredTree

by mathieubmddehouck＠mailoo.org

Yes, it's the same algorithm that I translated. And the RadialTreeLayout_N has changed a bit, or example it does not use "aNode element" but simply "aNode", and other changes that makes ROCompactTreeNode no longer useful. Well, I will see at the cluster layout, it must not be very complicated. Regards Mathieu

12 years, 2 months

2
1
0 0

New layout: ROClusterLayout

by mathieubmddehouck＠mailoo.org

Hi There's a new layout fro Roassal, try it. Gofer it smalltalkhubUser: 'MathieuDehouck' project: 'RoassalAlgorithm'; package: 'Roassal-Algorithm'; load. | rawView view layout | rawView := ROView new. view := ROMondrianViewBuilder view: rawView. "enter your script below" "-------------" "-------------" view shape circle size: 10. view nodes: (Collection withAllSubclasses), (ROLayout withAllSubclasses ). view edgesFrom: #superclass. layout := ROClusterLayout new. view edges do: [ :e | e - ROLine + (ROBezierCurve radial new attachPoint: ROCenteredAttachPoint instance) ]. view layout: layout. "-------------" "-------------" "Below is the initiation of the menu and opening the visualization" ROEaselMorphic new populateMenuOn: view. view open Regards Mathieu

12 years, 2 months

3
3
0 0

Porting DSM into Roassal. Question about MOFilledStyle>>borderStyle:

by Juraj Kubelka

Hi! I am almost done with porting DSM views into Roassal. There is several times (for example: NumberColoredDSM>>contentOfSimplyCell:for:with:out:) used method MOFilledStyle>>borderStyle: which is not supported by Roassal. Just for sure: Is it obligatory for this views? Should I implement this feature in Roassal? Thanks, Jura

12 years, 2 months

4
5
0 0

Moosing Cobol

by Fabrizio Perin

Hi, I will soon need to do some analyses of cobol code. Is there something available to import Cobol into Moose? Cheers, Fabrizio

12 years, 2 months

2
1
0 0

delphi parser

by Tudor Girba

Hi, I started to look into the Delphi parser. I was successfully parsing a couple of large files. I will let you know how it goes. In the meantime, I would also migrate it to STHub in the Moose team. Is this Ok with you? Cheers, Doru -- www.tudorgirba.com "Every thing has its own flow"

12 years, 2 months

1
0
0 0

Issue 917 in moose-technology: ConfigurationOfMerlin on Smalltalkhub needs to be updated

by moose-technology＠googlecode.com

Status: New Owner: ---- Labels: Type-Enhancement Priority-Medium New issue 917 by usman.bh...(a)gmail.com: ConfigurationOfMerlin on Smalltalkhub needs to be updated http://code.google.com/p/moose-technology/issues/detail?id=917 ConfigurationOfMerlin on Smalltalkhub needs to be updated because the baseline still loads from squeaksource, it should normally load from the packages from SmallTalkHub. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

12 years, 2 months

1
3
0 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

Moose-dev