In the description of Girba, 2005, "Modeling History to understand Software
Evolution", there is a small statement on "referenceVersion" in the Hismo
metamodel:
"Each Version has a reference to the so called referenceVersion which
provides a fixed point in the historical space."
This is implemented in Moose Hismo, but there is little description of its
relevence to modelling. What is meant by "fixed point in the historical
space"? In fact, there is an interface to set it to easily set it to nil!!
(HismoEntityVersion class >> with:inHistory:)
Can Tudor or someone else able to describe why referenceVersion would be
important in time based analysis?
Could this be, for example, the "baseline" to which other copies are
compared? Can we have a different referenceVersions in different
HismoHistoryGroups? Can we change the referenceVersion on the fly during
analysis? I can see hints in the names of methods (e.g.
isBornPriorToOrInReferenceVersion), but I can't quite catch the semantics.
Can you give some guidelines on which version should be selected as the
referenceVersion, and why?
As I've described earlier, I'm trying to analyse different versions of
system development schedules. I'm trying to use the Hismo framework to its
best advantage, so I'm trying to understand the semantics as well as the
code.
Alan.
--
View this message in context: http://forum.world.st/What-is-the-relevence-of-referenceVersion-in-Hismo-tp…
Sent from the Moose mailing list archive at Nabble.com.
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 829 by google....(a)ben.coman.com.au: Roassal Label Text does not
scale with Zoom Out
http://code.google.com/p/moose-technology/issues/detail?id=829
Actions
1. Open Roassal Easel > Example > #arrowed edges > umlLike
2. Click the <Zoom out> button multiple times
Expected Behaviour
Text gets smaller so as to stay within the border as the label box gets
smaller.
Observed Behaviour
Only the border of the label gets smaller. The text gets the same size
until it all overlaps.
Updates:
Summary: Moose crashes when importing Citezen
(OrderedCollection(Object)>>doesNotUnderstand: #unsafeAdd:)
Comment #3 on issue 736 by tudor.gi...(a)gmail.com: Moose crashes when
importing Citezen (OrderedCollection(Object)>>doesNotUnderstand:
#unsafeAdd:)
http://code.google.com/p/moose-technology/issues/detail?id=736
(No comment was entered for this change.)
Updates:
Status: WontFix
Comment #2 on issue 401 by tu...(a)tudorgirba.com: fromPositions: and
toPositions:
http://code.google.com/p/moose-technology/issues/detail?id=401
(No comment was entered for this change.)
--
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
Chris wrote:
>Interestingly, Stephan has commented most of the other nodes - thanks!
Can't claim that. We tried merging with the last version and had conflicts.
We then used an earlier version that merged. Good to see it working though.
I noticed you're committing as both cbc and ChrisCunningham?
Seems to confuse smalltalkhub (it can't find user ChrisCunningham).
Stephan
Hi All,
it has been a while for me, so apologies in advance if this is known/stupid/...
I have not worked on at AspectMaps in a looooong time, and now I am assessing (heh) the effort of getting it up to date to the latest version of Moose. (Last working version is for 4.3) It has been going reasonably well, but now I have encountered something in the custom importer that has me stumped. Any pointers on how to resolve this would be most helpful.
FAMIXStructuralEntity>>declaredType: throws a DNU because it ends up sending #structuresWithDeclaredType to the ByteString 'method' when executing FMMultiValueLink class>>on: update: from: to: The only guys that understand that messages are FAMIXType instances. This is weird to me because there is no obvious relation between 'method' and any FAMIXType instances.
Can anybody point me to a solution?
---> Save our in-boxes! http://emailcharter.org <---
Johan Fabry - http://pleiad.cl/~jfabry
PLEIAD lab - Computer Science Department (DCC) - University of Chile
Hi,
I want to share with you a screenshot of the first version of the web client
for the Moose On Web Project.
It's based on Amber and use a Rest Api to interact with the Moose image.
A demo version will be online next week !
Cheers,
Vincent