Gentlefolks,
I'm looking for applications which would benefit from maze resolution. The
picture attached can give you an impression. It has 4 collections of
objects and 4 collections of relations (all can be manipulated).
The large center area holds multiple documents (code, text, multi media).
Documents, objects and relations can be moved out of the way if desired.
Resting the mouse over something tells you what it is.
When selecting a relation it highlights the objects which it can see.
Maze resolution can guarantee that no other non-empty relation exists from
top left to bottom right and also not from top right to bottom left. So
there can be nothing in the picture (nothing in the image!) which is
hidden from you. Objects can be relocated and can actively help you to
find another suitable location.
I post in the hope to receiving application ideas from other people, i.e.
what to put into the 8 selection areas. If the picture can be populated
with things that make sense then a prototype would make sense (the example
below could be a start).
Thank you in advance for your feedback, all appreciated.
Cheers
Klaus
P.S. an example: top-left classes, top-left-right #category, top-right
system categories, bottom-left methods, top-left-bottom {#allSelectors.
#class->#allSelectors}, bottom-right methods, bottom-left-right #messages.
Then bottom-right shows the methods which are sent but not implemented
(foreigners) by the top-left classes themselves. And top-right can
optionally show the to bottom-right corresponding foreign system
categories with bottom-right-top #methodClass->#category.
P.P.S. thank you Doru for introducing me to your thesis and to
Moose+Mondrian.
hello
I created my own metamodel to import my own elements in Moose.
Actually, I want to analyse chickens and eggs with Moose. So,I wrote
classes Chicken and Egg which both extend MooseElement. Then, I extended
MooseModel in my package and I implemented allChickens and allEggs methods
in the class MooseModel. Finally, I imported in Moose my instances of
Chicken and Egg and I could see them into Moose, so I was very happy :)
Infortunatly, when I decided to unload my model(and consequently the
methods allChickens and allEggs in MooseModel), Moose didn't work anymore!
To solve it, I ran System>> reinitializeDefaultSystem. Nervertheless, it
may be painful and tiresome to reinitialize the system whenever a
metamodel is removed.
Is there an other solution to fix this problem? Or is there possible to
reinitialize it automatically at Moose launch.
Thank you for your help
Sara
Hi dear Moose/Mondrian experts :-)
since we discussed usage of Mondrian at Squeak day last October I
assume there is much work done. I have not tracked the mailinglist
the last months. So today, I have to visualize some Fortran 77 and C+
+ Code. Assume that I have a FAMIX file (done by Sourcenavigator
parser and TCL).
Which Moose/Mondrian version I should use as an simple user ?
Regards
Hans
Dear Famixers and Moosers,
one of the results of the Famoosr Workshop is that we will work
towards a release of Famix 3.0, to facilitate seamless sharing of
case-studies and metamodels between researchers and tools.
You are all invited to take part in the new Famix version. Join the
discussion, share your metamodels and take part in the
standardization. In particular EMF/ecore experience is welcomed. As a
seed, I started a wikisite
http://smallwiki.unibe.ch/moose/famix3.0/
To edit the site you need a password, please contact us to get it ..
err, more precise, contact Doru (as I am on holidays next two weeks
contacting me will be pointless).
cheers,
AA
Hi,
I found the default model in Moose not usefull.
Would it be possible not to have them?
Or at least keep only one.
Thanks
Mth
___________________________________________________________________________
Yahoo! Mail r�invente le mail ! D�couvrez le nouveau Yahoo! Mail et son interface r�volutionnaire.
http://fr.mail.yahoo.com
New submission from Adrian Dozsa <adi.dozsa(a)gmail.com>:
in the FAMIXAbstractAssociation for classState it uses MinimalState which is
stub, because for "attributeSet: name value: value" it only calls "self
nullStateError". So FAMIXAbstractAssociation cannot have state.
----------
component: Famix
messages: 116
nosy: adi.dozsa
priority: Bug
status: unread
title: FAMIXAbstractAssociation has no classState
________________________________________________
Moose Bugs <moose-dev(a)iam.unibe.ch>
<http://macamis.unibe.ch/trackers/moose/issue75>
________________________________________________
