Hi,
moose.unibe.ch is now watched with Google Analytics.
Cheers,
Doru
--
www.tudorgirba.comwww.tudorgirba.com/blog
"Problem solving should be concentrated on describing
the problem in a way that is relevant for the solution."
Hi,
The goal of a highlight in moose.unibe.ch is to provide an entry point
inside the content of the page.
The highlight should be visual and the accompanying text should be
kept to a minimum. Please do not write more than one line there,
because it clutters the front page.
Cheers,
Doru
--
www.tudorgirba.comwww.tudorgirba.com/blog
"Every thing has its own flow."
Hi all,
after doing some reading to prepare for tomorrows talk, I started to
implement traversal strategies for Moose, based on the new Fame
framework. Currently implemented is a simple single edge strategy,
using classes or properties as waypoints, Multiple single edge
strategies can be combined to a compound strategy. I stopped
yesterday night shortly before implementing the actual visiting...
If you are interested you may have a look at the package Fame-
Traversals in MetaDevelopment on SCG Store, there are even tests,
using the EquationSystem example as sample model :)
cheers,
AA
There is a new famix.jar online (revision 14476), see url
https://www.iam.unibe.ch/scg/svn_repos/Sources/Famix/MSE4Java/famix.jar
The following opposites are fixed now
> Opposites must match: Moose.Model.mooseModel
> Opposites must match: FAMIX.AbstractStructuralEntity.accessedByList
> Opposites must match: FAMIX.InheritanceDefinition.superclass
> Opposites must match: FAMIX.InheritanceDefinition.subclass
> Opposites must match: FAMIX.Class.incomingInheritance
> Opposites must match: FAMIX.Class.accessedByList
> Opposites must match: FAMIX.Class.outgoingInheritance
> Container must be single-values: FAMIX.Class.method
cheers,
AA
Mmh... the website still seems to have that "bug" related to the system
below it. If I let the site open for a few hours without touching it;
and then try to open a link; I get redirected to "localhost:...."which
obviously fails. And for me this kind of browsing behavior is quite
common; since I open websites in tabs and tempt to forget about it :) I
guess it has something to do with cookies expiring?
cheers
hi,
I just seen that #union: in Collection is implemented as following:
^self copy addAll: aSet.
Thus it returns the passed parameter instead of the resulted
collection (see #addAll: in collection).
bests,
Hani
Wouldn't it be useful to be able to specify properties to be keyed when
they are multivalued? This would allow us to generate dictionary related
code for those keyed elements; and en plus give us a way to specify that
one of the properties can not be used twice within a same environment.
Example usage would be the classes property of a fm3.Package which would
be keyed by the property name.
Like this we would be able to do something like:
aPackage.getFromClassesAt("aName") instead of having to loop over the
classes until we find the right one.
I know that Adrian just stores all fm3specified packages+classes into
one big dictionary... but of course; having this property would also
enable its use one level lower.
Just a thought.
Toon
@adrian
I was just checking your fm3.mse file... first of all; all files should
end in a newline so maybe you want your endDocument to print a newline
at the end...
Then I see that for opposites you do not specify derived anymore either?
Thats already good.
The container property you have, that is for identifying back links
right? If so... aren't all One's of a One->Many relationship back links?
Does anybody know of a metamodel where this is not the case? If not ...
maybe we could throw that out and infer this too?
cheers
Hi,
I worked for some days with the new version of Moose in which the
Group and MooseModel have AbstractGroup as super class, and it seems
to work just fine.
As a consequence, I now published this as development so it gets
loaded with Moose Config.
Please let me know if you encounter any problems due to this change.
Doru
--
www.tudorgirba.comwww.tudorgirba.com/blog
"Problem solving efficiency grows with the abstractness level of
problem understanding."