I am trying to combine interactions with subviews in Mondrian but it is
not working as expected. This is with a fresh Moose 4.6 downloaded today
plus ConfigurationOfMondrian (AlexandreBergel.345) and [
ConfigurationOfMondrian project lastVersion load ].
As a test case, from ( World > Moose > Mondrian Easel ) I combine:
Examples > interaction > variation in node size
Examples > subviews > simple
to produce the following example:
----8<-----
view nodes: (1 to: 5)…
[View More] forEach:
[:each |
view interaction strongHighlightWhenOver: [ :v | v ].
view shape rectangle withText; size: 20.
view nodes: (1 to: each).
view gridLayout
].
----8<-----
However executing this in Mondrian Easel you will notice that (taking
for example the third group) hovering over small squares 1 & 2 does not
highlight these and hovering over small square 3 highlights the large
square rather than its small square.
I get my expected/required behaviour by modifying
MOAnnouncer>>registerForEvent: forNodes: updateShape: updateLayout:
to replace...
domainNodes := (aBlockOrSymbol moValue: ann element model).
nodes := ann viewRenderer nodeForDomainValues: domainNodes.
by...
nodes := OrderedCollection new add: ann element ; yourself.
...but I don't know what else that breaks or another way to get my
required behaviour.
How should I proceed?
cheers, -ben
[View Less]
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 789 by google....(a)ben.coman.com.au: Mondrian spelling recursive
http://code.google.com/p/moose-technology/issues/detail?id=789
I notice the following methods in Mondrian...
resetCacheResursively
resetFormCacheResursively
resetMetricCachesResursively
and assume the spelling should be "recursive" not "resursive"
Hi,
This little q&a game I initiated on the humane assessment blog might be interesting for people interested in Moose:
http://www.humane-assessment.com/blog/assessment-q-a/
------
Assessment is not difficult once you jump in the boat. But, this jumping can be perceived to be difficult. To dispel the magic, let's open the curtain and play a game.
It's simple. You ask questions, and I will answer them on this blog.
How to ask questions:
• send me an email at tudor(a)tudorgirba.com
• …
[View More]post a comment on this blog
• post a tweet mentioning @humaneA, or @girba
• ask me in person when you see me (I will be at PharoConf and Jazoon in the following months)
What questions? Any questions.
What's in it for me? You will help me shape my ideas.
Your turn now.
------
Cheers,
Doru
--
www.tudorgirba.com
If you can't say why something is relevant,
it probably isn't.
[View Less]
Hi,
I downloaded latest Moose and I dragged and dropped into the image a st
file to file it in. Debugger popped up saying:
SubscriptOutOfBounds: 1
By copy pasting the content of the st file into a workspace and by
executing the workspace's content it works.
here the build i used:
http://ci.moosetechnology.org/job/moose-latest-dev/923/artifact/moose/
Cheers,
Fabrizio
The issue tracker New Issue Template says: "Please fill in the labels
with the following information: * Type-Defect, Type-Enhancement,
Type-Engineering, Type-Review, Type-Other * Component-XXX"
but I don't see where to do that. Where should these be set?
cheers, -ben
Doru
Question1
---------
I would like to save the annotations (and annotation creation) with a model.
Do you have an idea where to start looking for?
Because so far I'm puzzled since this is a Magritte description of FameEntity.
Question2
--------
I have a question why FM3Element does not have a magritteDescription but description? should I fix it because even if we use pragma I prefer when this is regular.
FM3Element >>descriptionName
<magritteDescription>
^ …
[View More]MAStringDescription new
accessor: #name;
default: 'noname';
label: 'Name';
priority: 100;
beRequired;
yourself
FM3PropertyDescription>>magritteDescriptionType
<magritteDescription>
^ MASingleOptionDescription new
accessor: #type;
label: 'Type';
priority: 300;
default: FM3 boolean;
beRequired;
options: {FM3 number . FM3 string . FM3 boolean};
yourself
Question3
---------
FM3 number returns an AnonymousClass.
I saw that FM3 number create a FM3MetaDescription which describes a class.
I'm not sure that I need to add new species may be boolean, string and number are enough. Now I would like to change the an Anonymous in the UI a least.
I suggest that we create an instance of a subclass of Class (I called it FM3AnonymousClass) so that we can customize the printing and other behavior the way we want.
I did it but changing printOn: in such class is not invoked so I'm confused (but now I understand but still I found that confusing).
FM3MetaDescription>>numberClass
| class |
class := Class new.
class superclass: self.
class setFormat: self format.
class methodDictionary: MethodDictionary new.
class methodDictionary at: #isPrimitive put: (self methodDictionary at: #anonymousReturnTrue).
class setName: 'AnonymousClass'.
^class
Do you know the relationship between such anonymous classes and FM3etaDescrption?
The class comment does not say much on that :(
When I read the code I guess that FM3 is a subclass of FM3MetaDescription (not sure that the superclass is FM3MetaDescription or FM3MetaDescription class), now I do not know what is the real advantages compared to have real subclasses of FM3MEtaDescription (besides being cool and yes we can do it syndrome).
Now what confused me was that
FM3 number superclass is FM3Object and I got it
FM3MetaDescription>>number
number isNil ifTrue: [
number := self numberClass basicNew.
number initialize.
number name: #Number.
].
^number
For changing the printOn: method I imagine that it should be put in the
class methodDictionary at: #printOn: put: (self methodDictionary at: #anonymousPrintOn:).
booleanClass
| class |
class := FM3AnonymousClass new.
class superclass: self.
class setFormat: self format.
class methodDictionary: MethodDictionary new.
class methodDictionary at: #isPrimitive put: (self methodDictionary at: #anonymousReturnTrue).
class methodDictionary at: #printOn: put: (self methodDictionary at: #anonymousPrintOn:). <-------
class setName: 'AnonymousClass'.
^class
but it means that to define it in FM3MetaDescription. But so far it did not work… I will try again.
I have problem to see the added value to recreate an independent class and metaclass core?
Stef
[View Less]
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-ExternalTools
New issue 721 by tu...(a)tudorgirba.com: VerveineJ should mark constructors
http://code.google.com/p/moose-technology/issues/detail?id=721
Constructors should be marked with isConstructor.
Hi,
the method ensureClassesAndNamespaces Invoke "parentScope:" on a class.
ensureClassesAndNamespaces
<menuItem: 'Ensure Classes and Namespaces' category: 'Utilities'>
self allMethods do: [ :each |
each parentType isNil ifTrue: [
each parentType: self unknownFAMIXClass ] ].
self allClasses do: [ :each |
each parentScope isNil ifTrue: [
each parentScope: self unknownFAMIXNamespace ] ]
Now FAMIXType contains the method "parentScope" …
[View More]implemented as:
parentScope
"Polymorphic alias to mimic GlobalVariable#parentScope and similar"
^ self container
I believe that in the method ensureClassesAndNamespaces we should use the
method "container:" instead of "parentScope:"
What do you think?
Cheers,
Fabrizio
[View Less]