Dear All,
I was wondering what should be the correct behavior in Mondrian in VW.
Consider the following scripts:
| view |
view := ViewRenderer new.
view interaction popupText: [:e | 'first level'].
view node: 1.
view node: 2.
view open
the popup appears for the first node only. Is it really the intended
behavior? I would expect the interaction object to be shared between
nodes
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
I need the following method from VW to run some tests in SqMoose. Does
anybody have an idea about its licence? Does not seem to be part of
our own extensions :(
It's not especially difficult to reimplement one, anyone can come up
with a Squeak/Pharo equivalent (although it works as is under Pharo,
perhaps there is a better way)
Symbol>>asSortBlock
"Answer a sort block, which evaluates this symbol for both arguments
and compares the resulting values"
| stream |
stream := (String new: self size * 2 + 14) writeStream.
stream
nextPutAll: '[:a :b | a ';
nextPutAll: self;
nextPutAll: ' <=b ';
nextPutAll: self;
nextPut: $].
^Compiler evaluate: stream contents
--
Simon
Hi,
With the version 134 of sqMondrian, the popupText doesn't work fine.
DSM worked before. Now, there is a infinited while when some popups
must appear.
popupText take account only the last popupText. In the example after,
only the text '3rd level' appear, everywhere.
--> in the previous version, it works.
----
| view |
view := MOViewRenderer new.
view interaction popupText: [:e | 'first level'].
view nodes: (1 to: 20) forEach: [:each |
view interaction popupText: [:e | '2nd level'].
view nodes: (1 to: 5) forEach:[:ea |
view interaction popupText: [:e | '3rd level'].
view nodes: (6 to: 10).
view gridLayout].
view gridLayout].
view open
----
Cheers
---
Jannik Laval
PhD Student - Software Quality - INRIA
Certified Project Management Associate (IPMA)
http://www.jannik-laval.euhttp://rmod.lille.inria.fr
---
Hi all,
What is the meaning of FAMIXType ?
I know its subclass is FAMIXClass, but why don't we merge them ?
In FAMIXMethod, the variable parentClass has been changed in parentType.
I think this is less clear.
The problem is that I don't see what is FAMIXType :)
Thanks for your help.
Cheers
Jannik Laval
I ran into the following problem (related to FamixModelExtractionTest
even if it's more general)
(#((1) (3) () ()) flatCollect: [ :each ])
returns
#(1 3 nil nil)
when one expects #(1 3)
flatCollect: is defined in Colllection, I dont want to override it
if possible.
Collection>>flatCollect: aBlock
| stream |
self isEmpty ifTrue: [ ^ self copy ].
stream := (self species new: self size) nsWriteStream.
self do: [ :each | stream nextPutAll: (aBlock value: each) ].
^ stream contents
Can someone find an elegant solution which would "shrink" the
resulting array to its non-nil content?
--
Simon
Hi All,
Just to let you know that the MooseBrowser now contains an import
Pharo package command in addition to the import MSE one.
cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi Alex,
I have progressed in DSM visualization in pharoMondrian.
Now I need some new features:
- on MOLabelShape, the method fontSize: doesn't work.
- It would be interessant to fix a width to a MOLabelShape.
- When I do subShape, I always have a 2 pixels free space on the right
and the bottom of the shape.
Maybe, we can do this together, next week.
Cheers
Jannik
Dear list
Here is the current version of the Famix3 metamodel, which should
replace the slightly outdated pdf of beta14.
Most importantly, we are asking for reviews, especially to check
whether bidirectional relationships are correct.
--
Simon
Hi All,
What should we do with UtilitiesTest and GroupTest? Some tests are red.
I will fix them over the time...
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
Hi all,
When I would like to import smalltalk code, like this:
---
importer := MooseSqueakClassPackageImporterTask new.
importer importingContext mergeClassAndMetaclass.
importer candidateClass: CandidateListOperator.
importer importerClass: SmalltalkImporter.
importer model: model; addFromPackagesNamed: #( #'Moose-LAN') ; run.
---
I have an exception: message not understood, for the message
#incomingAccesses.
This is in the method FMMultivalueLink>>on: update: from: to:
Thanks for your help.
Cheers
---
Jannik Laval
PhD Student - Software Quality - INRIA
Certified Project Management Associate (IPMA)
http://www.jannik-laval.euhttp://rmod.lille.inria.fr
---
