Hi guys,
Anybody used the C# importer recently? Do you know
if it exports in FAMIX 2.1? I'm a bit behind the trend with
Softwarenaut and would like to apply it on a case study :)
Cheers,
M.
Anybody to refactor the tools list on the website?
http://www.moosetechnology.org/tools
I started to sort things out, putting generic tools/frameworks on top, and custom tools/projects after.
Maybe it would be good to revise a bit the page, see what is/what is not in the Moose suite and update the information.
And why not adding a 'Moose platform' to group together all things generic?
--
Simon Denier
Hi,
I'm having a problem updating labels with glamour.
I explain:
I have a browser with a "status line" at the bottom, something like this:
browser := GLMTabulator new
row: #itemDetail;
row: #summary size: 18;
yourself.
then, on #summary:
browser transmit
to: #summary;
andShow: [ :presenter |
presenter label
updateOn: AnAnnouncement from: [self announcer ];
display: [ self summary ] ].
but the summary is never updated :(
I'm doing something wrong, or this is a bug? (if I change #label for #text, it is updated properly).
Also... dynamicActions shouldn't be updated, on a presentation update? Now I'm using some "status buttons" (it changes an overlay depending on status), and of course, I would like to update it when something changes... how can I do that?
best,
Esteban
Some people suggested trying moose for analysis of SAS programs, and I'm
trying to figure out where to start with the meta-modeling.
SAS is not object oriented, though parts of it could be imagined to be.
The main SAS code contains blocks of statements that begin with DATA or
PROC; each block could probably be thought of as a function--to be
precise, the application of a function.
If I want to make some new models, where do I start? FM3? FAMIX?
elsewhere? The 4.0 release announcement says FM3 and FAMIX3 are both
implemented in Fame, so maybe start with Fame? I've read some
documentation, but I can't tell.
My inspiration for the project is understanding how some SAS datasets
were produced. I have a system that creates numerous datasets, which
feed into later datasets, etc. This is split at least across a couple
of program files and it's really too complicated to keep in the brain.
If I get ambitious it would also be useful to trace where particular
variables came from, in the sense of both datasets and individual
expressions.
The only thing resembling a SAS parser I've run into (except for SAS,
which is closed source) is a Perl module, and it looked relatively
primitive. I've been using PetitParser, and at the point I started
thinking about what it would parse results into.
Thanks for any pointers.
Ross Boylan
When working on eclipse, I discovered the necessity to represents things like plugins or components which are not directly handled in Famix.
It is important if we want to be able to deal with real world cases.
May be we should consider introducing them as Moose Entities?
Or may be not: I used Moose-Groups (of class because one package can be spread over different plugins) and it is not that bad.
the main issue, in my case, was that classes don't know to what group they have been assigned...
So computing dependencies could be very lengthy.
I solved that by creating a dictionary on the side, but maybe we should think on a better solution.
And then of course integrate this with all the tools...
nicolas
I am looking to understand what mse entities are created for associations
(except inheritance i.e. invocations, access, refs) in code and how to
exactly treat the duplicates. I have seen a reference of it in a bug
reported for VerveineJ but I am not sure if this issue has been discussed
elsewhere.
For example,
A a;
M()
{
a = new A();
a = new A();
a.CallAMethod();
a.CallAMethod();
}
The above code creates these associations (with Verveinesharp) ..
1. An invocations to A's constructor (duplicate constructor invocation is
ignored).
2. A field access to the field a (only one instance is recorded, the others
are just ignored).
3. An invocation to CallAMethod (field access is already recorded so this
one is not considered).
4. A reference from method M() to type A (Duplicate reference is ignored).
Please let me know if there an anomaly.
thanx,
Usman