Here's a snippet from my builder method:
...
views do: [ :d |
container tree
act: [ :tree :projects | "change the model." tree update ]
iconName: #back
on: $n
entitled: 'New Project';
... ].
Each tree represents a different view on the same data. When the action is
performed, they all need to be updated. I tried replacing `tree update` with
`container update`, but that didn't work.
Ideas?
-----
Cheers,
Sean
--
Sent from: http://forum.world.st/Moose-f1310756.html
Hi!
Today I finished a refactoring on Moose 8 and I wanted to keep
everyone informed.
Since Moose 7 we have multiple metamodels and we generate them via a
generator. Each metamodel has a FMMetaRepository used to build tools
and to query our models. This FMMetaRepository was created by the
generators.
This had some drawbacks such as:
- You need to have your generator in the image to be able to query your model
- You cannot write a new metamodel without generator
Now this changed, the FMMetaRepository is created and stored in the
subclasses of MooseModel specific to the metamodel currently used.
The change should be transparent, except that you will need to
regenerate your metamodel for it to be effective.
Have a nice day.
--
Cyril Ferlicot
https://ferlicot.fr
Hello moose developer!
First of all, thanks for the little meeting at Esug19!
One of the point during the meeting was: do we have documentation about
the new features introduced in moose?
The answer is: YES!
It's still work in progress (as the work on Moose 8).
I'm trying to create a moose-wiki (as
https://github.com/pharo-open-documentation/pharo-wiki).
You can find it here: https://moosetechnology.github.io/moose-wiki/ (w
eb version) and here: https://github.com/moosetechnology/moose-wiki
(github version).
Most of the documentation come from themoosebook and
https://github.com/SquareBracketAssociates/Booklet-FamixNG and part of
the documentation are new.
I'm also trying to collect all the famix parsers (to create mse files)
we have and the meta-models.
I think we can also create links to great moose-projects (not directly
in a moose image but you can load it in moose (like FAST)).
I also create linked to blog posts that describes the protocol to
analyze projects with moose (as
https://fuhrmanator.github.io/2019/07/29/AnalyzingJavaWithMoose.html)
If you have one, please send me an email ;-)
Benoît Verhaeghe
@badetitou
PHD student at: RMoD - Inria Lille - Nord Europe
R&D developer at Berger-Levrault - France
Hi,
I would like to organise a meeting around Moose at ESUG19, to explain you what we have done this year, where we are going and discuss with you what you are expecting and how you can contribute.
If we are enough, we can do that either today (Wednesday) just after lunch at 13h or tomorrow Thursday after show us your project.
Can you please say if you want to attend and which date you are available?
Thanks in advance.
Anne
Hi all,
We have added the method "allUsing:".
It takes a Trait as a parameter and will return all the entities in your
model that use the trait.
Example:
mooseModel allUsing: FamixTClass
will return all the FamixJavaClass and FamixJavaInnerClass (if
FamixJavaInnerClass --|> FamixJavaClass)
It will be the main method if you want to query your model with abstract
entities.
Benoît
Hello
I want to execute statement
RTHTML5Exporter new export: aRoassalView
How?? to download exporter or?? exporter for???? Glamorou browser.
I read moose book and want use it for logistic application.
Feliks
